Skip to content
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

Add debug traces to failing test steps #19145

merged 2 commits into from Apr 12, 2019


None yet
1 participant
Copy link

commented Apr 12, 2019

Currently, if one of the steps executed during the tests returns a non-zero exit code, we fail with the following message:

##[error]Cmd.exe exited with code '1'.
##[section]Finishing: Run tests

Normally, since the failing step prints an error, it's easy to identify which step failed, but in other situations (like this test build) it's hard to identify which step is failing.

For now this only prints the step that caused the failure (which is the only thing we can get at the moment), but we can use this to print additional information in the future.

This may give us some information to identify the root cause of #19089

@rafeca rafeca merged commit 74308fb into master Apr 12, 2019

2 checks passed

Atom Pull Requests #20190412.3 succeeded
continuous-integration/appveyor/pr AppVeyor build succeeded

@rafeca rafeca deleted the add-traces-to-test branch Apr 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.