|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang) |
Date: | Fri, 26 Jun 2020 09:51:02 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 |
Follow-up Comment #45, bug #57591 (project octave): The following build on one of my buildbot systems failed: http://buildbot.octave.org:8010/#/builders/22/builds/516 I've been repeatedly running the test suite using this build for the last 8 hours or so and it hasn't failed once. I'm using while true ; do if nice -n 19 xvfb-run -a -s 'screen 0 640x480x24' make V=1 check ; then echo "OK $?" else echo "NOT OK: $?" break fi done I said earlier that I would set the default ulimit for the buildbots so that we would generate core files, but I'm not sure of the best way to do that. If I understand correctly, buildbot starts new shells to do each shell command step and I'd rather not have to add ulimit commands to each one. So it seems that a change like this should be made on the worker systems instead but I don't know what startup file to add the ulimit command to on the build worker system. Any ideas? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57591> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |