lsb

Failure in /olver/process/meta/tests/getpriority_spec 828

Bug #1335255 reported by Jeff Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lsb
In Progress
Medium
Unassigned
Mandriva
In Progress
Medium

Bug Description

/olver/process/meta/tests/getpriority_spec 828 failed Known problem
Message from the test:

failure 168
--------------------------------
POSTCONDITION_FAILED
Requirement failed: {getpriority.09.02} Function executed successfully with EOK
error code, while `( which != 1 && which != 0 && which != 2 ) || isEmpty_Set(
processes ) == true` means that EINVAL SHALL be set
--------------------------------
Registered bug: bug828(getpriority)

Problem info:

The getpriority() and setpriority() functions shall fail if:
[ESRCH]
No process could be located using the which and who argument values specified.
[EINVAL]
The value of the which argument was not recognized, or the value of the who
argument
is not a valid process ID, process group ID, or user ID.
But getpriority() and setpriority() returns EOK if no process could be located
using the which and who argument values specified or if the value of the which
argument was not recognized, or the value of the who argument is not a valid
process ID, process group ID, or user ID.
Additional information about this bug may be found at
http://linuxtesting.org/results/report?num=S0828

Also another test is failing

/olver/process/meta/tests/setpriority_spec 829 failed Known problem
Message from the test:

failure 167
--------------------------------
POSTCONDITION_FAILED
Requirement failed: {setpriority.09.01} Function executed successfully with EOK
error code, while `isEmpty_Set( processes ) == true` means that ESRCH SHALL be
set
--------------------------------
Registered bug: bug829(setpriority)

Comment:

Test Purpose Comment: Check requirement

Open the journal:

/var/opt/lsb/test/manager/results/x86-64-pes-guest-83.lab.eng.brq.redhat.com-2013-11-13-14h-33m-28s/results/olver.journal:15082
Problem info:

The getpriority() and setpriority() functions shall fail if:
[ESRCH]
No process could be located using the which and who argument values specified.
[EINVAL]
The value of the which argument was not recognized, or the value of the who
argument
is not a valid process ID, process group ID, or user ID.
But getpriority() and setpriority() returns EOK if no process could be located
using the which and who argument values specified or if the value of the which
argument was not recognized, or the value of the who argument is not a valid
process ID, process group ID, or user ID.
Additional information about this bug may be found at
http://linuxtesting.org/results/report?num=S0829

Tags: update
Changed in mandriva:
importance: Unknown → Medium
status: Unknown → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.