action #52892
closed[functional][u] test fails in toolkits/prepare: sdk repo url is invalid
0%
Description
Observation¶
openQA test in scenario sle-12-SP5-Server-DVD-x86_64-toolkits_sle12@64bit fails in
prepare
Test suite description¶
Maintainer: dheidler@suse.de Test GUI Toolkits; Special SDK repo for SLE12
Reproducible¶
Fails since (at least) Build 0138
Expected result¶
Last good: 0137 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dheidler almost 5 years ago
- Subject changed from [functional][u] test fails in toolkits/prepare: sdk repo is not syned to osd to [functional][u] test fails in toolkits/prepare: sdk repo url is invalid
- Status changed from New to In Progress
- Assignee set to dheidler
Updated by dheidler almost 5 years ago
In testsuite toolkits_sle12
I changed the var:
-ADDONURL_SDK=ftp://openqa.suse.de/SLE-12-SP5-SDK-POOL-%ARCH%-Build0088-Media1/
+ADDONURL_SDK=ftp://openqa.suse.de/SLE-12-SP5-SDK-POOL-%ARCH%-Media1-CURRENT/
Updated by dheidler almost 5 years ago
- Status changed from In Progress to Feedback
Updated by okurz almost 5 years ago
dheidler wrote:
In testsuite
toolkits_sle12
I changed the var:-ADDONURL_SDK=ftp://openqa.suse.de/SLE-12-SP5-SDK-POOL-%ARCH%-Build0088-Media1/ +ADDONURL_SDK=ftp://openqa.suse.de/SLE-12-SP5-SDK-POOL-%ARCH%-Media1-CURRENT/
I guess I do not need to tell that this is a timebomb?
Updated by dheidler almost 5 years ago
Why should it?
I would expect that the current SDK is always in place.
Updated by okurz almost 5 years ago
Yes, sure. But it will not necessarily be the correct one. There is a build of base SLES and a corresponding build of SDK. The two need to be corresponding to be compatible. Also, retriggering might pick up a different SDK and change test results.
Updated by mgriessmeier almost 5 years ago
- Status changed from Resolved to Feedback
I agree with okurz here - we cannot rely on having always the correct one copied to CURRENT
- why not just use %BUILD_SDK%
?
Updated by dheidler almost 5 years ago
I didn't even know about that var - I was actually expecting that the build number would be the same as the one of the sle build but as I didn't find one in the ftp tree I just used the current entry.
Updated to:
ADDONURL_SDK=ftp://openqa.suse.de/SLE-12-SP5-SDK-POOL-%ARCH%-Build%BUILD_SDK%-Media1/
Updated by SLindoMansilla almost 5 years ago
- Status changed from Feedback to Resolved
Verified on OSD: https://openqa.suse.de/tests/2992499#next_previous