Project

General

Profile

action #90314

unhandled error output in t/4-worker-jobs.t

Added by okurz 4 months ago. Updated 4 months ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Concrete Bugs
Target version:
Start date:
2021-03-18
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

https://app.circleci.com/pipelines/github/os-autoinst/openQA/5979/workflows/fbd3ad90-3f24-4d2f-8bdf-08a4124f9109/jobs/56377

[17:53:52] t/24-worker-jobs.t ........................................ 14/? [ERROR] Aborting job because web UI doesn't accept new images anymore (likely considers this job dead)
[ERROR] Unable to make final image uploads. Maybe the web UI considers this job already dead.
[ERROR] Unable to make final image uploads. Maybe the web UI considers this job already dead.
[ERROR] Unable to make final image uploads. Maybe the web UI considers this job already dead.

Acceptance criteria

  • AC1: Tests fail if there is any unhandled output
  • AC2: No unhandled output in t/24-worker-jobs.t

Suggestions

  • I can confirm this is reproducible locally, so run prove -l t/24-worker-jobs.t to reproduce and make sure the output is handled

History

#1 Updated by okurz 4 months ago

  • Status changed from New to Workable
  • Assignee set to mkittler
  • Priority changed from Normal to High

It seems very likely that https://github.com/os-autoinst/openQA/pull/3791 introduced this just recently, see #90152 as well

mkittler can you take a look please?

#2 Updated by openqa_review 4 months ago

  • Due date set to 2021-04-02

Setting due date based on mean cycle time of SUSE QE Tools

#3 Updated by mkittler 4 months ago

  • Status changed from Workable to In Progress

#4 Updated by okurz 4 months ago

https://github.com/os-autoinst/openQA/pull/3806 merged. I crosschecked that there is no more unhandled output. So AC2 is covered, AC1 to go

#5 Updated by mkittler 4 months ago

Not sure about AC1. I can mock _log_msg from our logging module and fail the test if the log level is higher than debug. But how would I distinguish the case when the output is actually handled?

#6 Updated by okurz 4 months ago

  • Status changed from In Progress to Workable
  • Assignee deleted (mkittler)
  • Priority changed from High to Normal
  • Target version changed from Ready to future

mkittler asked in internal chat if anyone has an idea. Because I don't expect an answer soon taking it out of backlog again.

#7 Updated by okurz 4 months ago

  • Due date deleted (2021-04-02)

Also available in: Atom PDF