Bug 176937

Summary:	NPTL: Process scheduling and semaphores
Product:	Red Hat Enterprise Linux 4	Reporter:	Tony Reix <tony.reix>
Component:	glibc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	drepper
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
URL:	http://nptl.bullopensource.org/Tests/TC2/report.php#problems
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-01-04 17:06:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tony Reix 2006-01-04 15:30:34 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
OPTS test:

sem_post/8-1.c

 	This test checks the higher priority processes get the semaphore first.
 	It looks the priority is not taken into account. 


Details are available at:
http://nptl.bullopensource.org/Tests/results/report.php
Browse: (TC2) 2xi686HT - RHAS4u2 Run 1,2,3

See:
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=11&testcase_id=3516

Version-Release number of selected component (if applicable):
Unmodified RHEL4u2

How reproducible:
Always

Steps to Reproduce:
Use OPTS.
(Used version was:  OPTS cvs repository on Nov 14, 2005)

Actual Results:  See:
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=11&testcase_id=3516

Additional info:

Comment 2 Tony Reix 2006-01-04 16:02:29 UTC

Use the 3 (correct !) URLS:

http://nptl.bullopensource.org/Tests/TC2/report.php#problems

http://nptl.bullopensource.org/Tests/results/run-browse.php
     Click the "Browse" button of : (TC2) 2xi686HT - RHAS4u2 Run 3
     You can also select 2 runs and click the "Compare Selected" button.

Comment 3 Ulrich Drepper 2006-01-04 17:06:50 UTC

There is no guarantee about scheduling determined by priority.