This repository was archived by the owner on Sep 1, 2024. It is now read-only.
Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 9 commits
- 14 files changed
- 1 contributor
Commits on Jan 2, 2024
Commits on Mar 15, 2024
-
Use "new-style" pluggy hook wrapper
When all test failures are due to quarantined tests, we call pytest.exit() to force a successful exit. Newer versions of pluggy emit a `pluggy.PluggyTeardownRaisedWarning` warning due to using the "old-style" hook wrappers. This change switches to the new style, which eliminates the warning.
Commits on Mar 16, 2024
-
Check uploaded results in integration tests
These checks were unintentionally removed in a31066e.
-
Bump GitHub Actions versions to use Node.JS 20
Node.JS 16 actions are deprecated, leading to CI warnings.
-
A user reported an issue in which freezegun (specifically, the `@freeze_time()` decorator) was impacting the test start and end timestamps reported to Unflakable. It turns out that this issue was fixed in freezegun 1.2.2. This change adds a new test case and checks timestamp consistency for every test case.
Commits on Mar 27, 2024
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff pytest-0.1.7...pytest-0.2.0