diff options
author | Todd Gamblin <tgamblin@llnl.gov> | 2020-05-08 23:04:07 -0700 |
---|---|---|
committer | Todd Gamblin <tgamblin@llnl.gov> | 2020-05-09 00:56:18 -0700 |
commit | 7b8e5c89999621d3e036e52998a541c3a34e8fd0 (patch) | |
tree | e7a079e30870a95aa713b5c6e899f8407b8ad423 /.mailmap | |
parent | 5883e9df53258f7fe32cbf76f14abe9e42dfeebc (diff) | |
download | spack-7b8e5c89999621d3e036e52998a541c3a34e8fd0.tar.gz spack-7b8e5c89999621d3e036e52998a541c3a34e8fd0.tar.bz2 spack-7b8e5c89999621d3e036e52998a541c3a34e8fd0.tar.xz spack-7b8e5c89999621d3e036e52998a541c3a34e8fd0.zip |
bugfix: don't use sys.stdout as a default arg value (#16541)
After migrating to `travis-ci.com`, we saw I/O issues in our tests --
tests that relied on `capfd` and `capsys` were failing. We've also seen
this in GitHub actions, and it's kept us from switching to them so far.
Turns out that the issue is that using streams like `sys.stdout` as
default arguments doesn't play well with `pytest` and output redirection,
as `pytest` changes the values of `sys.stdout` and `sys.stderr`. if these
values are evaluated before output redirection (as they are when used as
default arg values), output won't be captured properly later.
- [x] replace all stream default arg values with `None`, and only assign stream
values inside functions.
- [x] fix tests we didn't notice were relying on this erroneous behavior
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions