redhat-developer / redhat-developer/dotnet-regular-tests
debugging-via-dotnet-dump fails with .NET 11
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8
- Forks
- 17
- Avg merge
- 1d 4m
- Merged PRs (30d)
- 6
Description
The debugging-via-dotnet-dump test fails with .NET 11 with many different issues.
- Sometimes
dotnet dump analyze coredump.975 --command analyzeoom --command exitfails. - Sometimes commands print garbage
To keep results green, I am going to disable this test.
This issue is to track re-enabling it for .NET 11.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the debugging-via-dotnet-dump test and run the shown dotnet dump analyze command under .NET 11. Compare the intermittent command failures and garbled output with the test's current expectations. Done means the test is re-enabled and passes reliably with .NET 11.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100