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

[d16-9] [CI][VSTS] Do not step over success statuses in rebuilds. #10566

Conversation

vs-mobiletools-engineering-service2
Copy link
Collaborator

This happens just in very few cases when we have two builds for the same hash in different branches. This is not common, except when we are branching. A cherry-pick does create a new hash yet same message and change, therefore cherry-picks have never been an issue, just branching without new commits.

Backport of #10565

@vs-mobiletools-engineering-service2
Copy link
Collaborator Author

❌ Tests failed on Build ❌

Tests failed on Build.

Test results

1 tests failed, 174 tests passed.

Failed tests

  • introspection/watchOS 32-bits - simulator/Debug (watchOS 3.2): Failed

Pipeline on Agent XAMBOT-1101'

@dalexsoto
Copy link
Member

Failure is unrelated to PR

introspection/watchOS 32-bits - simulator/Debug (watchOS 3.2): Failed

@dalexsoto dalexsoto merged commit 11a1c24 into dotnet:d16-9 Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported not-notes-worthy Ignore for release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants