Father Chrysostomos wrote on 2013-08-12:
George Greer ‘wrote’:
../t/re/pat.t...FAILED
228-231
../t/op/taint.t.FAILED
592
OK, so which of my commits caused these? They make no sense to
George Greer âwroteâ:
../t/re/pat.t...FAILED
228-231
../t/op/taint.t.FAILED
592
OK, so which of my commits caused these? They make no sense to me.
I will investigate which commit caused the breakages, but in the
meantime here is the op/taint.t dump output, confirming that ${^TAINT}
has indeed been written to:
C:\Dev\Git\perl\t..\perl harness op\taint.t
op/taint.t .. 1/797 SV = PVMG(0x7afa7c) at 0x7d12cc
REFCNT = 1
FLAGS =
The tests fail in commit 3805b5fb04f8819edfb6bd5256d5eefd7b23e730 (and
pass in the previous commit,
0ffdaf1a47312f763d4610e9ec65c24561e957a5).
On 12 August 2013 22:18, Steve Hay steve.m@googlemail.com wrote:
I will investigate which commit caused the breakages, but in the
meantime here is
Steve Hay wrote:
t/re/pat.t, t/re/pat_thr.t, t/op/taint.t and
dist/threads-shared/t/clone.t all fail (in a threaded build) at
c9f1f591ba751b24222b22f1f3a6799db0ab0d1b (Read-only COWs), the first
of your three merge commits.
Thank you. Can you tell which commit in the branch caused it?
What
Steve Hay wrote:
The tests fail in commit 3805b5fb04f8819edfb6bd5256d5eefd7b23e730
Thank you! clang is being âhelpfulâ and preventing me from spotting
errors like this. Does the sprout/taint-failure branch make the fail-
ures go away?
On 12 August 2013 23:54, Father Chrysostomos spr...@cpan.org wrote:
Steve Hay wrote:
The tests fail in commit 3805b5fb04f8819edfb6bd5256d5eefd7b23e730
Thank you! clang is being ‘helpful’ and preventing me from spotting
errors like this. Does the sprout/taint-failure branch make the fail-
