microsoft / microsoft/terminal
We need to do something about these feature tests
Open
Area-Build
Issue-Task
Product-Meta
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
Seriously. I'd reckon that 50% of our CI runs fail due to this. Dunno what happened to make these flakier. EIM seems like a good time to address this.
Previous notes:
* #11858
* #8534
* #15106
We're definitely correctly waiting on the conhost / openconsole process to start. It's just that some percent of the time, it still just fails to re-open the stdout handle and attach to that console. Crazy.
Contributor guide
Research direction
Start by reviewing the feature-test failures and the previous notes in #11858, #8534, and #15106. Investigate the conhost/openconsole startup path and the intermittent stdout-handle reattachment; done means the affected tests no longer fail intermittently in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100