adoptium / adoptium/infrastructure
Feature: add timeout in job "QEMUPlaybookCheck"
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/ does not have timeout, which causes https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/358/console running there for more than 1 month still not finish
Probably is something wrong with https://ci.adoptopenjdk.net/job/QEMUPlaybookCheck/ARCHITECTURE=ppc64le,OS=ubuntu18,label=vagrant/358/consoleFull (I had it aborted this morning when I saw https://ci.adoptopenjdk.net/job/Will-HostOnlyIfsCheck/120/ waiting for node on [infra-ibmcloud-vagrant-x64-1.4](https://ci.adoptopenjdk.net/computer/infra-ibmcloud-vagrant-x64-1.4) since 15th Nov)
Contributor guide
Research direction
Start by inspecting the QEMUPlaybookCheck job configuration and the linked console output, especially the ppc64le Ubuntu 18 job. Determine where its timeout is configured and verify that a stalled run such as build 358 would be aborted; done means the job has a bounded runtime and the relevant CI behavior is confirmed.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100