Fix flaky Task240306MigrateLegacyLanguageVariablesTest integration test
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Integration test Task240306MigrateLegacyLanguageVariablesTest.testBothFilesMapToSameLanguageWithPriorityHandling is failing intermittently in merge queue CI runs with assertion error: expected 0 migration failures but was 5. This failure is unrelated to the PublisherTest timing fixes in PR 33750 and requires separate investigation into the language variable migration logic.
Acceptance Criteria
- [Define what needs to be accomplished]
Additional Notes
[Any additional context or notes]
Contributor guide
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 with Task240306MigrateLegacyLanguageVariablesTest.testBothFilesMapToSameLanguageWithPriorityHandling and reproduce the intermittent assertion failure in merge queue CI. Trace the language variable migration logic involved in the five reported failures and compare it with the PublisherTest timing fixes in PR 33750. Done means the cause is understood, the test is stable, and migration failures are zero; the acceptance criteria still need definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100