action #58388
closed[qam] LTP on SP1: fallocate05 fails now
0%
Description
https://openqa.suse.de/tests/3493708#step/fallocate05/7
it's not new, it was just whitelisted by mistake for 2 weeks
> I've added an exit code filter to the entry in ltp_known_issues yesterday which limits the whitelist only to the failures caused by known bugs in the test
the SP1 failure is not related to the known bugs so it's not softfailing anymore
Updated by okurz over 4 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: ltp_syscalls_pre12sp4
https://openqa.suse.de/tests/3552025
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by MDoucha over 4 years ago
- Status changed from New to Rejected
This is a kernel bug. Btrfs in kernel 3.12.74 most likely treats fallocate()d blocks as full of data before they were actually written to so the first write() tries to copy the reserved blocks and fails because the disk is intentionally full. The bug is not worth fixing at this stage in 12SP1 lifecycle so I'm closing this without creating a BSC.
Updated by MDoucha over 4 years ago
coolo wrote:
Did you whitelist this test then?
Yes. https://openqa.suse.de/tests/3584186#step/fallocate05/9