PriorityQueue tests failing seemingly at random about chiselverify HOT 4 OPEN

will do!

from chiselverify.

Having been over the code quite thoroughly now, I believe this issue stems from calling scala.util.Random directly without a seed instead of instantiating and initializing one for subsequent use. As this is done on several occasions (in MemoryTest.scala, for example), the order the tests are executed in may affect whether they fail or not.

Unfortunately, a similar thing is done within the chiselverify.assembly component where fixing it might be a bit more troublesome.

from chiselverify.

Why was this closed? The issue still persists and it doesn't look great to keep having random red crosses in PRs and on the main branch.

from chiselverify.

I see that now, sorry I thought this had been solved

from chiselverify.