(Sorry for the confusion, I accidentally used my company email. Please answer to this address).
Hi Aurelien! On 05/31/2016 04:13 PM, Aurelien Jarno wrote: >> ---------- >> XFAIL: wcsmbs/test-wcsncmp >> original exit status 1 >> wcsncmp simple_wcsncmp stupid_wcsncmp >> Didn't expect signal from child: got `Bus error' >> ---------- > > While the issue is real, this is not the reason while the package fails > to build from source. The test is marked as XFAIL as shown above. Ok, I see. I thought the problem would still trigger due to the unusual failure. > Thanks for submitting the patch upstream. Given the above, I think it is > better to wait for an answer from upstream before applying it. The test comes from Jose Marchesi who I know is gcc upstream, but I'm not sure about glibc. Jose, could you please comment on this? >> Please note: I was still getting some spurious test failures in >> rt/tst-mqueue5 >> due to timeouts. But those could also be a local issue which needs some >> further >> investiogation (might be related to TIMEOUTFACTOR in debian/build.mk). > > TIMEOUTFACTOR just increases the timeout, if you don't specify it, the > test will just fail faster. Hmm, then I'm a bit out of ideas. The idea came from Nick Alcock, so maybe he can comment on this as well. What's more strange is that glibc_2.22-7 actually happened to build fine, with the tests enabled [1]. All later builds failed again. Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.22-7&stamp=1462606555 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
