The table below displays the activity of the Jenkins Parser job.
Red entries correspond to failed jobs where the Jenkins Parser has not taken any action. Please, take the appropriate action in those cases. White entries correspond to jobs retried by the Parser because a known Error Message was found in the log.
| Time | Job Name | Build Number | Error Message | Retry Job |
|---|---|---|---|---|
| 2025-07-15 00:30:34 | ib-run-relvals | 366347 | Remote call on .* failed. The channel is closing down or has closed down | 23049 |
| 2025-07-14 23:39:52 | ib-run-igprof | 93825 | Build timed out | 23048 |
| 2025-07-14 18:40:10 | ib-run-relvals | 366331 | Remote call on .* failed. The channel is closing down or has closed down | |
| 2025-07-14 18:33:07 | ib-run-relvals | 366330 | Remote call on .* failed. The channel is closing down or has closed down | 23046 |
| 2025-07-14 18:25:45 | ib-run-relvals | 366329 | Remote call on .* failed. The channel is closing down or has closed down | 23045 |
| 2025-07-14 18:17:57 | ib-run-relvals | 366328 | Remote call on .* failed. The channel is closing down or has closed down | 23044 |
The table below displays the blacklisted nodes in our Jenkins infrastructure. There is a sanity job that checks if CernVM-FS repositories are accessible and if singularity can start a container on the nodes. If not, the node is blacklisted and displayed in the table below.
If the table entry is red, please take the appropriate action (open a SNOW ticket, run the start_cvmfs.sh script on aarch64 machines, etc) and re-run the sanity job to take the node out of the blacklist. In any case, the sanity job automatically runs every 30 min.
| Blacklisted Node | Node Url | Reason |
|---|