-
Notifications
You must be signed in to change notification settings - Fork 2k
[BLD]: move GC proptest into separate job #4794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
77d9364 to
40215b5
Compare
40215b5 to
ee545fe
Compare
|
Separate Slow GC Integration Test into Distinct CI Job to Speed Up Rust Integration Tests This PR restructures the Rust CI integration test workflow by isolating the slow 'test_k8s_integration_garbage_collection' test into its own matrix job using a new nextest profile ( Key Changes: Affected Areas: This summary was automatically generated by @propel-code-bot |
eculver
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These partitioning options are a little magical to me, but I'll take your word for it.
## Description of changes The wall time of Rust integration tests is now ~18m, down from ~22m. ## Test plan _How are these changes tested?_ - [x] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust
Description of changes
The wall time of Rust integration tests is now ~18m, down from ~22m.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rust