Skip to content

Add GitHub Actions workflow to verify flaky test #712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Md-Arif-Hasan
Copy link
Contributor

@Md-Arif-Hasan Md-Arif-Hasan commented Apr 26, 2025

Purpose

This PR adds a custom GitHub Actions workflow named verify-flaky-test.yml to confirm that the test org.jsmart.zerocode.core.kafka.DeliveryDetailsTest#testSerDeser is flaky. The test passes under normal execution but fails when executed with NonDex, confirming the presence of non-deterministic behavior.

Summary of Changes

  • Added a new workflow .github/workflows/verify-flaky-test.yml
  • The workflow:
    • Sets up JDK 11 using actions/setup-java
    • Builds the project using Maven with tests skipped
    • Runs the test once normally (expected to pass)
    • Runs the test again using NonDex (expected to fail)
    • Verifies flakiness by comparing exit codes and logs

Output

The GitHub Actions build shows:

  • ✅ Normal test run passes
  • ❌ NonDex test run fails
  • ✅ Final verification logs include:
    ✅ Test is flaky: Passes without NonDex but fails with NonDex

You can find the logs and output in the attached file or view the successful build here:
https://github.com/Md-Arif-Hasan/zerocode/actions/runs/14678327187/job/41197758983

Attachments

🔗 CI Build Log: logs_37716316986.zip (see ci-build.log inside)

  • 🧾 Workflow YAML: .github/workflows/verify-flaky-test.yml
  • 🔄 Diff: Use git diff to compare this new file against the baseline

Notes

This workflow documents the flakiness of DeliveryDetailsTest.testSerDeser using GitHub Actions.
The CI logs confirm that the test passes normally but fails under NonDex shuffling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant