Bug 1654819

Summary:	glibc: Test suite failure: posix/tst-spawn
Product:	[Fedora] Fedora	Reporter:	Arjun Shankar <ashankar>
Component:	glibc	Assignee:	Carlos O'Donell <codonell>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	31	CC:	arjun, codonell, dj, fweimer, law, mfabian, pfrankli, rth, siddhesh
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glibc-2.29.9000-18.fc31	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-30 14:34:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1659512

Description Arjun Shankar 2018-11-29 18:43:27 UTC

I'm filing this bug to track the triaging of the cause of a test failure at build time:

Task: https://koji.fedoraproject.org/koji/taskinfo?taskID=31142692
Build: glibc-2.28.9000-21.fc30
Test: posix/tst-spawn

Comment 1 Carlos O'Donell 2018-11-29 19:04:32 UTC

Extracted from the build.log's detailed test failure data:

=====FAIL: posix/tst-spawn.out=====
tst-spawn.c:100: numeric comparison failure
   left: 0 (0x0); from: xlseek (fd2, 0, SEEK_CUR)
  right: 28 (0x1c); from: strlen (fd2string)
error: 1 test failures
tst-spawn.c:229: numeric comparison failure
   left: 1 (0x1); from: WEXITSTATUS (status)
  right: 0 (0x0); from: 0
error: 1 test failures
=====FAIL: posix/tst-spawn.test-result=====
FAIL: posix/tst-spawn
original exit status 1

I don't know what could have caused this failure.

It looks like the fd was closed, and so ended up at a current position of 0 instead of 28. I don't know why that would happen in the trivial test scenario.

Comment 2 Carlos O'Donell 2018-11-29 19:55:28 UTC

+ uname -a
Linux buildhw-07.phx2.fedoraproject.org 4.18.10-200.fc28.x86_64 #1 SMP Wed Sep 26 09:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Model name:          Intel(R) Xeon(R) CPU E5-2670 v3 @ 2.30GHz

Comment 3 Patsy Griffin 2019-05-14 01:28:05 UTC

This should be fixed in rawhide by this upstream patch:

commit 114f792eaea2505cd8aee02d330aad37238da6a5
Author: Stefan Liebler <stli.com>
Date:   Fri Feb 1 11:03:35 2019 +0100

    posix/tst-spawn: Fix racy tests in spawned processes.

Comment 4 Ben Cotton 2019-08-13 19:13:45 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.