Open carlosgmartin opened 2 hours ago
It looks like this might be caused by the test script terminating due to failures before any cleanup occurs (see https://github.com/google-deepmind/optax/pull/1068).
In any case, the test script should clean up after itself even if failures occur.
On a related note: The output of test.sh
is very verbose.
What do we think of dropping the -x flag from the line
set -xeuo pipefail
which is responsible for most of this verbosity?
Running tests modifies the file
.pylintrc
, by appending the lineRunning tests a second time yields numerous failures. An example of this is shown below:
The numerous failures appear only after
.pylintrc
has been modified. Reverting.pylintrc
to its original state, and then running tests again, results in the same output as the first run.It seems to me that running tests should not be modifying any tracked files (which subsequently have to be reverted or manually excluded from commits).