Separate build and test in github workflows. #432
Merged
Conversation
This file contains 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
smoser
force-pushed
the
fix/build-separate-from-test
branch
from
e1001da to
43c3e5f
Compare
Currently the "Build and test" step of the c-i workflow does both build a binary and test the binary. Make 2 sections 'Build' and 'Test'. This way you can know which of the two sections failed, and also see how long each portion took. Signed-off-by: Scott Moser <smoser@brickies.net>
smoser
force-pushed
the
fix/build-separate-from-test
branch
from
43c3e5f to
991e293
Compare
Codecov Report
@@ Coverage Diff @@
## main #432 +/- ##
=======================================
Coverage 12.12% 12.12%
=======================================
Files 44 44
Lines 5433 5433
=======================================
Hits 659 659
Misses 4657 4657
Partials 117 117 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Currently the "Build and test" step of the c-i workflow does both build a binary and test the binary. Make 2 sections 'Build' and 'Test'. This way you can know which of the two sections failed, and also see how long each portion took.
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.