Op een zonnige herfstdag (Monday 06 October 2003 18:58), schreef
[EMAIL PROTECTED]:
> Automated smoke report for 5.8.1 patch 21395 on windows nt - 5.1 (x86)
> (TANGAROA) using version
> Report by Test::Smoke v1.18.06 (perl 5.8.1) [11 seconds]
>
> O = OK F = Failure(s), extended report at the bottom
> X = test(s) failed under TEST but not under harness
> ? = still running or test results not (yet) available
> Build failures during: - = unknown or N/A
> c = Configure, m = make, M = make (after miniperl), t = make test-prep
>
[snip]
> Summary: FAIL(m)
What did go wrong? Not a sign we loose Win32 right after release :(
Steve, can you send me these 3 files:
* <builddir>/mktest.out
* <builddir>/config.sh
* <smokedir>/smoke58x.log (or whatever you configured)
I would like to think about a way to incorporate "make" failures into smoke
reports, so as the obvious stuff is also automcally reported. (Yup,
suggestions on how to do it are always welcomed!)
Good luck,
Abe
--
Well, dereferencing that (as CvGV() would do) leads nowhere. Or, as
the Ten Commandments for C Programmers quoth, "Thou shalt not follow
the NULL pointer, for chaos and madness await thee at its end."
-- Jarkko Hietaniemi on p5p @ 2002-05-14
