action #178102
openQA (public) - coordination #162890: [saga][epic] feature discoverability
coordination #162896: [epic] Job triggering on jobless openQA instances
No automatic submission of os-autoinst+openQA as of 2025-02-28
0%
Description
Observation¶
It seems that there have not been recent submissions of os-autoinst+openQA to openSUSE:Factory, likely related to #177901. Last openQA submission was https://build.opensuse.org/requests/1247815 from 2025-02-22.
http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/2827/console and similar jobs say
Skipping submission, reason:
Only triggering tests from devel:openQA (not overriding devel:openQA:testing and doing a submission) because openQA-in-openQA tests or a submission is still pending (as devel:openQA:testing still contains packages)
I think the assumption that a submission is pending only because devel:openQA:testing contains packages is wrong.
Acceptance criteria¶
- AC1: There are regular submissions of os-autoinst+openQA to openSUSE:Factory again
Suggestions¶
Updated by okurz about 7 hours ago
- Copied from action #174451: openQA-in-openQA tests can get stuck with an inconsistent repository size:S added
Updated by okurz about 6 hours ago
- Copied to action #178105: Ensure automatic submissions os-autoinst+openQA if previous submissions have been too long in the past added
Updated by okurz about 6 hours ago ยท Edited
On jenkins.qe.nue2.suse.org I did rm /var/lib/jenkins/workspace/submit-openQA-TW-to-oS_Fctry/job_post_skip_submission
and triggered http://jenkins.qa.suse.de/job/trigger-openQA_in_openQA-TW/ again. I hope that's enough as mitigation.
EDIT: Seems to have no effect as per http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/lastSuccessfulBuild/console . I now deleted os-autoinst+openQA from https://build.opensuse.org/project/show/devel:openQA:testing and copypac
'd them from devel:openQA and called the submit script manually. Finally a new submission https://build.opensuse.org/requests/1249335 . Was that ok?