Ci: run entry tests first #2175
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #2175 +/- ##
==========================================
- Coverage 84.08% 83.84% -0.24%
==========================================
Files 90 90
Lines 10303 10303
==========================================
- Hits 8663 8639 -24
- Misses 1640 1664 +24 |
rafacanton
approved these changes
Mar 21, 2025
moe-ad
approved these changes
Mar 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix recent surge in instability for
test_apply_context_remote.Edit: after running the CI on this branch several times, it looks like the test does not fail anymore.
@moe-ad for context: the tests in
test_entry.pyare meant to test server start configurations and are marked as having to run first. Running them in parallel with other test modules probably creates conflicts. This is something to be investigated on our side but in the meantime I am separating them once again and running them first.