Repository navigation
We need sanity-checking CI on PRs #1794
Description
As the number of open PRs starts to grow, we need to add sanity checks on PRs to verify that every software they claim to add is actually added by the PR (seen in #1771 (comment) for example).
This is complicated to check, as you need to check
- what is added by the tarballs, is it consistent across architecture families
- does what is added match the additions to the easystacks
- check that what is being added by the tarballs does not already exist in the repository (this could be triggered once the deploy label is set, but only once as once ingestion has actually happened this check will fail...so maybe it needs triggering on
ready-to-deploy? Special CI forready-to-deploysounds a lot like what @casparvl has been working on)
Activity
casparvl commentedon Oct 20, 2026
Can you elaborate on what exactly you want to check? I mean, CI cannot really check for tarball contents. At best, it can check for what the bot reports.
Note that that's what #1564 aims to do: basically automating the assesment of the
bot:status last_buildreport. Nothing more, nothing less.I guess you could create an equivalent CI that checks the individual "Success" reports from the
bot:buildcommands to see what they (reportedly) build... But while you can check the eaysconfigs directly listed in the easystack quite easily, all of the dependencies are not know just by reading the PR content - you'd have to actually invoke EasyBuild to resolve that.ocaisa commentedon Oct 20, 2026
CI can check tarball contents to the extent that they are listed in the message posted by the bot, that's indeed what I meant.
You can easily check what the PR would build by running an
eb --missing ...and parsing the output a bit, the plan would be to sanity check that against what the bot is reporting in the comments. Triggering this onready-to-deployseems like a good move, as this is the only time you can at least hope that another PR is not going to interfere.