jammy/linux-uc22-lowlatency: 5.15.0-43.46.1 snap-debs snap:pc-lowlatency-kernel
Bug #1981228 reported by
Stefan Bader
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Committed
|
Medium
|
Unassigned | ||
Snap-prepare |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-beta |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-candidate |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-edge |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-stable |
New
|
Medium
|
Canonical Kernel Team |
Bug Description
This bug will contain status and test results related to a kernel source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https:/
-- swm properties --
issue: KSRU-4380
kernel-
phase: Complete
phase-changed: Tuesday, 19. July 2022 20:22 UTC
reason: {}
snap-name: pc-lowlatency-
variant: snap-debs
~~:
clamps:
parent: 5.15.0-47.53.1
self: 5.15.0-47.53.1
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-2022.07.11-1 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1981229 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
summary: |
- jammy/linux-uc22-lowlatency: <version to be filled> snap-debs + jammy/linux-uc22-lowlatency: <version to be filled> snap-debs snap:pc- + lowlatency-kernel |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
tags: | added: kernel-jira-issue-ksru-4380 |
description: | updated |
summary: |
- jammy/linux-uc22-lowlatency: <version to be filled> snap-debs snap:pc- + jammy/linux-uc22-lowlatency: 5.15.0-43.46.1 snap-debs snap:pc- lowlatency-kernel |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
To post a comment you must log in.
All tasks have been completed and the bug is being closed