adoptium / adoptium/infrastructure
Log of processes which the ProcessCheck job could not terminate
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
This issue will be used to track machines on which jobs are not terminating cleanly with a normal kill command.
These should be visible on the [SXA-processCheck](https://ci.adoptopenjdk.net/view/Tooling/job/SXA-processCheck/) job. Each should be annotated with the host machine (ideally a jenkins link) and the full output from the process listing corresponding to the rogue process - it should be in signle backticks to make the full line visible in here without scrolling. This information should be viisble just before any line such as this in the SXA-processCheck job. The processes listed here should be killed as part of the process of logging this so if someone else comes along they don't report the same thing.
The intention of this issue is that we can look for any potential patterms of things that are causing problems with stability of the test infrastructure.
```
Cleanup failed - may need manual intervention as I am too scared to run kill -KILL ...
```
Contributor guide
Research direction
Start with the linked SXA-processCheck Jenkins job and inspect the cleanup-failure output for machines where jobs do not terminate cleanly. Record the host, Jenkins link, and full process-list line for each rogue process, then verify the process is killed and the information is visible before the cleanup warning. No files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100