[Bug time/14096] Race condition on timezone/tst-timezone.out
cvs-commit at gcc dot gnu.org
sourceware-bugzilla@sourceware.org
Wed Jun 7 17:15:00 GMT 2017
https://sourceware.org/bugzilla/show_bug.cgi?id=14096
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via bd6193907a09f874553886f0986ba16b961fab8d (commit)
from 2e87c7d1582461044f8cd983fd9be121cf23803f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=bd6193907a09f874553886f0986ba16b961fab8d
commit bd6193907a09f874553886f0986ba16b961fab8d
Author: Joseph Myers <joseph@codesourcery.com>
Date: Wed Jun 7 17:14:28 2017 +0000
Fix tst-timezone race (bug 14096).
I observed a failure of timezone/tst-timezone with the same symptoms
as reported in bug 14096.
I was unable to reproduce the failure on testing again. However, from
inspection, the cause is as follows. tst-timezone uses time zones
compiled from the northamerica file, but has no dependency on any such
zones, so with a parallel build it is possible that they do not get
compiled until after tst-timezone is run. This patch adds a
dependency on the compiled America/New_York zone (the one used as a
makefile target to cause such zones to be compiled, rather than one
which is actually used in that test) to fix the race.
Tested for x86_64.
[BZ #14096]
* timezone/Makefile ($(objpfx)tst-timezone.out): Depend on
America/New_York.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 6 ++++++
timezone/Makefile | 1 +
2 files changed, 7 insertions(+), 0 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Glibc-bugs
mailing list