Project

General

Profile

Actions
Copy link

action #77260

closed

splice02 fails in JeOS

Added by mloviska over 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
pvorel
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-11-10
Due date:
% Done:

70%

Estimated time:
Difficulty:
Tags:
jeos, qac, ltp

Description

Observation

openQA test in scenario sle-15-SP2-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-on-kvm_syscalls@uefi-virtio-vga fails in
splice02

Test suite description

Excluded test cases:
quotactl* => quota modules are missing in JeOS
msgstress* => excluded as in server LTP testing

tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
splice02.c:30: TPASS: splice() system call Passed

Summary:
passed   1
failed   0
skipped  0
warnings 0
### TEST splice02 COMPLETE >>> 141

I haven't reproduced the issue outside of openQA.

Reproducible

Fails since (at least) Build 5.2

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz over 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5128870

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #2

Updated by okurz over 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5193875

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #3

Updated by openqa_review over 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5212937

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #4

Updated by okurz about 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5303661

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #5

Updated by okurz about 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5294577

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #6

Updated by okurz about 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5359939

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #7

Updated by openqa_review about 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5359939

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #8

Updated by jlausuch about 3 years ago

@pcervinka could kernel-qa team offer some help here? This issue only happens in JeOS and it's not reproducible manually.

Actions
Copy link
 #9

Updated by okurz about 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5425925

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #10

Updated by openqa_review about 3 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: jeos-ltp-on-kvm_syscalls
https://openqa.suse.de/tests/5425925

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #11

Updated by mloviska about 3 years ago

Does not fail in arm image testing

# wait_serial expected: qr/### TEST splice02 COMPLETE >>> \d+/u
# Result:

tst_test.c:1288: TINFO: Timeout per run is 0h 05m 00s
splice02.c:30: TPASS: splice() system call Passed

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0
### TEST splice02 COMPLETE >>> 0
Actions
Copy link
 #12

Updated by favogt about 3 years ago

Test process returned unkown none zero value (141).

This can happen if the process was killed by a SIGPIPE signal, which is number 13. -13 == 141 with 8-bit signed ints.

Actions
Copy link
 #13

Updated by favogt about 3 years ago

favogt wrote:

Test process returned unkown none zero value (141).

This can happen if the process was killed by a SIGPIPE signal, which is number 13. -13 == 141 with 8-bit signed ints.

Found it:

openQA runs seq 1 20000 | splice02; echo "### TEST splice02 COMPLETE >>> $?", but splice02 may exit before seq can write everything. In that case, seq is terminated with SIGPIPE and returns 141. I suggest to either use (seq 1 20000 || :) | splice02 or echo "### TEST splice02 COMPLETE >>> ${PIPESTATUS[1]}.

Actions
Copy link
 #14

Updated by mloviska about 3 years ago

  • Status changed from New to In Progress
  • Assignee set to mloviska

favogt wrote:

favogt wrote:

Test process returned unkown none zero value (141).

This can happen if the process was killed by a SIGPIPE signal, which is number 13. -13 == 141 with 8-bit signed ints.

Found it:

openQA runs seq 1 20000 | splice02; echo "### TEST splice02 COMPLETE >>> $?", but splice02 may exit before seq can write everything. In that case, seq is terminated with SIGPIPE and returns 141. I suggest to either use (seq 1 20000 || :) | splice02 or echo "### TEST splice02 COMPLETE >>> ${PIPESTATUS[1]}.

Perfect catch! Thanks for your help, I will try to update it according to your suggestion.

Actions
Copy link
 #15

Updated by pvorel about 3 years ago

  • Assignee changed from mloviska to pvorel

@favogt: Thanks a lot for help (again :).
Martin opened PR (https://github.com/linux-test-project/ltp/pull/796) and even sent patchset to ML
(https://patchwork.ozlabs.org/project/ltp/patch/20210303132403.6427-1-mloviska@suse.de/).

But metan (main LTP maintainer) requests proper fix: to generate it's input in C without relying on shell piping data into it. I agreed with mloviska, that I implement it.

Actions
Copy link
 #16

Updated by pvorel about 3 years ago

  • Tags changed from qac, jeos to qac, jeos, ltp
  • % Done changed from 0 to 70
Actions
Copy link
 #18

Updated by pvorel about 3 years ago

Contributed patchset [1] which works [2], but Cyril requests some more changes.

[1] https://patchwork.ozlabs.org/project/ltp/patch/20210308154421.2002-1-pvorel@suse.cz/
[2] http://quasar.suse.cz/tests/6129

Actions
Copy link
 #19

Updated by okurz about 3 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: jeos-ltp-syscalls
https://openqa.suse.de/tests/5671063

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #20

Updated by openqa_review about 3 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: jeos-ltp-syscalls
https://openqa.suse.de/tests/5671063

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #25

Updated by pvorel almost 3 years ago

  • Status changed from In Progress to Feedback

Finally merged (v6): https://github.com/linux-test-project/ltp/commit/b1a656559506796b1abc2b8285058ba1f9a595b5

I also added shell pipe test into runtest/smoketest and runtest/commands. Maybe one of them would be worth of running on JeOS
https://github.com/linux-test-project/ltp/commit/cba8a25b6cb92677615cd13875245a5a2fb7385e

Actions
Copy link
 #26

Updated by mloviska almost 3 years ago

pvorel wrote:

Finally merged (v6): https://github.com/linux-test-project/ltp/commit/b1a656559506796b1abc2b8285058ba1f9a595b5

I also added shell pipe test into runtest/smoketest and runtest/commands. Maybe one of them would be worth of running on JeOS
https://github.com/linux-test-project/ltp/commit/cba8a25b6cb92677615cd13875245a5a2fb7385e

Yes, I have already thought of the commands test suite. I will add it in JeOS testing. Thanks for the heads up!

Actions
Copy link
 #27

Updated by mloviska almost 3 years ago

pvorel wrote:

Finally merged (v6): https://github.com/linux-test-project/ltp/commit/b1a656559506796b1abc2b8285058ba1f9a595b5

I also added shell pipe test into runtest/smoketest and runtest/commands. Maybe one of them would be worth of running on JeOS
https://github.com/linux-test-project/ltp/commit/cba8a25b6cb92677615cd13875245a5a2fb7385e

https://gitlab.suse.de/qac/qac-openqa-yaml/-/merge_requests/193

Actions
Copy link
 #28

Updated by jlausuch almost 3 years ago

pvorel wrote:

Finally merged (v6): https://github.com/linux-test-project/ltp/commit/b1a656559506796b1abc2b8285058ba1f9a595b5

I also added shell pipe test into runtest/smoketest and runtest/commands. Maybe one of them would be worth of running on JeOS
https://github.com/linux-test-project/ltp/commit/cba8a25b6cb92677615cd13875245a5a2fb7385e

We decided to include it for maintenance, not for current SP3 as it's too late to add more tests. But as soon as SP3 goes into maintenance, we will enable it.

Actions
Copy link
 #30

Updated by mloviska almost 3 years ago

  • Status changed from Feedback to Resolved

Resolving and kudos!

Actions
Copy link
 #31

Updated by jlausuch almost 3 years ago

Nice work. Thanks!

Actions
Copy link
 #32

Updated by okurz almost 3 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: jeos-ltp-syscalls
https://openqa.suse.de/tests/5998509

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link

Also available in: Atom PDF