Re: Today's problem with GUB build

[Jonas Hahnfeld]

Am Mittwoch, den 15.07.2020, 21:35 +0200 schrieb David Kastrup:
> Jonas Hahnfeld <hahnjo@hahnjo.de> writes:
> > Am Mittwoch, den 15.07.2020, 17:31 +0100 schrieb Phil Holmes:
> > > Here's the logfile and the ly file.
> > 
> > Could this be collisions of the random file names generated for
> > temporary files? The argument to backend-library.scm:248 comes
> > from create-file-exclusive which returns #f if the file already exists
> > (or could not be created).
> 
> I had commented on the respective issue without response that the
> parallel processes, without taking additional measures, will generate
> the same "random" sequence, making this no better than just using
> sequential numbers.

"additional measures" are in place: multi-fork calls randomize-rand-
seed *after* forking. The seed is initialized based on the current
timestamp (might be the same) and the pid (different in the course of
one run). We can still have collisions, but the amount of trouble (or
rather the lack of reports until now) indicates that it is better than
sequential numbers. This was discussed (and answered) in the review.

signature.asc
Description: This is a digitally signed message part