Summary: | =sys-devel/autogen-5.18.16 fails getopt.test and library.test if /var/tmp/portage is on tmpfs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paolo Pedroni <paolo.pedroni> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | slyfox |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | autogen-5.18.16:20190125-105209.log.gz |
Description
Paolo Pedroni
2019-01-25 12:45:14 UTC
Does 'dmesg' report why those tests were killed? 137 exit code is a SIGKILL. I wonder if it's kernel killing tests or testsuite itself. Tests pass for me in tmpfs. Looks like autogen test harness does it explicitly. I'll need a bit more debug info from test failure. If it's reliably reproducible for you can you run individual failing test with more debugging available? For example for 'FAIL: getopt.test' you can go to $ cd '/var/tmp/portage/sys-devel/autogen-5.18.16/work/autogen-5.18.16' and run it as $ autoopts/test $ bash -x ./getopt.test (In reply to Sergei Trofimovich from comment #2) > Looks like autogen test harness does it explicitly. > > I'll need a bit more debug info from test failure. If it's reliably > reproducible for you can you run individual failing test with more debugging > available? It is reliably reproducible. > > For example for > 'FAIL: getopt.test' > you can go to > $ cd '/var/tmp/portage/sys-devel/autogen-5.18.16/work/autogen-5.18.16' > and run it as > $ autoopts/test > $ bash -x ./getopt.test I will try. No sooner than friday, though, I'm busy with work ATM. |