QA (public) » openQA Project (public)

Observation¶

From http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/ (old builds get deleted apparently hence no deep link):

…
Waiting while openQA is in progress
  <result project="devel:openQA:tested" repository="openSUSE_Factory" arch="x86_64" code="building" state="building">
Waiting while openQA is in progress
  <result project="devel:openQA:tested" repository="openSUSE_Factory" arch="x86_64" code="building" state="building">
Waiting while openQA is in progress
created request id 1268562
  <summary>unknown repository 'openSUSE_Leap_15.6'</summary>
  <details>404 unknown repository 'openSUSE_Leap_15.6'</details>
  <summary>unknown repository 'openSUSE_Leap_15.6'</summary>
  <details>404 unknown repository 'openSUSE_Leap_15.6'</details>
Waiting while openQA is in progress
  <summary>unknown repository 'openSUSE_Leap_15.6'</summary>
  <details>404 unknown repository 'openSUSE_Leap_15.6'</details>
Waiting while openQA is in progress
…

Suggestions¶

• openSUSE_Leap_15.6 should be just "15.6" without the prefix "openSUSE_Leap_" after a change to use SLE binaries directly some years ago. Maybe we still have that setup wrongly in some OBS project or some tooling doing that?
• See http://jenkins.qa.suse.de/job/trigger-openQA_in_openQA-TW/configure for the original trigger (based onhttp://download.opensuse.org/repositories/devel:/openQA/openSUSE_Tumbleweed/noarch/)
• Seems like jobs are getting stuck in a loop? Jobs seem to be running for almost 48hrs?
• Consider related work going on, maybe check with Yannis?
• DONE Mitigate by cancelling the stuck job