getrusage04 from ubuntu_ltp_syscalls failed on T-4.15 Azure

Bug #1841425 reported by Po-Hsu Lin on 2019-08-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-azure (Ubuntu)
Undecided
Unassigned
Trusty
Undecided
Unassigned

Bug Description

Test failed with:

<<<test_start>>>
tag=getrusage04 stime=1566816628
cmdline="getrusage04"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
sh: 1: systemd-detect-virt: not found
sh: 1: systemd-detect-virt: not found
getrusage04 0 TINFO : Expected timers granularity is 4000 us
getrusage04 0 TINFO : Using 1 as multiply factor for max [us]time increment (1000+4000us)!
getrusage04 0 TINFO : utime: 1384us; stime: 0us
getrusage04 0 TINFO : utime: 1384us; stime: 932us
getrusage04 0 TINFO : utime: 1384us; stime: 8609us
getrusage04 1 TFAIL : getrusage04.c:133: stime increased > 5000us:
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=1
<<<test_end>>>

It uses systemd-detect-virt to check for VM environment, and bails out the test with:
 if (tst_is_virt(VIRT_XEN) || tst_is_virt(VIRT_KVM))
  tst_brkm(TCONF, NULL, "This testcase is not supported on this"
          " virtual machine.");

Looks like the test will be skipped from Bionic Azure test result.
But this tool is not available for Trusty and this test failed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.15.0-1045-azure 4.15.0-1045.49~14.04.1
ProcVersionSignature: User Name 4.15.0-1045.49~14.04.1-username 4.15.18
Uname: Linux 4.15.0-1045-azure x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Mon Aug 26 10:50:35 2019
SourcePackage: linux-signed-azure
UpgradeStatus: No upgrade log present (probably fresh install)

Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew) wrote :

Test result on Bionic Azure:
  getrusage04 1 TCONF : getrusage04.c:202: This testcase is not supported on this virtual machine.
  getrusage04 2 TCONF : getrusage04.c:202: Remaining cases not appropriate for configuration

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers