But instead of directly disabling caching, we should look into how we can enable smart caches where if the changes are detected in the code/tests only then the caching is disabled.
I tried checking if there's an easy way to enable smart caches, but couldn't find any easily configurable.
The easiest way I found to fix this is to cleanup docker builder, so that the same builder won't be used again.
Reproducing the issue
In the last few CI builds I found that the same builder was not being used in the consecutive builds. But there's a possibility of that happening if the same actions node is reused again.
I could reproduce the issue locally if the same builder is being used.
Motivation
Closes #102
Suggested changes
Regarding this comment -
I tried checking if there's an easy way to enable smart caches, but couldn't find any easily configurable.
The easiest way I found to fix this is to cleanup docker builder, so that the same builder won't be used again.
Reproducing the issue
In the last few CI builds I found that the same builder was not being used in the consecutive builds. But there's a possibility of that happening if the same actions node is reused again.
I could reproduce the issue locally if the same builder is being used.