Skip to content
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

Jobs on Windows fail without logs sometimes #1776

Closed
tysonite opened this issue Oct 9, 2020 · 4 comments
Closed

Jobs on Windows fail without logs sometimes #1776

tysonite opened this issue Oct 9, 2020 · 4 comments
Labels
investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Windows

Comments

@tysonite
Copy link

tysonite commented Oct 9, 2020

Sometimes, jobs on Windows fail without logs:
image

Examples:

This might be related to similar issues on macOS: #841 or #736

@dibir-magomedsaygitov dibir-magomedsaygitov added OS: Windows investigate Collect additional information, like space on disk, other tool incompatibilities etc. and removed needs triage labels Oct 9, 2020
@konradpabjan
Copy link
Contributor

Hey @tysonite

I took a look at the failure! The runner abruptly disconnected which is why the step appears to have hanged and their aren't any logs available at the step.

This is a different error than the errors we've seen with our Mac VMs. We have a team internally investigating this. As a heads up internal telemetry is showing this error to come up very very infrequently. The RCA is unfortunately still unknown on our end 🤔

@maxim-lobanov
Copy link
Contributor

@tysonite , do you still experience these issues?
When you have seen repro last time?

@tysonite
Copy link
Author

tysonite commented Dec 4, 2020

I haven't looked into this since I reported it.

As far as I see, issue has been confirmed from github end, no point to look for me further unless there is confirmation that fix was applied.

@konradpabjan
Copy link
Contributor

Thanks for initially opening this issue @tysonite

There can be various causes on our end that lead to jobs failing with no logs. Over the last few months we've made a host of improvements to reduce the chances of these errors happening. For now I'm going to close out this issue. If this happens again please open up a new issue and you can ping me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Windows
Projects
None yet
Development

No branches or pull requests

5 participants