Kamil Jarosz

I have the exact same behavior on Gnome, Fedora 38

Right! Did not think about using nextest. :smile: Certainly has a better interface, but unfortunately tests are executing a bit longer :( I added nextest benchmarks to the table in...

This PR is just a suggestion, I tried speeding tests up somehow and noticed that at the end my CPU was sitting idle. Regarding the `fast` feature, I'm not sure...

Okay, I think I found out why nextest does not run tests marked as slow; I also found out why tests on nextest are slower compared to `cargo test`. Turns...

Created a new PR with these two commits: https://github.com/ruffle-rs/ruffle/pull/16031

> if anything, I'd go for increasing time duration That is better when we expect tests to fail instead of pass, but generally in CI it's way more probable for...

Refreshed this PR a bit to see how it performs as of today. I've removed the `fast` feature and did some tests (average out of 3 retries): | Test Command...

I think that would be easy to implement in `cargo test`, but I just don't see how I would do that in nextest: our code is executed only when tests...

It isn't trivial for nextest, but for `cargo test` I even remember having a PoC of something like that. But if we aren't planning on merging it anyway, taking the...

Updated slow tests, removed draft status. All nextest issues should be fixed already