After registry concurrency fix, new IT got unstable
Open
bug
- Dominant language
- Java
- Stars
- 3.5k
- Forks
- 250
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 36
Description
### Affected version
master
### Bug description
ERROR] Failures:
[ERROR] ConcurrentDownloadsTest.build:67 The maximum number of concurrent downloads (actual: 0) must fulfil the condition maxConcurrentDownloads >= 1 && maxConcurrentDownloads <= 2 ==> expected: but was: false
Contributor guide
No contributing guide indexed for this repository
Research direction
The failure is in ConcurrentDownloadsTest.build; start by running that integration test on master and inspect the reported concurrency assertion. Trace why actual maxConcurrentDownloads is 0 after the registry concurrency fix, then make the test reliably satisfy the stated 1–2 range and rerun it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100