Discussion:
Smoke [blead] v5.21.3-274-g57630fb FAIL(F) MSWin32 Win2000 SP4 (x86/1 cpu) {blead}
(too old to reply)
George Greer
2014-09-01 16:16:00 UTC
Permalink
Automated smoke report for 5.21.4 patch 57630fb62d6f2d2f3415550c56dc3a3c07c4bf37 v5.21.3-274-g57630fb
perl-win2k: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz(~2654 MHz) (x86/1 cpu)
on MSWin32 - Win2000 SP4
using cl version 14.00.50727.762
smoketime 2 hours 45 minutes (average 41 minutes 22 seconds)

Summary: FAIL(F)

O = OK F = Failure(s), extended report at the bottom
X = Failure(s) 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

v5.21.3-274-g57630fb Configuration (common) none
----------- ---------------------------------------------------------
O F
F F -Duseithreads
| +--------- -DDEBUGGING
+----------- no debugging


Locally applied patches:
SMOKE57630fb62d6f2d2f3415550c56dc3a3c07c4bf37

Failures: (common-args) none
[default] -DDEBUGGING
../cpan/IPC-Cmd/t/01_IPC-Cmd.t..............................FAILED
20
Non-zero exit status: 1

[default] -Duseithreads
[default] -DDEBUGGING -Duseithreads
../t/op/taint.t.............................................FAILED
800

Compiler messages(MSWin32):
RealPPPort.xs(1864) : warning C4101: 'len' : unreferenced local variable
Base64.xs(394) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
Base64.xs(396) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
POSIX.xs(2003) : warning C4244: '=' : conversion from 'NV' to 'IV', possible loss of data
d:\smoke\perl\blead\build\ext\posix\posix.c(2496) : warning C4700: uninitialized local variable 'RETVAL' used
d:\smoke\perl\blead\build\ext\posix\posix.c(2808) : warning C4700: uninitialized local variable 'RETVAL' used
d:\smoke\perl\blead\build\ext\posix\posix.c(2836) : warning C4700: uninitialized local variable 'RETVAL' used
d:\smoke\perl\blead\build\ext\posix\posix.c(2866) : warning C4700: uninitialized local variable 'RETVAL' used
--
Report by Test::Smoke v1.53 build 1374 running on perl 5.10.0
(Reporter v0.050 / Smoker v0.045)
Father Chrysostomos
2014-09-01 16:28:10 UTC
Permalink
Post by George Greer
[default] -Duseithreads
[default] -DDEBUGGING -Duseithreads
../t/op/taint.t.............................................FAILED
800
It's inconvenient for me to go digging through the logs. Could some-
one with Windows run './perl -Ilib t/op/taint.' and post the output?
Jarkko Hietaniemi
2014-09-01 17:30:10 UTC
Permalink
Post by Father Chrysostomos
Post by George Greer
[default] -Duseithreads
[default] -DDEBUGGING -Duseithreads
../t/op/taint.t.............................................FAILED
800
It's inconvenient for me to go digging through the logs. Could some-
one with Windows run './perl -Ilib t/op/taint.' and post the output?
The failures I'm getting from a reasonably fresh (last night) build are:

# Failed test 1 - at t/op/taint.t line 145

# got undef

# expected "1\n"

# Failed test 393 - Exited with status -1 at t/op/taint.t line 1045

# got "-1"

# expected "0"

# Failed test 397 - at t/op/taint.t line 1064
Father Chrysostomos
2014-09-01 19:49:38 UTC
Permalink
Post by Jarkko Hietaniemi
Post by Father Chrysostomos
It's inconvenient for me to go digging through the logs. Could some-
one with Windows run './perl -Ilib t/op/taint.' and post the output?
# Failed test 1 - at t/op/taint.t line 145
# got undef
# expected "1\n"
# Failed test 393 - Exited with status -1 at t/op/taint.t line 1045
# got "-1"
# expected "0"
# Failed test 397 - at t/op/taint.t line 1064
But 800 is passing for you?

Those failures are not the same as the smokers'.

Did you compile with threads?
Jarkko Hietaniemi
2014-09-01 22:12:51 UTC
Permalink
Post by Father Chrysostomos
But 800 is passing for you?
AFAICT, yes.
Post by Father Chrysostomos
Those failures are not the same as the smokers'.
Did you compile with threads?
The default for Win32 is threads. (I learned this only today myself.)
Jarkko Hietaniemi
2014-09-02 01:03:10 UTC
Permalink
Post by Father Chrysostomos
Post by Jarkko Hietaniemi
Post by Father Chrysostomos
It's inconvenient for me to go digging through the logs. Could some-
one with Windows run './perl -Ilib t/op/taint.' and post the output?
# Failed test 1 - at t/op/taint.t line 145
# got undef
# expected "1\n"
# Failed test 393 - Exited with status -1 at t/op/taint.t line 1045
# got "-1"
# expected "0"
# Failed test 397 - at t/op/taint.t line 1064
But 800 is passing for you?
Those failures are not the same as the smokers'.
Did you compile with threads?
From George Greer's logs:

Log says:

# Failed test 800 - tainted constant as logop condition should not
prevent "use" at op/taint.t line 2326
# got undef
# expected "122669\n"

If you need more information I can do a build and run the test.
Father Chrysostomos
2014-09-02 05:20:46 UTC
Permalink
Post by Jarkko Hietaniemi
# Failed test 800 - tainted constant as logop condition should not
prevent "use" at op/taint.t line 2326
# got undef
# expected "122669\n"
Thank you. You saved me some time.
Post by Jarkko Hietaniemi
If you need more information I can do a build and run the test.
Yes, that would be helpful.

And if you can get it to fail, then please try the sprout/taint
branch, or apply the commit at the tip of that branch to blead and
test that. Thank you.
Jarkko Hietaniemi
2014-09-02 10:52:17 UTC
Permalink
Post by Father Chrysostomos
Post by Jarkko Hietaniemi
# Failed test 800 - tainted constant as logop condition should not
prevent "use" at op/taint.t line 2326
# got undef
# expected "122669\n"
Thank you. You saved me some time.
Post by Jarkko Hietaniemi
If you need more information I can do a build and run the test.
Yes, that would be helpful.
Oh, sorry, that was cut-and-paste from George. I have no access to his
Win32, I just asked him for the failure details.
Post by Father Chrysostomos
And if you can get it to fail, then please try the sprout/taint
branch, or apply the commit at the tip of that branch to blead and
test that. Thank you.
Father Chrysostomos
2014-09-03 05:38:36 UTC
Permalink
Post by Jarkko Hietaniemi
Post by Father Chrysostomos
Post by Jarkko Hietaniemi
If you need more information I can do a build and run the test.
Yes, that would be helpful.
Oh, sorry, that was cut-and-paste from George. I have no access to his
Win32, I just asked him for the failure details.
I'll just go ahead and apply my patch to blead and see if the fail-
ures go away.

(Just a moment....)

OK, it's in as eaff586.

Loading...