#120 RFE: Run the CI tests cron-ly or upon dependencies changes
Opened by churchyard. Modified

Every now and then, we open a pull request and we see a CI failure that is unrelated to the PR itself. Something has changed in the environment (openssl or glibc was updated, etc.).

Hence, I would really love to be able to run the CI test cron-ly (i.e. weekly, daily, etc., whatever the load would allow) or even based on dependencies changes (similarly to Koschei).

Obviously, I would need to be notified of a new failure somehow.

Is this something you would consider? Thanks.


Hi Miro,

Testing when dependencies change is planned. We call it "reverse dependency testing". The way it works downstream and how it will likely work in Fedora is that if your package A depends on package B, then when B is being updated, the dist-git (STI/FMF tests) tests of your package A will be executed as well.

Will something like that suffice?

Hey Michal.

Will something like that suffice?

Yes, assuming it counts with transitive dependencies and build dependencies as well.

Thanks.

Yes, assuming it counts with transitive dependencies and build dependencies as well.

It takes transitive dependencies into account, but I don't think build deps are included in the mix. Please note that this system would only run existing STI/FMF tests, but it would not try to rebuild anything. Therefore if your package A only build-requires package B, then running STI/FMF tests for A would not find any issues (when B gets updated).

Koschei integration is also work-in-progress though. cc @sturivny who knows more about it.

Hello. Is there any update on running the CI cron-ly or upon dependencies changes? Thanks

+1 it would be nice to have this in Fedora also, and done properly. @jkaluza @msrb this is planned for FY22 right?

Metadata