Fedora Account System
Red Hat Associate
Red Hat Customer
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
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.
+ 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
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.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.