coordination #34996
closed[qe-core][functional][opensuse][epic] test fails in systemd_testsuite - TEST-16-EXTEND-TIMEOUT works only when executed against systemd built in the same specfile
100%
Description
The systemd test suite is tested in QA using the test suite suse_patches-systemd_testsuite:
- Scenario opensuse-Tumbleweed-DVD-x86_64-suse_patches-systemd_testsuite@64bit: osd#656311/modules/systemd_testsuite/steps/49
The problem happens when the package systemd-qa-testsuite is built separated from systemd itself (tblume, could you elaborate here the technical reason why this happens?)
This issue affects only Factory/Tumbleweed, which uses systemd version 237.
It doesn't happen on SLE15 nor Leap 15, that use systemd version 234.
To fix this issue we should build systemd-qa-testsuite in the same OBS package. systemd-qa-testsuite has a lot of patches which are not in a acceptable state to be accepted into Factory. The patches has to follow the guidelines (https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines) and the guidelines of https://github.com/openSUSE/systemd maintainers.
Acceptance criteria¶
- AC1: systemd-qa-testsuite patches are acceptable for openSUSE Factory.
- AC2: systemd-qa-testsuite is accepted to be built as a sub package of OBS package systemd.
Tasks¶
- Try to resolve one patch per Sprint. Upstream: https://github.com/systemd/systemd
Further details¶
Always latest result in this scenario: latest
Updated by SLindoMansilla over 6 years ago
- Related to action #32614: [opensuse][functional][u][systemd] systemd_testsuite fails, as it does not cope with the split of systemd-container added
Updated by okurz over 6 years ago
- Due date set to 2018-05-22
- Target version set to Milestone 16
Updated by oorlov over 6 years ago
- Subject changed from [functional][opensuse][u] test fails in systemd_testsuite - TEST-16-EXTEND-TIMEOUT works only when executed against systemd built in the same specfile to [functional][opensuse][u][medium] test fails in systemd_testsuite - TEST-16-EXTEND-TIMEOUT works only when executed against systemd built in the same specfile
- Description updated (diff)
- Status changed from New to Workable
- Difficulty set to medium
Updated by okurz over 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: suse_patches-systemd_testsuite
https://openqa.opensuse.org/tests/677208
Updated by SLindoMansilla over 6 years ago
- Status changed from Workable to In Progress
- Assignee set to SLindoMansilla
Updated by SLindoMansilla over 6 years ago
tblume told me that the initrd parameter is missing:
-initrd /boot/initrd-SVERSION
in the test-functions script this is here:
default_suse_initrd=/boot/initrd-${KERNEL_VER}
Updated by SLindoMansilla over 6 years ago
PR to fix missing initrd parameter:
- https://github.com/openSUSE/systemd/pull/14
- Upstream should go first: https://github.com/systemd/systemd/pull/9029
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-05-22 to 2018-06-05
Updated by SLindoMansilla over 6 years ago
PR was merged: https://github.com/systemd/systemd/pull/9029
Waiting for backport into Tumbleweed.
Updated by SLindoMansilla over 6 years ago
- Related to action #36754: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation added
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-06-05 to 2018-06-19
- Target version changed from Milestone 16 to Milestone 17
Updated by okurz over 6 years ago
SLindoMansilla wrote:
Waiting for backport into Tumbleweed.
where can we follow on with this? This ticket here hasn't moved since 14 days now
Updated by SLindoMansilla over 6 years ago
Well, actually I was working on this one for SLE15: https://progress.opensuse.org/issues/36754
This ticket about TW is not blocked, because I can apply the patch following the guidelines.
Updated by SLindoMansilla over 6 years ago
btw, patch is now backported: https://github.com/openSUSE/systemd/blob/openSUSE-Factory/test/test-functions
Updated by okurz over 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-06-19 to 2018-07-03
Updated by SLindoMansilla over 6 years ago
SR to organized patches on factory under factory first rule: https://build.opensuse.org/request/show/618101
Updated by SLindoMansilla over 6 years ago
SR to backport and reorganized systemd patches for Leap/SLE 15: https://build.opensuse.org/request/show/618533
Updated by okurz over 6 years ago
- Priority changed from Normal to High
As discussed with SLindoMansilla: We should make sure that the systemd test scenario for openSUSE Tumbleweed does not show up as failure in the validation job group anymore, the least we can do – this is what we decided for – is to move the test scenario to the "test development" job group, make sure it's properly labeled and then continue with less urgency to provide fixes to the systemd+tests package. AFAIU that means providing patches to upstream systemd and waiting for their acceptance and then having these changes included in the upstream-pulled packages as on top of the openSUSE patches packaging policy the systemd team wants to avoid maintaining any upstream acceptable packages – even temporary – within the openSUSE packages.
Updated by SLindoMansilla over 6 years ago
- Subject changed from [functional][opensuse][u][medium] test fails in systemd_testsuite - TEST-16-EXTEND-TIMEOUT works only when executed against systemd built in the same specfile to [functional][opensuse][u][epic] test fails in systemd_testsuite - TEST-16-EXTEND-TIMEOUT works only when executed against systemd built in the same specfile
- Status changed from In Progress to Workable
This task will be split to handle patches separately.
How to handle patches: See https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
Updated by SLindoMansilla over 6 years ago
- Description updated (diff)
- Difficulty changed from medium to hard
Updated by SLindoMansilla over 6 years ago
I have moved the test suite suse_patches-systemd_testsuite from Tumbleweed job group to Development Tumbleweed, because it fails since a long time and the expected "fix" is not expected before 6 weeks, maybe even longer.
Updated by okurz over 6 years ago
- Target version changed from Milestone 17 to Milestone 19
Updated by okurz about 6 years ago
- Target version changed from Milestone 19 to Milestone 21
@SLindoMansilla has the "expected fix" arrived by now or would this need your help?
Updated by SLindoMansilla about 6 years ago
There is no fix coming. This task needs each individual subtask to be resolved (aka. patches put in a way that openSUSE Factory can take them) and then submitting this package to Factory.
Updated by SLindoMansilla almost 6 years ago
- Related to action #45158: [systemd] Implement systemd testsuite as openQA perl module added
Updated by SLindoMansilla almost 6 years ago
- Status changed from Workable to Blocked
Blocked by #45158
Updated by SLindoMansilla almost 6 years ago
- Related to deleted (action #45158: [systemd] Implement systemd testsuite as openQA perl module)
Updated by SLindoMansilla almost 6 years ago
- Blocked by action #45158: [systemd] Implement systemd testsuite as openQA perl module added
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21 to future
due to blocker
Updated by mgriessmeier almost 5 years ago
- Blocked by deleted (action #45158: [systemd] Implement systemd testsuite as openQA perl module)
Updated by szarate about 4 years ago
- Tracker changed from action to coordination
- Status changed from Blocked to New
- Difficulty deleted (
hard)
Updated by szarate about 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [functional][opensuse][u][epic] test fails in systemd_testsuite - TEST-16-EXTEND-TIMEOUT works only when executed against systemd built in the same specfile to [qe-core][functional][opensuse][epic] test fails in systemd_testsuite - TEST-16-EXTEND-TIMEOUT works only when executed against systemd built in the same specfile