Bug#1056238: gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity
On 2023-11-23 12:22:05 +0100, Matthias Klose wrote:
> Control: tags -1 + moreinfo
>
> I'm not looking into that, CCing the ports maintainers. Sure, we can
> disable running the tests on mips64el.
It used to be no problem while the faster mips64el buildds were
available. But currently we only have the slow ones, where the tests
timeout.
Best
Sebastian
>
> On 19.11.23 11:18, Sebastian Ramacher wrote:
> > Source: gcc-13
> > Version: 13.2.0-6
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the past)
> > X-Debbugs-Cc: sramacher@debian.org
> >
> > https://buildd.debian.org/status/fetch.php?pkg=gcc-13&arch=mips64el&ver=13.2.0-6&stamp=1700351970&raw=0
> >
> > === libstdc++ Summary for unix ===
> >
> > # of expected passes 3886
> > # of expected failures 43
> > # of unsupported tests 139
> > Running target unix/-fstack-protector
> > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
> > Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> > Using /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file.
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp ...
> > FAIL: libstdc++-abi/abi_check
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ...
> >
> > === libstdc++ Summary for unix ===
> >
> > # of expected passes 158
> > # of unexpected failures 1
> > # of unresolved testcases 1
> > Running target unix/-fstack-protector
> > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
> > Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> > Using /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file.
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp ...
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ...
> >
> > === libstdc++ Summary for unix ===
> >
> > # of expected passes 3689
> > # of unexpected failures 1
> > # of expected failures 37
> > # of unsupported tests 186
> > Running target unix/-fstack-protector
> > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
> > Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> > Using /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file.
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
> > Running /<<PKGBUILDDIR>>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
> >
> > testsuite still running ...
> >
> > E: Build killed with signal TERM after 150 minutes of inactivity
> >
> >
> > Cheers
>
--
Sebastian Ramacher
Reply to: