Add GitHub Actions workflow to verify flaky testVerify flaky test #2457
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
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.
Add GitHub Actions workflow to verify flaky test
Purpose:
This PR adds a custom GitHub Actions workflow named verify-flaky-test.yml to confirm that the test org.jbpm.casemgmt.impl.CaseServiceImplTest#testStartExpressionCaseWithCaseFile is flaky.
The test passes under normal execution but fails when executed with NonDex, confirming the presence of non-deterministic behavior.
Summary of Changes:
Output:
The GitHub Actions build shows:
Test is flaky: Passes without NonDex but fails with NonDex
Logs and Output:
You can find the logs and output in the attached build artifacts, or view the successful build at: (https://github.com/Md-Arif-Hasan/flink/actions/runs/14689442443)
Attachments:
Notes:
This workflow automates the process of documenting the flakiness of CaseServiceImplTest.testStartExpressionCaseWithCaseFile using GitHub Actions. The CI logs confirm the test's behavior, showing that it passes under normal conditions but fails when executed with NonDex, which confirms the test is flaky due to non-deterministic behavior in certain environments.
Using this workflow, flaky tests can be detected and verified in a controlled, automated manner, which helps maintain the stability of the project's test suite.