| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Thank you for opening the issue, #13767 is moving it elsewhere you'll probably need to rebase on it when it's merged. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks!
No worries about the rebase, I will handle it, along with a few minor changes. Out of abundance of caution I will also mark this a breaking change. The next release is 9.0 so that's OK :)
Sorry, something went wrong.
… string
Previously, if either env variable was defined, CI mode would be activated,
even if the variable was set to the empty string.
This had some unfortunate consequences:
* The easy and obvious method of setting those variables,
i.e. `CI="${OTHER_VAR}"`,
would not work,
because `$CI` would always end up being defined
even if `$OTHER_VAR` was undefined.
* The easy and obvious method of clearing those variables at runtime,
i.e. `CI="" pytest ...`,
would not work,
because again `$CI` would still be defined even though it was blank.
Now, at least one of those variables must be set to a non-empty string
in order to enabled CI mode.
Closes pytest-dev#13766
|
macos CI is down, I doubt it's relevant here, so force-merging. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Previously, if either $CI or $BUILD_NUMBER was defined, CI mode would be activated, even if the variable was set to the empty string. This had some unfortunate consequences:
Now, at least one of those variables must be set to a non-empty string in order to enable CI mode.
Closes #13766