Bug 13676

Summary: selftest test_gdb_hardlink_debug failure
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Richard Purdie <richard.purdie>
Component: coreAssignee: Randy MacLeod <randy.macleod>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Medium+ CC: meta.mr.watcher, meta.watcher, randy.macleod
Version: 3.0   
Target Milestone: 3.2 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Richard Purdie 2019-12-04 13:48:06 UTC
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/844

2019-12-04 02:31:38,889 - oe-selftest - INFO - ======================================================================
2019-12-04 02:31:39,008 - oe-selftest - INFO - FAIL: package.PackageTests.test_gdb_hardlink_debug (subunit.RemotedTestCase)
2019-12-04 02:31:39,008 - oe-selftest - INFO - ----------------------------------------------------------------------
2019-12-04 02:31:39,008 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/oe-selftest/build/meta/lib/oeqa/selftest/cases/package.py", line 150, in test_gdb_hardlink_debug
    self.fail('GDB %s failed' % binary)
  File "/opt/poky/3.0/sysroots/x86_64-pokysdk-linux/usr/lib/python3.7/unittest/case.py", line 693, in fail
    raise self.failureException(msg)
AssertionError: GDB /usr/bin/hello1 failed

At the very least we need to improve this failure output to aid debugging what really went wrong.
Comment 1 Ross Burton 2019-12-04 21:26:47 UTC
Further context from the log:

2019-12-03 16:22:31,628 - oe-selftest - ERROR - GDB result:
0: Reading symbols from /usr/bin/hello1...
Reading symbols from /usr/bin/.debug/hello1...
(gdb) Breakpoint 1 at 0x1050: file /usr/include/bits/stdio2.h, line 107.
(gdb) Starting program: /usr/bin/hello1 
<<< run_serial(): command timed out after 60 seconds without output >>>

Considering hello1 is just a printf() statement, was this machine massively loaded at the time?
Comment 3 Randy MacLeod 2020-08-27 10:28:16 UTC
Duplicate so close the this one as it is more recent.

*** This bug has been marked as a duplicate of bug 13123 ***