The issue may have been the interactive docker session I was running it in.
The last few tests (150-157) were all taking until the timeout the lab uses
for unit tests (2 hours since the timeout was multiplied by 10). I had to
leave for the day so I restarted it in a non-interactive container and it
ran in 2 hours. If we were to just run the fast-tests suite, then it would
have taken 42 minutes to run. This is mostly due to timeouts
in eal_flags_c_opt_autotest, eal_flags_hpet_autotest, eal_flags_misc_autotest
and multiprocess_autotest, each taking 600 seconds. Finding out what caused
these to stall would bring the runtime down to 3 minutes. All of the
failures should be ASAN-related.

On Tue, Jun 15, 2021 at 3:43 AM David Marchand <david.marchand@redhat.com>
wrote:

> Hi Owen,
>
> On Mon, Jun 14, 2021 at 10:42 PM Owen Hilyard <ohilyard@iol.unh.edu>
> wrote:
> >
> > From what I've seen so far, that fixes the PCI leak. That just leaves a
> few other places. I'll try to get the complete list to you tomorrow, since
> running the full set of unit tests takes quite a few hours when ASAN is
> involved.
>
> Ok, thanks for the test.
> I'll send a patch on the pci bus.
>
> Just odd that it tooks hours in your case.
> On my f32 system, it took 3/4 minutes.
> It is probably worth looking why the difference.
> We can't have asan enabled at UNH otherwise.
>
>
> --
> David Marchand
>
>