On 6/12/23 18:35, enh wrote: > It's basically "find /dir -name '*.ko'" produces results, or it does not. > Not a > huge amount of subtlety there. Since it's no longer trying to discard > stderr > then if nothing is written to stderr, it most likely means there's > nothing in > that directory. (Even the directory not being there or not being readable > should > produce an error to stderr, which would show up in the log...) > > Which means it's a VM setup issue, which is not really my area. :) > > yeah, me neither. i suppose i should +Alistair Delva > <mailto:ade...@google.com> in case he's interested (internal bug for this was > https://b.corp.google.com/issues/279863718 > <https://b.corp.google.com/issues/279863718>). but the 0.08% failure rate > makes > me think this clearly isn't a normal state for those VMs to be in!
At one point earlier this year I hit a race condition in the kernel with make -j>1 where if the last target was "modules_install" it tried to run before the modules existed, but I'm not reproducing it at the moment... Rob _______________________________________________ Toybox mailing list Toybox@lists.landley.net http://lists.landley.net/listinfo.cgi/toybox-landley.net
