action #95164
closed
OBS Package build in github fails to provide updates, "OBS Package Build Expected — Waiting for status to be reported" size:M
Added by okurz over 3 years ago.
Updated over 3 years ago.
Description
Observation¶
Seems like in multiple, maybe all, pull requests the OBS status check does not report back to github anymore, e.g. in
https://github.com/os-autoinst/openQA/pull/3987
there is
OBS Package Build Expected — Waiting for status to be reported
while https://build.opensuse.org/project/show/devel:openQA:TestGithub:PR-3987 looks just fine and finished
Expected result¶
- An OBS package build check reports back same as some days ago
Suggestions¶
- DONE: Try if re-creating PRs can work around the problem -> closing PR and creating new one helps
- Check if/why some PRs still proceed -> likely a temporary problem that is fixed meanwhile for new PRs
Workaround¶
Close PR and create new one (closing+reopening is not sufficient)
- Related to action #93838: Use new OBS SCM integration to trigger OBS checks on pull/merge requests for our projects added
- Subject changed from OBS Package build in github fails to provide updates, "OBS Package Build Expected — Waiting for status to be reported" to OBS Package build in github fails to provide updates, "OBS Package Build Expected — Waiting for status to be reported" size:M
- Description updated (diff)
- Status changed from New to Workable
Just did a quick test: At least closing and reopening a PR doesn't help.
- Description updated (diff)
- Due date set to 2021-07-14
- Status changed from Workable to Feedback
- Assignee set to okurz
- Priority changed from Urgent to High
Updated the ticket description with workaround hence reducing prio. Also, as newly opened PRs do not seem to have the problem I think we do not need to actively change something except suggest reviewees to recreate their affected PRs unless we force-merge the non-critical ones.
- Assignee deleted (
okurz)
- Priority changed from High to Urgent
I've just received "Successful pipeline for master | osd-deployment | af090d3d" so I suppose it works.
- Assignee set to okurz
- Priority changed from Urgent to High
wrong ticket – and wrong update :)
- Status changed from Feedback to Resolved
Also available in: Atom
PDF