action #15876
closed[sles][functional]LTP tests utimensat01, writev01, writev03, and writev04 fail with 4.4.41 kernel
0%
Description
Build 0207 failed when running compiled ltp tests on all architectures
https://openqa.suse.de/tests/overview?distri=sle&version=12-SP3&build=0207&groupid=55
Files
Updated by michalnowak over 7 years ago
- Subject changed from toolchain fails when running compiled ltp to LTP tests utimensat01, writev01, writev03, and writev04 fail with 4.4.41 kernel
- Status changed from New to In Progress
- Target version set to Milestone 5
This occurred first in build 0207 (0206 was fine), where kernel 4.4.41-1.1 got introduced. Will see if it's bug (kernel, LTP) or we just need to use more recent LTP.
Updated by michalnowak over 7 years ago
- Status changed from In Progress to Feedback
Updated by michalnowak over 7 years ago
- Category set to Enhancement to existing tests
Proved in https://openqa.suse.de/tests/723257/file/gcc5_C_compilation-runltp.log. Need to wait for utimensat01 in kernel, or LTP patch.
Updated by okurz about 7 years ago
I am not quite sure I understand this ticket. What is necessary to make the toolchain jobs green on short-term?
Updated by michalnowak about 7 years ago
It's not entirely clear yet: http://marc.info/?l=linux-api&m=148586553318265&w=2.
It probably stays upstream, but we may choose to revert it in SLES for the sake of compatibility & patch LTP. It seems to me we don't know yet.
Updated by okurz about 7 years ago
Let me rephrase then: Do you have a better idea than just deleting the test module from the test plan until this is solved?
Updated by michalnowak about 7 years ago
My plan is to wait until it's resolved what should be in our kernel, and then fix or keep the failing utimensat01 LTP test. Removing the test means that the original problem is not on our radar anymore.
Updated by michalnowak about 7 years ago
Updated by michalnowak about 7 years ago
Milestone 5 review: No kernel resolution so far.
Updated by okurz about 7 years ago
- Target version changed from Milestone 5 to Milestone 6
Updated by michalnowak about 7 years ago
Talked to @metan yesterday: no solution upstream, nor in SUSE kernel, nor in LTP, yet.
Updated by okurz about 7 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: toolchain_zypper@ppc64le-smp
https://openqa.suse.de/tests/817418
Updated by SLindoMansilla about 7 years ago
Could you please check this: https://openqa.suse.de/tests/841139#step/gcc5_C_compilation/38
I think it can be related.
Updated by michalnowak about 7 years ago
SLindoMansilla wrote:
Could you please check this: https://openqa.suse.de/tests/841139#step/gcc5_C_compilation/38
I think it can be related.
It's bsc#1024050, reported additional logs to Bugzilla. Good catch.
Updated by maritawerner about 7 years ago
- Subject changed from LTP tests utimensat01, writev01, writev03, and writev04 fail with 4.4.41 kernel to [sles][functional]LTP tests utimensat01, writev01, writev03, and writev04 fail with 4.4.41 kernel
Updated by okurz almost 7 years ago
- Target version changed from Milestone 6 to Milestone 7
M6 is closed since some time. This was mentioned during the review meeting and discussed. bsc#1024050 is still open and not moving. But as not much time is wasted on waiting on this one we can shift it to the next milestone. But as we should aim to have all soft-fails fixed for the release of SLE 12 SP3 as well we should solve this issue here within M7, that is within the next 19 days.
Updated by michalnowak almost 7 years ago
- Status changed from Feedback to Resolved
We don't run LTP as part of SLE Functional openQA tests anymore.