Tomasz Janiszewski

> On ARM, 386, and 32-bit MIPS, **it is the caller's responsibility to arrange for 64-bit alignment of 64-bit words accessed atomically via the primitive atomic functions** (types [Int64](https://pkg.go.dev/sync/atomic#Int64) and...

I see 3 options: - move stats to the top of struct https://github.com/allegro/bigcache/blob/caa34156bfeab3aa547e18c21292736bbd2ae2c2/shard.go#L32 - use `atomic.Int64` - instead of atomic use lock (that's already there) https://github.com/allegro/bigcache/blob/main/shard.go#L403-L406 @912929782 How to reproduce...

Any updates. If I get a hint where it should be implemented I'll do it :)

Thanks. That helps a lot. At least I know how to create proof of concept. After adding new field to https://github.com/spockframework/spock/blob/e97e2edf99c8ab00e32dba46e8dd2e814ab8f287/spock-core/src/main/java/org/spockframework/runtime/model/SpecInfo.java#L35 I should sort it by this new field: https://github.com/spockframework/spock/blob/e97e2edf99c8ab00e32dba46e8dd2e814ab8f287/spock-core/src/main/java/org/spockframework/runtime/SpockEngineDiscoveryPostProcessor.java#L12-L18...

@kriegaex That's great! I think we would need 3 different options. For example let's have specs `A`, `B`, `C` and tests `1`, `2`, `3` in each: 1. Randomise specs order...

Do we need this func? We have `Get`

Indeed it's not exposed in config nor available in the action.

Closing as #460 was merged

Sure, I'm waiting for one more PR and will cut release tomorrow. Thanks for pointing this out.

I think I found a broken generation in different part as well. In my case migration is not working due to broken sql that uses `$2` but not `$1` resulting...