On Tue, Jul 13, 2021 at 10:20 PM Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote: > > It was either a script bug (but I haven't seen this one before) > or a user error (more likely). > My daily linux-next builds are started by a cron job but the don't > always start when they should (IMO), so I may have started it > manually... but then the error that I saw would have only happened > if 2 linux-next builds were started at almost the same time (one > by cron, one manually by me) - I don't know if that happened or not. > > Today's linux-next builds didn't have any similar problem and I doubt > that I can reconstruct what happened exactly. I see -- it should be unlikely that someone else sees it then. Thanks! Cheers, Miguel
