Create an @Concurrent test group for concurrency related tests [LUCENE-10566]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
This Jira is based off of the discussion in [PR #633](https://github.com/apache/lucene/pull/633#discussion_r867220409).
The idea is to be able to separately identify and run tests which verify concurrency related code. It would make it easier to narrow down to concurrency related issues in CI build failures, and make it easy for people to run such tests on repeat ("beast them") when they make related changes.
---
Migrated from [LUCENE-10566](https://issues.apache.org/jira/browse/LUCENE-10566) by Vigya Sharma (@vigyasharma)
Contributor guide
Research direction
Start with the discussion in PR #633 and the migrated Jira issue LUCENE-10566, then inspect Lucene's existing test-grouping entry points. Done means concurrency-related tests can be identified separately, run repeatedly, and used to narrow related CI failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100