Project

General

Profile

Actions
Copy link

action #154699

closed

https://os-autoinst.github.io/qa-tools-backlog-assistant/ not updated since 2023-01-31 size:M

Added by okurz 3 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
High
Assignee:
jbaier_cz
Target version:
openQA Project - Ready
Start date:
2024-02-01
Due date:
% Done:

0%

Estimated time:
Tags:
reactive work, tools

Description

Observation

https://os-autoinst.github.io/qa-tools-backlog-assistant/ shows Latest Run: 2024-01-31 23:19:25 UTC, should be 2024-02-01 by now

From the GitHub action log: https://github.com/os-autoinst/qa-tools-backlog-assistant/actions/runs/7738915674/job/21100696051#step:12:329

Err:49 mirror+file:/etc/apt/apt-mirrors.txt jammy-updates/main amd64 python3-pil amd64 9.0.1-1ubuntu0.1
  404  Not Found [IP: 20.106.104.242 80]
E: Failed to fetch mirror+file:/etc/apt/apt-mirrors.txt/pool/main/p/pillow/python3-pil_9.0.1-1ubuntu0.1_amd64.deb  404  Not Found [IP: 20.106.104.242 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Fetched 62.4 MB in 5s (12.0 MB/s)
Error: Process completed with exit code 100.

And why did nobody receive emails about failing github actions?

Expected result

  • "Latest run" should be current again
  • We should receive some notification if github actions fail

Suggestions

  • Look into the details of the mentioned github actions
  • Fix the problem
  • Ensure that we receive notifications for failing github actions (if they actually fail)
  • Ensure that our backlog status is current again
  • Consider improving the GHA, why do we even install dependencies. Should we build a container for deps ourselves?
Actions
Copy link
 #1

Updated by jbaier_cz 3 months ago

  • Description updated (diff)

Apparently some internal problem in the Github runner we might need to solve.

Actions
Copy link
 #2

Updated by okurz 3 months ago

  • Subject changed from https://os-autoinst.github.io/qa-tools-backlog-assistant/ not updated since 2023-01-31 to https://os-autoinst.github.io/qa-tools-backlog-assistant/ not updated since 2023-01-31 size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by jbaier_cz 3 months ago

  • Status changed from Workable to In Progress
  • Assignee set to jbaier_cz
Actions
Copy link
 #4

Updated by jbaier_cz 3 months ago

I created https://github.com/openSUSE/backlogger/pull/30 to address the installation issue.

Actions
Copy link
 #5

Updated by jbaier_cz 3 months ago

Quoting from documentation:

Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead. If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.

So there was actually a notification sent, looking at the last commits the receiver was probably Dominik as he took over the notification with the last commit

Actions
Copy link
 #6

Updated by openqa_review 3 months ago

  • Due date set to 2024-02-16

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

Actions
Copy link
 #7

Updated by jbaier_cz 3 months ago

  • Due date deleted (2024-02-16)
  • Status changed from In Progress to Resolved

I added some minor extra enhancements (mostly version updates). Backlog seems to be working again, I do not think we can do much more.

Actions
Copy link

Also available in: Atom PDF