-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Disable failing jobs in PR testing. #1283
Disable failing jobs in PR testing. #1283
Conversation
@sandreenko what are all the |
Thanks for catching this. Probably that was a miss click, I do not remember adding them. Sometimes GitHub does strange things when you use browser's "go back" while opening a PR/issue. |
@@ -171,7 +171,7 @@ jobs: | |||
jobTemplate: /eng/pipelines/coreclr/templates/crossgen-comparison-job.yml | |||
buildConfig: checked | |||
platforms: | |||
- Linux_arm | |||
# - Linux_arm Return this when https://github.com/dotnet/runtime/issues/1282 is fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest increasing the timeout, instead of disabling the submission entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, thanks
Did not help, if we are talking about a temporary solution, can we disable the whole coreclr/pr pipeline? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the current state of affairs, I suggest merging in the 1st version of your PR i.o.w. disabling the two offending PR tests (Windows ARM32 and Crossgen comparison) as upping the timeout for the Crossgen comparison test as suggested by @jashook doesn't seem to be helping. I'll follow up on Monday with Ilya based on Jarret's comments towards the ARM queue and we can re-enable the tests once the queues have been configured properly. Thanks for making this change!
The log looks very strange.
|
Feel free to merge disabling the job to get to a good state, but this looks like it should be investigated. |
@jashook - I was originally under the impression that this is a secondary effect of the Helix run timing out so that the result scan fails to find its output data. If this assumption is incorrect, we definitely need to figure out what's going on. Actually, even if my understanding is correct, we should improve the logging to make the cause more obvious, I completely agree this is pretty cryptic and hard to action on. |
I do not disagree with it being cryptic, but the thing that has me confused is that it looks like the jobs finished. See:
|
I just do not know what the time that they finished was, and what how long it took to do whatever it was doing after that point. |
ec87b06
to
8211f08
Compare
@@ -111,7 +111,7 @@ jobs: | |||
platforms: | |||
- OSX_x64 | |||
- Linux_x64 | |||
- Linux_arm | |||
# - Linux_arm return this when https://github.com/dotnet/runtime/issues/1097 is fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this commented out. The comment beside it seems to be for Windows am but this is Linux arm
Fixes dotnet#1283. Also, small improvement wrt warnings and IsGenericType.
Disable PR testing jobs that are failing.
Revert when #1097 and #1282 are fixed.
Question: how can we match yml names to ADO names nowadays? I guess that
Checked JIT test executions
matches to "CoreCLR Pri0 Test Run checked", but there are no common words there.