-
Notifications
You must be signed in to change notification settings - Fork 239
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
Improve CI jobs split #1210
Improve CI jobs split #1210
Conversation
This is more or less a straight port with slightly improved control flow. All tests are still built and run serially.
This build was failing from the start.
If a debug assertion or error occurs, this dialog blocks execution of the CI.
Have to hack catch2.hpp a bit so that it outputs ANSI colour sequence.
@@ -44,94 +44,96 @@ namespace | |||
} | |||
} | |||
|
|||
TEST_CASE("disconnected,handler") | |||
TEST_CASE("disconnected,handler,1") |
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.
What's the ,1
for?
|
||
{ | ||
auto async = Action(); | ||
TEST_CASE("disconnected,handler,2") |
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.
Oh, you flattened these tests...
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Much nicer output - thanks!!
This basically rewrites the CI jobs based on the original
build_test_all.cmd
but split the steps into different jobs so any failures will be easier to pinpoint. This also allows the tests to be built and run in parallel, which can save about 5 minutes of full run time.One thing to note is that the nuget test build seems to be failing even on the initial GHA workflow. This failure was hidden before because
build_test_all.cmd
did not detect the build error. Now that it is exposed, I have added a hack to purposely ignore the failure (instead only emit a warning) because I don't know how to fix it properly.