Run muzzle during PR

[iNikem]

Every module as a separate job

[anuraaga]

I don't think our config for muzzle has enabled caching but I see FROM-CACHE in the logs. Do you know how this is happening? Forgot about s3 cache.

[anuraaga]

Do you mind doing a run with cache disabled to measure the time? Some changes, like updating Gradle, will invalidate all cache. That doesn't mean we have to stick with CircleCi but knowing how the worst case does will be helpful. For example, if worst case of CircleCi is 30min and GHA is 4 hours, I don't know what to do. But if the numbers are 30min and 45min for worst case, I won't think any more on the topic :)

[iNikem]

Buildscan claims that we saved 15s due to remote cache. It just needs to compile couple of modules. Probably tests will still be the longest checks

[iNikem]

@anuraaga Tried. Tests are still the longest part.

[anuraaga]

@iNikem Something magical is going on or I'm not being able to read the logs correctly - isn't ab6b2ca also printing a lot of FROM-CACHE?

[iNikem]

Don't see

[anuraaga]

Perhaps it depends on the version. I think your icon on this screenshot makes it clear right? :-)

[anuraaga]

Ah - nevermind, why am I not looking at muzzle. Got it

[anuraaga]

Here's a muzzle with without cache (fairly confident this time but still definitely may be doing something silly :P.

[anuraaga]

Why is muzzle so fast even though it seems like it should be really expensive?

[iNikem]

I don't know how

Why is muzzle so fast even though it seems like it should be really expensive?

Because it is per module. 2-3 minutes per module is expensive. It's just cheaper that something cheaper (tests) for all modules at once.

[trask]

Nice 😄