-
-
Notifications
You must be signed in to change notification settings - Fork 636
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
Run contrib tests with unit tests and integration tests for fewer CI delays #7709
Run contrib tests with unit tests and integration tests for fewer CI delays #7709
Conversation
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.
Cool! I think the bottleneck are still the integration tests, so this change is cool :)
The contrib folders have these, but we don't want to run them.
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.
Thanks!
This fails due to running contrib unit tests with |
Closing in favor of #7845. This solution is now out of sync with master as well. If we wanted to move forward with this approach, we should start by getting chroot to work for contrib. |
Makes for a faster failure if the core integration tests fail
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.
Now ready for review.
This PR means that the unit tests will take even longer :/ @blorente and I discussed creating our own manual shards for unit tests: one to run V2 and one to run V1 + contrib + ci.sh -l
. I punted on that work to do in a followup PR.
@@ -27,18 +27,9 @@ Usage: $0 (-h|-2fxbkmrjlpuneycitzsw) | |||
-j run core jvm tests | |||
-l run internal backends python tests | |||
-p run core python tests | |||
-u SHARD_NUMBER/TOTAL_SHARDS |
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.
This should have been removed from #7724.
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.
Thanks for the review John!
Problem
The contrib shards consistently are the blocker for CI runs because they appear near the end of the shards.
While discussing options to fix this, we realized that there is no compelling reason for the contrib folder to have its own dedicated shard(s). Instead, it would be valuable to use the split between unit tests vs. integration tests with the contrib code too.
Solution
Merge contrib tests into the unit tests and integration tests shards.
Result
The unit tests and integration tests shards will take slightly longer, but we will no longer be blocked by contrib at the end of the run.