Re^2: Unit test failing but "got" and "expected" are equal

Good call, thanks Corion!

# hello\x2c\x20world\x21\x0f
# hello\x2c\x20world\x21
[download]

At least now I have something to focus on.

Update: In the meantime until I can figure out exactly what's going on, I've made the following change to the test so that my automation doesn't keep yelling at me:

like $s->gets(13), qr/^hello, world!/, "puts() and gets() ok";
[download]

Comment on Re^2: Unit test failing but "got" and "expected" are equal Select or Download Code

Replies are listed 'Best First'.
Re^3: Unit test failing but "got" and "expected" are equal by AnomalousMonk (Archbishop) on Jan 04, 2019 at 20:36 UTC
`qr/^hello, world!/` ~~You might also consider `qr/^hello, world!\s\z/` since `\x0f` is a member of the `\s` set and the quoted regex allows anything* at the end of the string.~~ No! I was thinking of `\f` (form feed) and not of `\x0f` ... never mind ... Give a man a fish: `<%-{-{-{-<`	[reply] [d/l] [select]
Re^4: Unit test failing but "got" and "expected" are equal by stevieb (Canon) on Jan 04, 2019 at 21:08 UTC
Don't feel bad, at first, I was thinking the same thing :) Because I just reloaded all of my Pi devices from scratch, I'm unsure if this is an "issue" with the config of the serial device on-board or not quite yet. All I know is that after I built my PCB hard-soldered test platform with all my ICs and sensors I'm testing, but before the OS upgrade, it worked without hiccup. No software changes to the serial code on my end (or my underlying C code), so I'm thinking it has to be how the device is configured hardware-wise.	[reply]
Re^5: Unit test failing but "got" and "expected" are equal by kschwab (Vicar) on Jan 05, 2019 at 05:06 UTC
It's an ascii NAK (negative acknowledge). Maybe set hardware flow control, or slower baud rate? Or perhaps NAK means something special in WiringPI?	[reply]


more useful options
	PerlMonks