This message was deleted.
# androids
Slackbot
03/22/2022, 2:45 PMThis message was deleted.
n
no
03/22/2022, 4:54 PMwehre is that time going? is it downloading the robolectric jars?
j
Justin Breitfeller
03/22/2022, 6:05 PMNo, I think whatever setup robolectric has to do when it first launches is causing that slowdown
Justin Breitfeller
03/22/2022, 6:06 PMAt least, I’m not aware of it downloading any jars
Justin Breitfeller
03/22/2022, 6:08 PMhttps://github.com/robolectric/robolectric/issues/5847 is one of the tickets on their issue tracker about it
Justin Breitfeller
03/22/2022, 6:09 PMhttps://github.com/robolectric/robolectric/issues/5561 that one as well
d
Daniel B Duval
03/22/2022, 6:16 PMFirst, can you try and update to 4.4 at least? It seems that they had an issue where they were reading the binary zips were taking too long - https://github.com/robolectric/robolectric/issues/5118
We recently went from 4.3 -> 4.7.3 and had our worst offender (testing N -> R) have single test class go from 1m 42s -> 42s.
j
Justin Breitfeller
03/22/2022, 6:17 PMWe are using 4.7.3
d
Daniel B Duval
03/22/2022, 6:22 PMah, my bad. Went off of the version in the links and assumed, incorrectly, it was your filing.
j
Justin Breitfeller
03/22/2022, 6:23 PMOh yeah sorry. Those bugs are definitely just things I have found in my research.
Justin Breitfeller
04/04/2022, 3:13 PMNot sure if anyone would know this, but would a build service be able to force all these tests to run in the same classloader so that whatever initialization work is done for robolectric tests can be forced to only happen once?
e
ephemient
04/15/2022, 11:40 PMI think Gradle can't do anything about this.
RobolectricTestRunner does try to re-use sandboxes between test methods, if they have the same configuration, but it's scoped to a single test class only, that's just how JUnit4 runners work. you'd have to write a RobolectricSuite to share between test classes.