Re: [Patch] Fix output pattern checking issue
Ben Elliston <[email protected]>
| Newsgroups | gmane.comp.sysutils.dejagnu.general |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Mar 04, 2016 at 10:20:57PM +0100, Yvan Roux wrote:
> there is an issue when remote testing testcases which check an
> output pattern with an explicit '\n' at the end. rsh_exec
> explicitly removes it to behave as 'exec', I don't know if something
> changed in 'exec' behavior since these lines were checked in in 2001
> or if it still removes a '\n' in some configs, but there is a
> mismatch between native, where these kind of tests are ok, and
> remote, where they fail.
Natively, exec strips the newline (and there are no occurrences of
"keenewline" in the source tree; I grepped). Here's a simple test
script (foo.exp):
set x [exec uptime]
set x2 [rsh_exec remotebox uptime "" "" ""]
note "local: >${x}<"
note "remote:>[lindex $x2 1]<"
No newline in either case, which is what I would have expected.
Cheers, Ben
_______________________________________________
DejaGnu mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/dejagnu
signature.asc
(application/pgp-signature, 811 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIVAwUBVueQlnY2KIi1WYjUAQg2rRAAgJ1pOMxDVdR0f9QXRnQmI0n6lmUdwSgj qTqLGDO1X1Y7u1r4eGxEX9nTo0XeRJGjsHiimRhNBdtCb72yGdmkh23O2WpKMzJd G3ruRvYV8A4xWmWgugWAj/agbQTPbhWT9QtWOtfbp6sIncpBEUjNiWbID0SmczlD TFb12ruM7qQX6qjXRz81ooJwHGE6ZRnwjgzhMM4ZyCEVch6T5pjNuk1dFUYNjQ81 oSuFuhFKp2XKZhz53T78lpTVTZPPb0+4h7vSsWO/+0oxgHOuMCYVDmzIIfwy9TnL hwhkrGC6aaxunM9qz0Jdm5+gWDyhasPO5wpgG10sM+G7Yl35UnyfAm3NggVfjKDt XgvnYOB0uNmaM5269aDchsCXfnXsldGItloff3UaOSz9gDvNb4C/tD1uph9BgkUM V5+y8NiBLPYbvw8AlE0LPnVXPJKqKJD4NPSfj3Wkm35oULToN0PIxybVQdw9lqw6 j920/QdxenFlSBw+4pTZUPMwUDPueBGEUpTKXNsysvk1jVDneS1UgjzzpBw5MG04 GYTEti6dr3URTO9WRkT62LbHCadQ3/kVAbjQxe6NFLkFz6FfO/lDVhHkOrQWK3ht UhAALA87O9DAPsmd9N7QVr9rqfxE1w6Olo/Dbwd6Qa7AyS387/uMhIwCqcnW9pCe eRiJONR3h2U= =DcVx -----END PGP SIGNATURE-----