-
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
Crossgen2 failure: tracing/eventpipe/reverse/reverse/reverse.sh #35270
Comments
failed again in job: runtime-coreclr outerloop 20200510.5 failed test: tracing/eventpipe/reverse/reverse/reverse.sh Error message
|
Happened again OSX build; console log. |
I am guessing the CI failures are not related to crossgen2, and possibly a different issue which should be assigned to the Tracing team. |
@mangod9 do you know who the tracing team would be so that we can loop them in? |
@tommcdon ^^ |
Taking a look |
Couldn't repro locally, but I created a PR to enhance this suite of tests. I'm hoping that if the tests fail again, we should be able to easily identify what went wrong. The |
Rereading the logs posted above, I think there are actually 3 different issues in this one issue. The initial comment at the top has error output from crossgen2 and looks as though crossgen failed to R2R the test binary. The other 2 errors appear to be a timeout and an exception that should have more information if they happen again under the PR I linked. |
Yeah correct, the original crossgen2 issue is unrelated and shouldnt be affecting CI. If this repros a new issue should be created so they could be tracked separately. Thx. |
Happened again: https://helix.dot.net/api/2019-06-17/jobs/24babe78-7797-4a21-b7d0-6157ef54bf62/workitems/PayloadGroup0/console Any update on this? |
@safern I took a look at the log and it looks like something timed out the wait for a reverse server connection. The timeout was 30 seconds I believe. I'm going to spin this into a different issue, as I think there are too many things being tracked in here. I'll post any findings in the new issue. |
Thanks for creating a new issue @josalem. I have moved the |
This test has run fine in Crossgen2 runs so I believe we fixed whatever CG2-specific issue we had some time ago. |
failed in job: runtime-coreclr crossgen2 20200420.1
Error message
The text was updated successfully, but these errors were encountered: