Jenkins Parser Monitoring

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-03-11 07:27:58 check-docker 186967 No error found. Please, take the appropriate action [ No action taken ]
2025-03-11 05:37:55 ib-run-qa 81318 Remote call on .* failed. The channel is closing down or has closed down
2025-03-11 05:03:52 ib-run-qa 81317 Remote call on .* failed. The channel is closing down or has closed down 21943
2025-03-11 04:40:07 ib-run-qa 81315 Remote call on .* failed. The channel is closing down or has closed down 21942
2025-03-11 04:02:10 ib-run-qa 81311 Remote call on .* failed. The channel is closing down or has closed down 21941
2025-03-10 12:39:30 ib-run-igprof 90446 Remote call on .* failed. The channel is closing down or has closed down 21939
2025-03-10 08:32:19 ib-run-igprof 90435 Build timed out 21936
2025-03-10 03:12:44 ib-run-relvals 350698 Remote call on .* failed. The channel is closing down or has closed down
2025-03-10 03:02:52 ib-run-relvals 350694 Remote call on .* failed. The channel is closing down or has closed down 21934
2025-03-10 02:52:32 ib-run-relvals 350692 Remote call on .* failed. The channel is closing down or has closed down 21933
2025-03-10 02:41:16 ib-run-relvals 350685 Remote call on .* failed. The channel is closing down or has closed down 21932

Jenkins Blacklist

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