[DEV] Investigate Hikary warning in logs
- Dominant language
- Java
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
During run of all tests I've obtained this message in logs:
17:55:01.531 [HikariPool-2 housekeeper] WARN com.zaxxer.hikari.pool.HikariPool - HikariPool-2 - Thread starvation or clock leap detected (housekeeper delta=47s231ms877µs24ns).
after which all the work stopped and tests left hanging. We should investigate what could be the reason of this warning and is it safe.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running the full test suite and capture the HikariPool warning together with the point where tests hang. Investigate the reported thread-starvation or clock-leap warning and determine whether it causes the hang or is safe to ignore. Done means the cause and safety of the warning are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100