action #95164: OBS Package build in github fails to provide updates, "OBS Package Build Expected — Waiting for status to be reported" size:M - openQA Project - openSUSE Project Management Tool

Actions

Copy link

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.

Status:

Resolved

Priority:

High

Assignee:

okurz

Category:

Organisational

Target version:

Ready

Start date:

2021-07-07

Due date:

2021-07-14

% Done:

Estimated time:

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 issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by okurz over 3 years ago

Related to action #93838: Use new OBS SCM integration to trigger OBS checks on pull/merge requests for our projects added

Actions

Copy link

Updated by livdywan over 3 years ago

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

Actions

Copy link

Updated by tinita over 3 years ago

Just did a quick test: At least closing and reopening a PR doesn't help.

Actions

Copy link

Updated by mkittler over 3 years ago

Check if/why some PRs still proceed

It seemed to work on my PRs from yesterday and e.g. https://github.com/os-autoinst/openQA/pull/4015, https://github.com/os-autoinst/openQA/pull/4014 and https://github.com/os-autoinst/openQA/pull/4013. So I simply think that not all PRs are affected. Maybe there was a temporary problem. I remember that I had the same problem before and assumed that there was a connection issue at the time OBS attempted to report the status back (and the integration misses a re-try). Maybe #93838 would help with that.

Try if re-creating PRs can work around the problem

As already stated, it works on new PRs so this should help.

Actions

Copy link

Updated by okurz over 3 years ago

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.

Actions

Copy link