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

Custom queries

All 'new' issues w/o assignee, sorted by version/priority
All auto_review tickets
All auto_review+force_result tickets
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE Tools team - due soon
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

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 almost 3 years ago. Updated almost 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)

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

Resolved

okurz

2021-06-10

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by okurz almost 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 almost 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 almost 3 years ago

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

Actions

Copy link

Updated by mkittler almost 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 almost 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