action #112676
open[qe-core] All tests fails in dracut_enhanced
0%
Description
Observation¶
dracut_enhanced is a series of upstream tests. Because ALL of them fail and because the only error message in dracut_enhanced-dracut-testsuite-logs.tar.bz2 is
./test.sh: line 307: /test-functions: No such file or directory
this looks like a problem with setting up the test for 15SP4.
Acceptance Criteria¶
- AC1: Compare tests on IBS and tests here, coordinating with the maintainer
- AC2: Make at least one test succeed
- AC3: File bugs for the tests that do not succeed.
Reproducible¶
Fails since (at least) Build 20220615-1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by punkioudi almost 2 years ago
@dvenkatachala do you have any update on this ticket? :)
Updated by dvenkatachala almost 2 years ago
No Anna, I do not have much idea on this ticket.
Updated by mloviska almost 2 years ago
- Status changed from New to In Progress
- Assignee set to mloviska
Updated by mloviska almost 2 years ago
I am afraid this wont be an easy fix as the former patches are not applicable any more and the test structure with helper functions have been extracted to other scripts.
Maybe we should run the tests as they are designed (in qemu) but that would mean we need to refactor the whole test case.
Updated by punkioudi almost 2 years ago
@mloviska for some reason I don't get the notifications in progress the last days, so sorry for the delay :/
Question: I think that unfortunately we cannot see right now if there is a product issue and on the other hand, there are 3 testsuites failing because of this issue.
My proposal here would be to exclude these testsuites till and probably re-write/refactor the test.
Wdyt??
Updated by mloviska almost 2 years ago
punkioudi wrote:
@mloviska for some reason I don't get the notifications in progress the last days, so sorry for the delay :/
Question: I think that unfortunately we cannot see right now if there is a product issue and on the other hand, there are 3 testsuites failing because of this issue.
My proposal here would be to exclude these testsuites till and probably re-write/refactor the test.
Wdyt??
Yes, we should remove it for now. I can do that. AFAICT the original upstream test case is fine as I have run it manually, and it has shown no issues. The problem is here how we are trying to patch it and execute it
Updated by mloviska almost 2 years ago
- Status changed from In Progress to Workable
- Priority changed from Immediate to Normal
Updated by mloviska almost 2 years ago
- Related to action #97007: [qa-core] test fails in dracut_enhanced added
Updated by szarate almost 2 years ago
Rather than keeping trying to run these tests, let's double check if those are being ran already on IBS/OBS, and contact peeps from Boot & Init to find a test that could be doing a similar job.
Updated by szarate almost 2 years ago
- Sprint set to QE-Core: July Sprint (Jul 06 - Aug 03)
Updated by mloviska almost 2 years ago
- Status changed from Workable to In Progress
- Assignee set to mloviska
Updated by mloviska almost 2 years ago
- Status changed from In Progress to Blocked
Update from Boot & Init team:
Thomas Blume and Robert Richardson are working on new patches as they are required to for the upstream tests any way to be executable for SUSE and together with openQA integration. We will be notified later on.
I will set this ticket to blocked.
Updated by mloviska over 1 year ago
Systemd devs are almost ready with the patch, only few fixes are left and we are good to reschedule the test suites
http://moore.arch.suse.de/tests/5329#
Updated by mloviska over 1 year ago
Updated by szarate over 1 year ago
- Tags set to #bugbusters
- Description updated (diff)
We should takeover Robert's PR (I think he's on another team atm), Martin do you have any suggestions?
Updated by mloviska over 1 year ago
szarate wrote:
We should takeover Robert's PR (I think he's on another team atm), Martin do you have any suggestions?
Oh, forgot about the PR :facepalm:. I think it is eligible to merge as it is, as we do not really schedule the whole test suite as of now.
Updated by szarate about 1 year ago
- Tags changed from #bugbusters to bugbusters
Updated by mgrifalconi 11 months ago
- Status changed from Blocked to Workable
Hi, according to the latest comments, it appears that the issue is not blocked but can be worked on.