Skip to content

kola: run provisioning tests separately #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 12, 2022

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Oct 12, 2022

This effectively upstreams
coreos/fedora-coreos-pipeline@c3af4ad57ab4.

The same reasons apply, but we're doing it now here too because it'll help with not hitting against our memory limits.

This effectively upstreams
coreos/fedora-coreos-pipeline@c3af4ad57ab4.

The same reasons apply, but we're doing it now here too because it'll
help with not hitting against our memory limits.
@jlebon
Copy link
Member Author

jlebon commented Oct 12, 2022

I bet we could revert this (and the pipeline version) once we have coreos/coreos-assembler#3118. Because that'll naturally lower the concurrency on these tests.

Though if it still causes issues, we should lower this into kola in the form of a e.g. heavyweight tag or something and then kola knows not to run more than one heavyweight test at a time.

Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dustymabe dustymabe merged commit 574fbc6 into coreos:main Oct 12, 2022
@cgwalters
Copy link
Member

Ah, nice, thanks for digging into this. I think coreos/coreos-assembler#3118 is the best fix, but even short term, this also touches on coreos/coreos-assembler#3008 and the need to be able to implement logic like this that's decoupled from Jenkins.

jlebon added a commit to jlebon/coreos-ci-lib that referenced this pull request Oct 13, 2022
Some upstreams just want to run a subset of tests. coreos#118 split out the
reprovisioning tests, but it then changed the semantics for users that
only want to run a specific pattern. Now, those CIs are always running
reprovisioning tests even though they're not interested.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants