[Cvs-dev] Re: latest cvs-passwd patch

[Derek R. Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

P J P wrote:

> ^^^^^^^
> ** expected:
>   ...
> error
> ** got:
>   ...
> error
> vvvvvvv
> 
> the surprising thing is, both, the '** expected:' & '** got:' output is
> exactly the same, and still the test fails. Rest all, I hope, is quite
> okay; But if anything needs to be redone or undone, please inform me.

When I've run into this in the past, there has usually been differing
white-space between the regex and result text.  Either one has a tab and
one has spaces in some location that lets the text still line up when
visually inspected, or there are trailing spaces or tabs on some line
just before the EOL (\n) where it doesn't show up easily, either.
Similarly, leading and trailing blank lines can be hard to spot.

The contrib/debug_check_log.sh script Mark described earlier can help
spot the offending lines in any of these issues.  Once you have narrowed
the offending line(s) down, you can usually find the difference by
moving the cursor around and counting white-space characters.

There is a secondary and very rare issue that has to do with trailing
blank lines in either the regex or result.  I don't recall exactly how
to trigger it, but there is one case that debug_check_log.sh doesn't
spot.  I usually solve the problem by trying variations on the regex.
If I recall correctly, I've never not been able to solve it by either
adding or removing one blank line from the end of the regex.

Good luck,

Derek
- --
Derek R. Price
CVS Solutions Architect
Get CVS support at Ximbiot <http://ximbiot.com>!
v: +1 248.835.1260
f: +1 248.835.1263
<mailto:address@hidden>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFKnkMLD1OTBfyMaQRAhD6AKC+kapXFB9aQpl0nczoC6WuhTAwaACfbJ7J
ld3+9yTLdVVUG5yQYa3BtoU=
=B2Eg
-----END PGP SIGNATURE-----