action #65025
closed[opensuse][aarch64][jeos] consistently incompleting scenario that never worked "opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos_tw_zdup_aarch64@aarch64"
0%
Description
Observation¶
https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensuse&flavor=JeOS-for-AArch64&machine=aarch64&test=jeos_tw_zdup_aarch64&version=Tumbleweed is consistently incompleting with Download of "/var/lib/openqa/cache/openqa1-opensuse/openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-old-20200329.raw.xz" failed: 404 Not Found.
Also a test suite should not have an arch-specific suffix.
Updated by okurz almost 5 years ago
- Subject changed from consistently incompleting scenario that never worked "opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos_tw_zdup_aarch64@aarch64" to [opensuse][aarch64][jeos] consistently incompleting scenario that never worked "opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos_tw_zdup_aarch64@aarch64"
- Assignee set to ggardet_arm
- Priority changed from High to Low
Removed from https://openqa.opensuse.org/admin/job_templates/38
@@ -103,20 +103,6 @@
description: ''
testsuite: null
priority: 60
- opensuse-Tumbleweed-JeOS-for-AArch64-aarch64:
- - jeos_tw_zdup_aarch64:
- description: |-
- https://progress.opensuse.org/issues/56936
-
- While it downloads the last published (=previous) snapshot, %BUILD% is included in HDD_1(_URL) to avoid caching the unversioned filename.
- settings:
- +HDD_1: openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-old-%BUILD%.raw.xz
- BOOT_HDD_IMAGE: '1'
- DESKTOP: textmode
- EXTRABOOTPARAMS: console=tty0 quiet
- HDD_1_URL: http://download.opensuse.org/ports/aarch64/tumbleweed/images/openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-Current.raw.xz?foobar=%BUILD%
- ZDUP: '1'
- testsuite: null
opensuse-Tumbleweed-NET-aarch64:
- btrfs+warnings:
priority: 50
Updated by favogt almost 5 years ago
- Is duplicate of action #62159: Asset GRU download not done by web UI host if job scheduled by `isos post`, fails to download and then cloned (was: … using the Web UI) added
Updated by favogt almost 5 years ago
This is just a dup of 62159 - the test itself works fine. Can you add it back?
Updated by okurz almost 5 years ago
I'm sorry, I don't want to add the test back in the current state for two reasons: 1. There should not be an arch-specific suffix in the test suite name, 2. I did not test if it works and previously it was consistently incompleting . So if you want to add it back please make sure to have a testsuite name that is generic regardless of the architecture and cover architecture specifics in the test code or, if you prefer, in a parameterized job template. And also please add it back after ensuring it does work.
Updated by favogt almost 5 years ago
Before https://progress.opensuse.org/issues/62159 is fixed it does not make sense to add it back.
Updated by favogt over 4 years ago
- Status changed from New to Resolved
I can confirm that the issue is fixed, thanks!
I created a new test suite and hooked it up, but unfortunately it bumps against max_redirects now. I opened a PR for that: https://github.com/os-autoinst/openQA/pull/3338
Updated by jlausuch almost 4 years ago
- Project changed from openQA Tests (public) to 208
- Category deleted (
Bugs in existing tests)