apache / apache/maven-surefire

[SUREFIRE-1708] skipAfterFailureCount should be coherent across multiple fork JVMs

Open
#2,037 0 comments 0 reactions 0 assignees View on GitHub
bug priority:major
Dominant language
Java
Stars
461
Forks
588
Avg merge
1d 8h
Merged PRs (30d)
19

Description

**[Tibor Digana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibor17)** opened **[SUREFIRE-1708](https://issues.apache.org/jira/browse/SUREFIRE-1708?redirect=false)** and commented

---

**Issue Links:**
- [SUREFIRE-1709](https://issues.apache.org/jira/browse/SUREFIRE-1709) Fire events when Provider execution is started and finished
(_**"Dependent"**_)
- [SUREFIRE-1710](https://issues.apache.org/jira/browse/SUREFIRE-1710) skipAfterFailureCount in JUnit5 provider
(_**"Dependent"**_)

Contributor guide

Open the contributing guide

Research direction

Start by reading the SUREFIRE-1709 and SUREFIRE-1710 dependent issues, since this issue provides no file, test, or entry point. The change is done when skipAfterFailureCount behaves coherently across multiple fork JVMs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, testing
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.