Skip to content

Commit

Permalink
increase test timeout for slow runners [skip ci] (#1085)
Browse files Browse the repository at this point in the history
  • Loading branch information
@baentsch
baentsch authored Sep 5, 2021
1 parent eb9ca19 commit 74867b6
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions .circleci/config.yml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -353,12 +353,16 @@ workflows:
- linux_oqs:
name: constant-time-x64
context: openquantumsafe
# some algorithms _are_ slow:
no_output_timeout: 45m
CONTAINER: openquantumsafe/ci-ubuntu-bionic-x86_64:latest
CMAKE_ARGS: -DOQS_OPT_TARGET=generic -DCMAKE_BUILD_TYPE=Debug -DOQS_ENABLE_TEST_CONSTANT_TIME=ON
PYTEST_ARGS: --numprocesses=auto -k 'test_constant_time'
- linux_oqs:
name: constant-time-x64-extensions
context: openquantumsafe
# some algorithms _are_ slow:
no_output_timeout: 45m
CONTAINER: openquantumsafe/ci-ubuntu-bionic-x86_64:latest
# building for haswell to avoid generating instructions that valgrind cannot currently handle
# TODO: Re-enable target=auto if/when valgrind supports beyond AVX2:
Expand Down

1 comment on commit 74867b6

@baentsch
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dstebila : Ouch, the merge was too fast: This CCI option only is permitted on run not on jobs. So, can we please throw out/revert this commit again? Also, we already set a no_output_timeout of 1h -- then I reall don't know how/why the Rainbow constant runtime tests failed in the weekly test run (ideas welcome).

Please sign in to comment.