action #37695
closed[qam][sle][functional][y] test fails in zypper_lifecycle_toolchain - gcc6 reached expiration
0%
Description
Observation¶
openQA test in scenario sle-12-SP3-Server-DVD-Updates-x86_64-qam-allpatterns+addons@64bit fails in
zypper_lifecycle_toolchain
# Test died: For toolchain module gcc6 expected 2024-10-30 as expiration date, lifecycle output:
[...]
gcc6 Now
gcc6-32bit Now
gcc6-c++ Now
gcc6-c++-32bit Now
gcc6-fortran Now
gcc6-fortran-32bit Now
gcc6-info 2024-10-30
gcc6-locale Now
@riafarov, as the maintainer of this test module, could you please take a look?
Feel free to reassign in case you don't have enough capacity to work on this one.
Reproducible¶
Fails since (at least) Build 20180621-6
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by riafarov over 6 years ago
- Subject changed from [QAM] test fails in zypper_lifecycle_toolchain - gcc6 reached expiration to [QAM][sle][functional] test fails in zypper_lifecycle_toolchain - gcc6 reached expiration
Updated by riafarov over 6 years ago
- Due date set to 2018-07-17
- Status changed from New to Workable
- Assignee deleted (
riafarov)
Moving to the next sprint, when we are done with tickets from current one, we'll pick it up.
@vsvecova for such tickets, simply put [functional] tag and we will see it and schedule according to our availability and priority, no need to find an assignee.
Updated by pcervinka over 6 years ago
- Priority changed from Normal to High
Occurs in every QAM incident job. It means making maintenance openQA review more demanding(manual check/approval of update is needed).
Updated by okurz over 6 years ago
- Subject changed from [QAM][sle][functional] test fails in zypper_lifecycle_toolchain - gcc6 reached expiration to [qam][sle][functional] test fails in zypper_lifecycle_toolchain - gcc6 reached expiration
@pcervinka Can you find someone within qam to work on this? I doubt QSF (QA SLE functional) is able to fix it fast.
Updated by okurz over 6 years ago
But as a temporary measure, you could exclude the test module with EXCLUDE_MODULES=zypper_lifecycle in test settings as well.
Updated by riafarov over 6 years ago
- Subject changed from [qam][sle][functional] test fails in zypper_lifecycle_toolchain - gcc6 reached expiration to [qam][sle][functional][y] test fails in zypper_lifecycle_toolchain - gcc6 reached expiration
- Assignee set to riafarov
Updated by riafarov over 6 years ago
- Status changed from Workable to Resolved