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.

Sign up for GitHub

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

Jump to bottom

Unknown test host crash in testing causes CI to fail #49032

Closed
sharwell opened this issue Oct 29, 2020 · 3 comments
Closed

Unknown test host crash in testing causes CI to fail #49032

sharwell opened this issue Oct 29, 2020 · 3 comments
Labels
Area-Infrastructure Contributor Pain The issue impedes progress for project collaborators.

Comments

@sharwell
Copy link
Member

sharwell commented Oct 29, 2020 •
edited by runfoapp bot
Loading

This is a tracking issue for cases where a stack overflow terminates the test process, causing CI to fail.

Build Kind Start Time
868866 PR 48978 2020-28-10
869760 Rolling 2020-29-10
870506 PR 48949 2020-29-10
870408 Rolling 2020-29-10
870306 PR 49048 2020-29-10
870623 Rolling 2020-29-10
870946 Rolling 2020-30-10
870968 PR 49047 2020-30-10
870858 PR 47305 2020-30-10
870719 Rolling 2020-29-10
871030 PR 49068 2020-30-10
@sharwell sharwell added Area-Infrastructure Contributor Pain The issue impedes progress for project collaborators. labels Oct 29, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Oct 29, 2020
@sharwell sharwell changed the title Stack overflow in testing causes CI to fail Unknown test host crash in testing causes CI to fail Oct 29, 2020
@sharwell sharwell removed the untriaged Issues and PRs which have not yet been triaged by a lead label Oct 30, 2020
@sharwell
Copy link
Member Author

sharwell commented Oct 30, 2020 •
edited
Loading

@jaredpar once we switch from procdump to registry keys for crash dump collection, this issue will either be fixed (no more crashes), or I will be able to review the collected heaps to identify the cause. Currently we're only collecting the crash message, but no data to narrow it down (the Dumps folder is empty).

@jaredpar
Copy link
Member

Okay. I will try and prioritize that over the weekend

@sharwell
Copy link
Member Author

Duplicate of #49275

@sharwell sharwell marked this as a duplicate of #49275 Nov 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Infrastructure Contributor Pain The issue impedes progress for project collaborators.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jaredpar @sharwell @Dotnet-GitSync-Bot