Uh oh!
There was an error while loading. Please reload this page.
[Test] Collapse mono runtime tests into single builds using global-build-job template - #62863
Conversation
ghost
commented
Dec 15, 2021
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsThis PR changes the way mono is build and consumed for runtime test lanes. Instead of separate steps that build and publish artifacts, and other steps that download them, building and running will be done on one machine. This reduces the number of network connections required run the tests, and each of those is a potential source of failure. It does preclude the ability to share some build artifacts, but mono builds are fast. It also lets use remove the coreclr dependency on the effected mono lanes. Contributes to: #45521 Draft while I iron out issues in CI.
|
Uh oh!
There was an error while loading. Please reload this page.
|
Azure Pipelines failed to run 1 pipeline(s). |
1 similar comment
|
Azure Pipelines failed to run 1 pipeline(s). |
naricc
commented
Jan 4, 2022
/azp run runtime-manual |
e71cf46 to
8d7ce1dCompare9df2172 to
0afa6b9Compareghost
commented
Feb 28, 2022
Tagging subscribers to this area: @directhex Issue DetailsThis PR changes the way mono is build and consumed for runtime test lanes. Instead of separate steps that build and publish artifacts, and other steps that download them, building and running will be done on one machine. This reduces the number of network connections required run the tests, and each of those is a potential source of failure. It does preclude the ability to share some build artifacts, but mono builds are fast. It also lets use remove the coreclr dependency on the effected mono lanes. Contributes to: #45521 Draft while I iron out issues in CI. Also only moving hte osx_x64 lane for testing purposes.
|
3672749 to
5d1b06aCompareSamMonoRT
commented
May 9, 2022
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
149aee5 to
27573d9CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
trylek
left a comment
There was a problem hiding this comment.
LGTM modulo a few nits, thank you!
naricc
commented
Nov 19, 2022
Failures seem spurious. |
I am reviving this PR from a while ago.
This PR changes the way mono is build and consumed for runtime test lanes. Instead of separate steps that build and publish artifacts, and other steps that download them, building and running will be done on one machine.
This reduces the number of network connections required run the tests, and each of those is a potential source of failure. It does preclude the ability to share some build artifacts, but mono builds are fast.
It also lets use remove the coreclr dependency on the effected mono lanes.
There were a few tests that didn't run successfully with out the coreclr build for different reasons; I have excluded them in issues.targets for now and will investigate them individually as a follow up item.
mono-windows is still using the old path while I investigate some errors in the build.cmd script.
Contributes to: #45521
This PR only changes the ones in the runtime pipeline. Follow up PRs will change runtime-staging.