action #30478
closed
[sles][functional][u][sporadic][hard] test fails in snapper_cleanup: btrfs quote rescan times out, maybe extend timeout?
Added by mgriessmeier over 6 years ago.
Updated about 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-extra_tests_filesystem@64bit fails in
snapper_cleanup
Reproducible¶
Fails since (at least) Build 419.1
Expected result¶
Last good: 414.13 (or more recent)
Tasks¶
- Investigate issue and find the root cause
- Apply solution to make it stable, or if not trivial - create a new ticket for that
- Perform many runs to get statistics
Further details¶
Always latest result in this scenario: latest
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_filesystem
https://openqa.suse.de/tests/1467662
- Due date set to 2018-03-13
- Priority changed from Normal to High
- Description updated (diff)
- Status changed from New to Workable
- Subject changed from [sles][functional][sporadic] test fails in snapper_cleanup: btrfs quote rescan times out, maybe extend timeout? to [sles][functional][sporadic][hard] test fails in snapper_cleanup: btrfs quote rescan times out, maybe extend timeout?
setting to hard because it's sporadic
It didn't fail in 20 days, we still need to increase the timeout?
- Status changed from Workable to Blocked
- Assignee set to JERiveraMoya
Please add a comment in the test suite describing why we need the 40GB HDDSIZE. I do not think we should do this by default. Moreover I doubt this will work because the test uses a generated HDD. How should the disk be made bigger magically?
The two bugs you mentioned are actually the same.
- Due date changed from 2018-03-13 to 2018-04-10
- Target version changed from Milestone 14 to Milestone 15
yes, good catch! I saw that you delete the 40GB from the child job (as no magic was applied). Both bugs are practically the same and mention problem with short memory, but I pasted twice the same link, I cannot find the other one now, but this one is the most related: https://bugzilla.suse.com/show_bug.cgi?id=1051920
Increased size for the parent job that create the image create_hdd_textmode and added comment to this test suite.
hm, ok. I would prefer though to not change the test suites when a hypothesis has not been confirmed. Better either run it locally or just call clone-job with individual test changes, e.g. clone-job <job_id> HDDSIZEGB=40 to check.
- Status changed from Blocked to In Progress
No actual works on this task during sprint #14.
Failure is still sporadic. Bug is still open considered by developers with low priority due to seems a memory issue.
Created locally parent image with 40GB and 10 child jobs currently running (most of then atm passing)
- Subject changed from [sles][functional][sporadic][hard] test fails in snapper_cleanup: btrfs quote rescan times out, maybe extend timeout? to [sles][functional][u][sporadic][hard] test fails in snapper_cleanup: btrfs quote rescan times out, maybe extend timeout?
- Due date changed from 2018-04-10 to 2018-04-24
- Status changed from In Progress to Blocked
- Status changed from Blocked to Resolved
worked for last 18 Days, so let's resolve this
Also available in: Atom
PDF