Project

General

Profile

action #65699

[kernel][sporadic][ltp] test fails in clock_gettime03 - wrong offset (CLOCK_MONOTONIC)

Added by pcervinka 4 months ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
SUSE QA tests - Planned - kernel&network
Start date:
2020-04-16
Due date:
% Done:

0%

Estimated time:
Difficulty:
Duration:

Description

Observation

openQA test in scenario sle-15-SP2-Online-x86_64-ltp_syscalls_debug_pagealloc@64bit fails in
clock_gettime03

Test suite description

maintainer: pvorel, rpalethorpe. A large collection of tests for individual system calls. This is generally considered to be the most important test suit within the LTP. The IPC tests have been filtered out from the syscalls runtest file. They are ran as part of the syscalls_ipc test case.
NOTE: for GRUB_BOOT_NONDEFAULT=1 depends on order in GRUB_PARAM in install_ltp job.

Reproducible

Fails since (at least) Build 143.1

Expected result

Last good: 142.1 (or more recent)

Further details

Always latest result in this scenario: latest

Most probably related to virtual environment, we should probably run it on bare metal only.

clock_gettime03.c:63: PASS: Offset (CLOCK_MONOTONIC) is correct 10001ms
clock_gettime03.c:73: PASS: Offset (CLOCK_MONOTONIC) is correct 1ms
clock_gettime03.c:63: PASS: Offset (CLOCK_BOOTTIME) is correct 10001ms
clock_gettime03.c:73: PASS: Offset (CLOCK_BOOTTIME) is correct 1ms
clock_gettime03.c:60: FAIL: Wrong offset (CLOCK_MONOTONIC) read -9999ms
clock_gettime03.c:73: PASS: Offset (CLOCK_MONOTONIC) is correct 1ms
clock_gettime03.c:63: PASS: Offset (CLOCK_BOOTTIME) is correct -10000ms
clock_gettime03.c:73: PASS: Offset (CLOCK_BOOTTIME) is correct 0ms
clock_gettime03.c:63: PASS: Offset (CLOCK_MONOTONIC_RAW) is correct 100000ms
clock_gettime03.c:73: PASS: Offset (CLOCK_MONOTONIC_RAW) is correct 0ms
clock_gettime03.c:63: PASS: Offset (CLOCK_MONOTONIC_COARSE) is correct 100000ms
clock_gettime03.c:73: PASS: Offset (CLOCK_MONOTONIC_COARSE) is correct 0ms

History

#1 Updated by metan 4 months ago

Looks like a rounding error on my side, I will have to check the code and assertions. Also this should be definitely analyzed before LTP release, so I should look into it soon.

#2 Updated by okurz 3 months 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_slub_debug
https://openqa.suse.de/tests/4222961

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

#3 Updated by okurz 3 months 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_debug_pagealloc
https://openqa.suse.de/tests/4281215

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

#4 Updated by openqa_review 2 months 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_slub_debug
https://openqa.suse.de/tests/4327752

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

Also available in: Atom PDF