It seems odd to have travis related workarounds in the general ci config files. Fix that oddity by moving the travis related workarounds to the travis yaml file.
For unexplained reasons, this should also work around and thus close #19171
It seems odd to have travis related workarounds in the general ci config files. Fix that oddity by moving the travis related workarounds to the travis yaml file.
For unexplained reasons, this should also work around and thus close #19171
Has anyone an explanation?
32 | @@ -33,9 +33,7 @@ if [ -z "$NO_DEPENDS" ]; then 33 | else 34 | SHELL_OPTS="CONFIG_SHELL=" 35 | fi 36 | - # Temporary workaround for https://github.com/bitcoin/bitcoin/issues/16368 37 | - python3 -c 'import time; [print(".") or time.sleep(500) for _ in range(4)]' &
I believe the issue was that this print did nothing, because by default flush=False (see https://docs.python.org/3.8/library/functions.html#print ).
Testing locally and on travis x86, it did always happen to print, just not on travis arm.
20 | @@ -21,8 +21,6 @@ if [ -n "$USE_VALGRIND" ]; then 21 | END_FOLD 22 | fi 23 | 24 | -bash -c "${CI_WAIT}" & # Print dots in case the tests take a long time to run 25 | -
This deletion is also necessary?
CI_WAIT no longer exists and this should be a no-op
ACK fa7166759789c1282609ff3ab2e80d4f70910a9f, I have reviewed the code and it looks OK, I agree it can be merged.