Description:
Pretty recently I've started using setup-python cache feature for my tests. I have a shared workflow with actions
https://github.com/fizyk/actions-reuse/blob/main/.github/actions/pipenv/action.yml
That I reuse in my other projects. Like here:
https://github.com/ClearcodeHQ/pytest-mysql/pull/456/files
However, in this particular PR linked, I have two consecutive sets of builds running one after another on macos. And the second fails if the cache exists, if it doesn't (i.e., it gets removed manually) the 2nd build works fine.
See https://github.com/ClearcodeHQ/pytest-mysql/actions/runs/6233151257
Action version:
v4
Platform:
Runner type:
Tools version:
Python 3.9. 3.10, 3.11
Repro steps:
Create two builds python builds (one after another) on macos using same python version.
Expected behavior:
Build succeded
Actual behavior:
Build using existing cache fails.
Description:
Pretty recently I've started using setup-python cache feature for my tests. I have a shared workflow with actions
https://github.com/fizyk/actions-reuse/blob/main/.github/actions/pipenv/action.yml
That I reuse in my other projects. Like here:
https://github.com/ClearcodeHQ/pytest-mysql/pull/456/files
However, in this particular PR linked, I have two consecutive sets of builds running one after another on macos. And the second fails if the cache exists, if it doesn't (i.e., it gets removed manually) the 2nd build works fine.
See https://github.com/ClearcodeHQ/pytest-mysql/actions/runs/6233151257
Action version:
v4
Platform:
Runner type:
Tools version:
Python 3.9. 3.10, 3.11
Repro steps:
Create two builds python builds (one after another) on macos using same python version.
Expected behavior:
Build succeded
Actual behavior:
Build using existing cache fails.