fix: work around PIP cache concurrency issues
Our issue with PIP appears to stem from its cache locking mechanism,
which doesn't seem capable of handling the number of concurrent
accesses to the cache as the CI generates.
Instead, we will create a cache for each concurrent executor so that
each executor has its own unique cache. It's not ideal, especially with
a lot of executors, but there's little else we can do short of not
cache at all.
Change-Id: Id46becb489328f9d169b69c56bc85d96cfab30e3
Signed-off-by: Chris Kay <chris.kay@arm.com>
1 file changed