[do not merge] travis gdb parachute for #9825 #9851

pull laanwj wants to merge 7 commits into bitcoin:master from laanwj:2017_02_travisissue changing 3 files +26 −17

laanwj commented at 11:10 AM on February 24, 2017: member

Hopefully this can give us a useful traceback.
gdb parachute df6bbb25d1
laanwj added the label Tests on Feb 24, 2017
paveljanik commented at 11:31 AM on February 24, 2017: contributor

Looks like gdb is missing

fixups

- actually install gdb
- remove unnecessary travis runs
- apply bt to all threads

5dae4674d3

laanwj commented at 11:32 AM on February 24, 2017: member

yep, added that now
laanwj commented at 11:52 AM on February 24, 2017: member

Hm, to make this iterate faster, could change the builds to only build test_bitcoin. Let's just wait for this to finish first to see if anything else needs changing.
build only test_bitcoin
This should be somewhat faster.
342167ee38
laanwj commented at 12:02 PM on February 24, 2017: member

Ugh the no-wallet build was rebuilding all dependencies (including Qt). Cancelled that. Hopefully it won't do that every time. Edit: it did, so removed that one

remove nowallet build

For some reason, travis wants to rebuild all dependencies for this one.
Just skip it. The issue comes up in the other Linux builds anyhow.

678525bcf5

laanwj force-pushed on Feb 24, 2017

disable ccache

Maybe it's a compiler non-determinacy issue

840ef783d4

quit gdb with error code

It's still nice to be able to detect errors when they happen.

6d7a789fb5

laanwj commented at 9:06 AM on February 25, 2017: member

Looks like I caught it in the act now:

test_bitcoin: /home/travis/build/bitcoin/bitcoin/depends/i686-pc-linux-gnu/share/../include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
Program received signal SIGABRT, Aborted.
Thread 41 (Thread 0xec3a7b40 (LWP 21516)):
Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0x24: 
[#0](/bitcoin-bitcoin/0/)  0xf7fdacd9 in ?? ()
Error while running hook_stop:
Cannot access memory at address 0x24
0xf7fdacd9 in ?? ()

Unfortunately, the traceback is everything but useful.

Worker information of the crashing Travis workers. Maybe this could come in handy for correlation:

hostname: travis-worker-gce-org-prod-6:52eb7685-63e5-4b02-b480-24b9089297d5
version: v2.6.2 https://github.com/travis-ci/worker/tree/fdccca4efd347ebc889baae641ccbf55bb871d19
instance: testing-gce-fbe09602-6023-4334-b7c2-d8f40f385fe6:travis-ci-connie-trusty-1480957854
startup: 21.207678721s

hostname: travis-worker-gce-org-prod5-8:2950a066-b261-4d21-89b7-73adc0a84994
version: v2.6.1-2-g9fbf704 https://github.com/travis-ci/worker/tree/9fbf704a6a755301e6b86b28a87b3f0636e502a8
instance: testing-gce-b04910e2-2d79-4567-9d00-10469e136a81:travis-ci-connie-trusty-1480957854
startup: 21.164956151s

Crank up debug information to the max

Without touching env variables, as that triggers a full rebuild of deps.

2eac75f95a

laanwj commented at 3:06 PM on February 27, 2017: member

I'm slightly optimistic that this has been solved by #9875. If the bug rears its head again I'll reopen.
laanwj closed this on Feb 27, 2017
ryanofsky commented at 4:14 PM on February 27, 2017: member

Maybe another thing to add would be --loglevel=all to test_bitcoin http://www.boost.org/doc/libs/1_63_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/log_level.html
DrahtBot locked this on Sep 8, 2021

Contributors

Labels