Ecdar / Ecdar/j-Ecdar

Flaky tests maybe related to consistency check

Open
#90 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
4
Forks
9
PR merge metrics
No merged PRs in 30d

Description

In #85 a flaky tests was experienced when merging #74 into main. ``cdd_tarjan_reduce_rec`` caused by an internal error. However, I have previously seen this kind of error when CDD have been incorrectly initialized (``init``) and finalised (``done``). I think that somewhere we have incorrect CDD access. A starting point for debugging could be to trace this [Consistency Test](https://github.com/Ecdar/j-Ecdar/blob/9d53d7a104cab5067b7337fa6967e84e6d9d8e7a/test/e2e/ConsistencyTest.java#L120).
![flaky test output from ci](https://user-images.githubusercontent.com/58144556/201989329-36dc8001-03a1-45bc-832b-4e6f55528300.PNG)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with test/e2e/ConsistencyTest.java around line 120, then trace the cdd_tarjan_reduce_rec internal error and the CDD init/done access mentioned in the report. Done means identifying and correcting the invalid CDD access and confirming that the consistency test no longer fails intermittently.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.