-
Notifications
You must be signed in to change notification settings - Fork 2.2k
ci: classify flow unit test #3346
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
Codecov Report
@@ Coverage Diff @@
## master #3346 +/- ##
==========================================
+ Coverage 88.77% 89.79% +1.02%
==========================================
Files 152 152
Lines 10820 10820
==========================================
+ Hits 9605 9716 +111
+ Misses 1215 1104 -111
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Latency summaryCurrent PR yields:
Breakdown
Backed by latency-tracking. Further commits will update this comment. |
can you elaborate a bit in the thread on how we classify and how could we put future flow test into different folders? |
Sure!
|
Classify flow unit test and break down the unit test folder, to leverage parallel CI implementation.
tests/unit/flow
tests/unit/flow-construct
tests/unit/flow-orchestrate
tests/unit/flow-example