-
Notifications
You must be signed in to change notification settings - Fork 9.2k
TryDuplicateBadTab and TryDuplicateBadPane unit tests are hanging when run locally #5169
Copy link
Copy link
Closed
Labels
Area-CodeHealthIssues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-BisectSomebody's got to go through and do the needful.Somebody's got to go through and do the needful.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsPriority-2A description (P2)A description (P2)Product-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
Metadata
Metadata
Assignees
Labels
Area-CodeHealthIssues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-BisectSomebody's got to go through and do the needful.Somebody's got to go through and do the needful.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsPriority-2A description (P2)A description (P2)Product-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Environment
Windows build number: Version 10.0.18362.657
Windows Terminal version (if applicable): Commit 28d108b
Steps to reproduce
runut.cmd /name:*TabTests::TryDuplicate*Expected behavior
The unit tests should execute successfully.
Actual behavior
The
TestHostAppwindow opens up and the test then appears to be stuck. Closing the window manually doesn't help, but if you instead kill theTestHostAppprocess, it will at least continue with the rest of the tests.