fix: rm failing pelican - #280
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the GitLab CI pipeline to stop using the Pelican binary in the deploy_results job, addressing a failing deployment step referenced in the linked job.
Changes:
- Removed Pelican download/verification and
pelican object copyupload steps fromdeploy_results. - Left
deploy_resultsto only generateresults/metadata.jsonand asummary.txtlisting.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
This is not because of pelican, but because tokens are not renewed right now. |
Nevertheless it hasn't worked in about half a year. |
|
Not fair, but okay. We have another use of pelican for low-Q2 tagger by @simonge, for that we have not yet agreed on transition to rucio, and I don't have a token for rucio renewed for benchmarks yet. This one is useless for validation (cc @torrijeske), but at least it's a canary for me to kick tires on token renewal. |
|
Sorry - do we want to keep this benchmark if it’s “useless for validation?” |
|
I don't feel strongly about this. I was just doing cleanup, and this has been failing for a long time so I figured it was defunct. If you want to keep it to fix it, then that's fine with me. |
Briefly, what does this PR introduce? Please link to any relevant presentations or discussions.
Pelican fails. Remove pelican.
What is the urgency of this PR?
What kind of change does this PR introduce?
Please check if any of the following apply