OverflowAsErrorTest and StaticInitializerExampleTest keep failing on 'main' #246
Conversation
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
denis-fokin
force-pushed
the
denis-fokin/remove-maven-gradle-plugin
branch
from
4bc0e8d to
f17f64d
Compare
denis-fokin
force-pushed
the
denis-fokin/remove-maven-gradle-plugin
branch
from
f17f64d to
587418c
Compare
denis-fokin
changed the title
Damtev
approved these changes
Jun 20, 2022
alisevych
pushed a commit
that referenced
this pull request
Jun 21, 2022
…'main' (#246) OverflowAsErrorTest is fixed. StaticInitializerExampleTest is disabled.
mmvpm
pushed a commit
that referenced
this pull request
Jun 22, 2022
…'main' (#246) OverflowAsErrorTest is fixed. StaticInitializerExampleTest is disabled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Recently we are getting red master and PR. Failure analysis does not show the problematic commit. Eventually, we figured out that two tests use the same example. If the same example is used two tests with the same name are generated. Subsequently, the first one is rewritten by the second one. I have not found the cause of the second failure, so we need to disable it in order to make the
mainbranch green.Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Automated Testing
Specify tests that help to verify the change automatically.
org.utbot.examples.math.OverflowExamplesTest
org.utbot.examples.math.OverflowAsErrorTest
org.utbot.examples.mixed.StaticInitializerExampleTest
Manual Scenario
No manual scenario
Checklist (remove irrelevant options):