fix runtime calculation for java#1698
Merged
misrasaurabh1 merged 5 commits intoomni-javafrom Mar 1, 2026
Merged
Conversation
The Java Comparator used only iteration_id as the map key when comparing test results. Since every test method had iteration_id="1", all rows collapsed to a single entry and only the last row survived. Because JUnit test execution order is non-deterministic, the surviving row differed between baseline and candidate runs, causing false correctness failures. Fix the key to include test_module_path:test_class_name:test_function_name for unique identification. Also add an A/A test that runs the original code through the candidate pipeline to detect verification bugs like this. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.