On Mon, Jan 28, 2019 at 8:37 AM Nick Desaulniers <ndesaulniers@xxxxxxxxxx> wrote: > So this test has been broken? If so, do you know for how long? Or > who's monitoring them? Either way, thanks for noticing and fixing. No, it's been working fine. It just consumes 100% cpu during the spin-wait. The intention was to sleep for a little bit to avoid a tight loop. It was just resource-inefficient. -- Kees Cook
