"H.Merijn Brand" wrote in perl.daily-build.reports : > 29220 Configuration (common) none > ----------- --------------------------------------------------------- > O O O O O F > O O O O O F -Duse64bitint > O O O O O F -Duselongdouble > O O O O O F -Dusemorebits
Do those failures mean that Dave's fix was incomplete, and should we reinstate a workaround similar at patches 29182 and 29184 ? (note that I don't reproduce the failures on Linux, so I'd appreciate more details) > O O O O O O -Duseithreads > O O O O O O -Duseithreads -Duse64bitint > O O O O O O -Duseithreads -Duselongdouble > O O O O O O -Duseithreads -Dusemorebits >| | | | | +- LC_ALL = en_US.utf8 -DDEBUGGING >| | | | +--- PERLIO = perlio -DDEBUGGING >| | | +----- PERLIO = stdio -DDEBUGGING >| | +------- LC_ALL = en_US.utf8 >| +--------- PERLIO = perlio > +----------- PERLIO = stdio > > Locally applied patches: > DEVEL > SMOKE29220 > > Failures: (common-args) none > [en_US.utf8] -DDEBUGGING > [en_US.utf8] -DDEBUGGING -Duse64bitint > [en_US.utf8] -DDEBUGGING -Duselongdouble > [en_US.utf8] -DDEBUGGING -Dusemorebits > ../lib/strict.t.........................FAILED 84-85 > ../lib/subs.t...........................FAILED 2 > ../lib/warnings.t.......................FAILED 123-124 138 145-147 155 > 158 310 > 455 499-500 > ../t/run/fresh_perl.t...................FAILED 48
