Continued problem from https://github.com/actions/cache/issues/1031
See original GitHub issueYes, and we posted at https://github.com/orgs/community/discussions?discussions_q=PySide2 The suggestion given at this issue was not the remedy to fix CI testing.
Description: A clear and concise description of what the bug is.
We are having an issue, possibly with caching on our repo https://github.com/Qiskit/qiskit-metal. Our CI suddenly broke because one of our dependencies, PySide2, is not in our environment. We didn’t make any changes to our pipeline file. It is clear that something is going wrong with the environment that GitHub Actions is creating for us, but we are unaware of where the issue is actually coming from and how to diagnose it, given that GitHub is controlling the environment. Based on this issue, we are writing to you, but in addition, we are going to consult with the GitHub Actions Customer Support.
We deleted all old caches and had GitHub create a new cache entry. Unfortunately, the same issue persists. We also tried creating our environment locally identically to how it is being created by GitHub Actions, and the environment was created without issue and was able to import PySide2.
We implemented the suggestion by response to cache-issue-1031, unfortunately, that did not fix the problem: Hi @obrienpja, I checked your previous successful runs and recent failed runs and found you are running apt install for installing specific dependencies which has probably broken with the latest ubuntu release. This has happened now because the tag ubuntu-latest points to ubuntu-22.04 instead of the previous ubuntu-20.04. Please see here. For now, try running your workflows with the pinned ubuntu version i.e ubuntu-20.04 in runs-on or use a self-hosted image that runs ubuntu 20.04. Closing this issue as it is not related/relevant to actions/cache.
You can view branch at https://github.com/Qiskit/qiskit-metal/pull/887.
We wondering why PySide2 is not being imported anymore into the python environment.
Action version: Specify the action version We had v2, but also tried v3.
Platform:
- [ x] Ubuntu
- [ x] macOS
- Windows
Runner type:
- [ x] Hosted
- Self-hosted
Tools version:
3.9, 3.10Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
https://github.com/Qiskit/qiskit-metal/pull/887
Expected behavior: A description of what you expected to happen. CI continue as it was working previously.
Actual behavior: A description of what is actually happening. CI is failing for every commit.
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (2 by maintainers)
Top GitHub Comments
Thank you @MaksimZhukov!
@MaksimZhukov ,Thank you for you triage, we are 100% blocked until this is resolved. We appreciate your time and support regarding this issue.