Integration tests failed randomly due to existing gradle Daemon
Open
bug
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 137
Description
### Describe the bug
We need to stop the daemon first to make sure the integration test can test. We might just need to document this.
```
./gradlew --stop
```
### To Reproduce
To run Polaris server locally
```
./gradlew run
```
To trigger regression test in another terminal
```
./gradlew check
```
Contributor guide
Research direction
Start by reproducing the integration-test failure with ./gradlew run followed by ./gradlew check, then compare the result after running ./gradlew --stop. Review the Gradle integration-test setup and determine whether the completed work should document this prerequisite or prevent the existing daemon from causing failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100