Yes you are correct. This is a possible problem. Digging down a bit
TomEE :: TCK :: MicroProfile Config TCK 1 mn 38 s TomEE :: TCK :: MicroProfile Fault Tolerance TCK 1 h 11 mn TomEE :: TCK :: MicroProfile Health TCK 5 mn 6 s TomEE :: iTests :: MicroProfile JWT 11 mn TomEE :: TCK :: MicroProfile JWT TCK 1 mn 50 s TomEE :: TCK :: MicroProfile Metrics TCK 45 mn TomEE :: TCK :: MicroProfile Open API TCK 8 mn 21 s TomEE :: TCK :: MicroProfile Rest Client TCK 4 mn 8 s I'm running them all locally to get a taste of how long they actually should take in an ideal world. So we have some more materials to reach out to infra. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Oct 11, 2022 at 5:42 PM David Blevins <david.blev...@gmail.com> wrote: > > On Oct 11, 2022, at 2:33 AM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > > I can't measure without investing a lot of time, but looking at what > Maven > > reports > > CDI + BVal TCK around 25 min > > MicroProfile TCK 2 hours and a half > > There's definitely something going on with the build machines as the > MicroProfile TCK takes 1 or 2 minutes on my machine. > > I've seen issues before where the random number generator runs out of > entropy and basically stops any call to SecureRandom for several minutes > while it just sits there and waits for more random numbers to be generated. > > With all the signing and encryption in the MicroProfile TCK, I bet that's > what's going on. Not too sure what options we might have. > > We'd probably need something very simple we could use to show infra and > work with them on a solution. > > -David > >
