Job Status

Job Status lists all jobs currently in progress.

Status	Explanation
Running	The job is currently executing.
Idle	The job has begun but is not currently executing. This is most commonly due to waiting on an executor for some stage of the job.

CI Nodes

Job executors. In some cases, they may be offline. Nodes may be offline for a variety of reasons, including, in no particular order:

• Test Errors: If a node is failing to run tests as expected (errors in test cases, crashes, etc), it may be taken offline until the issues is resolved.
• New Tests: The addition of new tests requires extensive testing with known good dpdk tarballs to ensure compatibility.
• Configuration Changes: Configuration changes are tested to ensure they do not break any working tests or cause performance regressions.
• Vendor Request: A vendor may request that testing on their hardware be suspended.
• Maintenance: Nodes may be taken offline for any maintenance deemed necessary. This may include software updates, hardware changes or other changes in environment.

CI Job Queue

Jobs which have not begun to execute. A long queue is typically the result of either a spike in patch submissions, or a CI Node being temporarily taken offline for maintenance while still allowing jobs to queue. Jobs may be allowed to queue if a node is expected to only be online for a short time period, typically less than half an hour to prevent any disruption of test coverage.