Skip to content

Use XHarness' diagnostics output to detect infrastructure issues#8139

Merged
premun merged 11 commits intodotnet:mainfrom
premun:prvysoky/python-ftw
Nov 5, 2021
Merged

Use XHarness' diagnostics output to detect infrastructure issues#8139
premun merged 11 commits intodotnet:mainfrom
premun:prvysoky/python-ftw

Conversation

@premun
Copy link
Member

@premun premun commented Nov 5, 2021

Instead of relying on the work item to request retry/reboot, we do it in the SDK at the end of the job while reading the diagnostics.json file generated by XHarness.
This will transparently work for any number of XHarness commands executed during the work item and can be a single place for the logic. It also unifies the logic we had duplicated over the .ps and .sh files.
The user then doesn't need to categorize or react on failed XHarness commands in any way.

We still allow the users to request retry/reboot using the .dotfiles but it should not be necessary.

Resolves #8109

Copy link
Member

@MattGal MattGal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wow this has evolved a lot since I last looked at it :)

@premun
Copy link
Member Author

premun commented Nov 5, 2021

Yeah! Piece by piece, edge case by edge case. I think this change will bring a lot of good things for maintenance

@premun premun merged commit ebeeb85 into dotnet:main Nov 5, 2021
@premun premun deleted the prvysoky/python-ftw branch November 5, 2021 18:26
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.

Create a way to share XHarness Helix SDK functionality

2 participants