Project

General

Profile

action #111110

[Minimal-VM][aarch64] LTP test fails in clock_gettime03 wrong offset (CLOCK_MONOTONIC)

Added by jlausuch about 1 month ago. Updated 28 days ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-05-15
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:

Description

Observation

openQA test in scenario sle-15-SP4-JeOS-for-kvm-and-xen-aarch64-jeos-ltp-containers@aarch64 fails in
clock_gettime03

Test suite description

Reproducible

Fails since (at least) Build 1.165

Expected result

Last good: 1.159 (or more recent)

Further details

Always latest result in this scenario: latest

This was spotted 2 years ago: https://progress.opensuse.org/issues/65699
and it started happening again in Minimal-VM (JeOS) quite often: https://openqa.suse.de/tests/8759735#next_previous

tst_kconfig.c:82: TINFO: Parsing kernel config '/proc/config.gz'
tst_test.c:1433: TINFO: Timeout per run is 0h 05m 00s
clock_gettime03.c:117: TINFO: Testing variant: vDSO or syscall with libc spec
clock_gettime03.c:78: TPASS: Offset (CLOCK_MONOTONIC) is correct 10003ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_MONOTONIC) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_BOOTTIME) is correct 10003ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_BOOTTIME) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_MONOTONIC) is correct -9997ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_MONOTONIC) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_BOOTTIME) is correct -9997ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_BOOTTIME) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_MONOTONIC_RAW) is correct 100002ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_MONOTONIC_RAW) is correct 3ms
clock_gettime03.c:75: TFAIL: Wrong offset (CLOCK_MONOTONIC_COARSE) read 100011ms
clock_gettime03.c:85: TFAIL: Wrong offset (CLOCK_MONOTONIC_COARSE) read 11ms
tst_test.c:1433: TINFO: Timeout per run is 0h 05m 00s
clock_gettime03.c:117: TINFO: Testing variant: syscall with old kernel spec
clock_gettime03.c:78: TPASS: Offset (CLOCK_MONOTONIC) is correct 10003ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_MONOTONIC) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_BOOTTIME) is correct 10003ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_BOOTTIME) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_MONOTONIC) is correct -9997ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_MONOTONIC) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_BOOTTIME) is correct -9997ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_BOOTTIME) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_MONOTONIC_RAW) is correct 100002ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_MONOTONIC_RAW) is correct 3ms
clock_gettime03.c:78: TPASS: Offset (CLOCK_MONOTONIC_COARSE) is correct 100000ms
clock_gettime03.c:88: TPASS: Offset (CLOCK_MONOTONIC_COARSE) is correct 0ms

Summary:
passed   22
failed   2
broken   0
skipped  0
warnings 0
### TEST clock_gettime03 COMPLETE >>> 1

In SLE, the test is passing for aarch64: https://openqa.suse.de/tests/8752207
and the history says it never failed.

History

#1 Updated by jlausuch about 1 month ago

Hi pcervinka, could someone from kernel team take a look?

#2 Updated by openqa_review 28 days 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-containers
https://openqa.suse.de/tests/8759735#step/clock_gettime03/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Also available in: Atom PDF