Skip to content

Conversation

@brettfo
Copy link
Member

@brettfo brettfo commented May 22, 2019

Add steps to publish test results that were inadvertently lost when PR builds migrated from .vsts-ci.yaml to azure-pipelines.yml.

Initial attempt also includes a hijacked test to force a failure. See comment below for details about logs, hijacked tests have been restored.

@brettfo brettfo force-pushed the pr-test-logs branch 4 times, most recently from 53cd59a to 8508045 Compare May 22, 2019 23:28
@brettfo brettfo requested a review from dsyme May 22, 2019 23:32
@brettfo brettfo force-pushed the pr-test-logs branch 2 times, most recently from 4af1d59 to a2f0240 Compare May 23, 2019 02:20
@brettfo
Copy link
Member Author

brettfo commented May 23, 2019

If fsharpqa fails then all log files (*.env, *.log, *.lst) are added as an artifact titled 'Windows Release testFSharpQA test logs' for examination.

If an NUnit test fails, the appropriate information is reported in the 'Tests' tab:

image

@brettfo brettfo changed the title [WIP] publish test results publish test results May 23, 2019
@brettfo brettfo merged commit 23d0f4d into dotnet:master May 23, 2019
@brettfo brettfo deleted the pr-test-logs branch May 23, 2019 05:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant