Adds trouble shooting info for #1627

[rominator1983]

Description

Adds trouble shooting information for the case discussed in #1627

Related Issue

#1627

Motivation and Context

Get more information when this case happens

How Has This Been Tested?

Unit tests have been run. It is not clear how this scenario can be created so it's not possible at the moment to create a unit test

Screenshots (if appropriate):

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation. => no
• I have updated the documentation accordingly. => no
• I have added tests to cover my changes. => no. See above
• All new and existing tests passed. => yes

[asbjornu]

I can't really see why the build is failing – I can't find the test that fails. Are you able to locate it?

[rominator1983]

I don't think that there are really single tests that fail. There are complete configurations like MacOS that fail while most configurations just work. I can check later.

Can you run the build on the current main? I think that this won't work either at the moment.

[arturcic]

I noticed the build recently got pretty unstable, especially the macOs agents, seems like there were some build agents updates that might affect the stability of the build, for now re-run of the failed jobs helps (sometimes couple of reruns)

[rominator1983]

Yeah tell me about it. We experience the same in other repositories. I think you restarted the checks? Thanks for that.

[mergify]

Thank you @rominator1983 for your contribution!

[arturcic]

🎉 This issue has been resolved in version 6.0.0-beta.2 🎉
The release is available on:

• GitHub Release
• Chocolatey Package
• .Net Global Tool

Your GitReleaseManager bot 📦🚀