Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spread pkg missing on some instances #210

Open
upils opened this issue Jan 26, 2024 · 2 comments
Open

spread pkg missing on some instances #210

upils opened this issue Jan 26, 2024 · 2 comments

Comments

@upils
Copy link

upils commented Jan 26, 2024

Bug Description

While running tests in self-hosted runner I noticed the package spread was missing on some instances.

My job failed on:

And it succeeded (I least spread was found) on ubuntu-image-agent-64-01 after a third retry on the same code.

AFAIK I never had to explicitly install spread on the runner so I thought it was installed by default.

I only notice the issue on these 2 particular instances by chance, but I guess other instances maybe affected.

To Reproduce

If possible, create a github workflow with a constraint to run specifically on one of these two instances and trying to run spread.

Environment

N/A

Relevant log output

N/A

Additional context

No response

@yhaliaw
Copy link
Collaborator

yhaliaw commented Jan 29, 2024

The packages installed on the self-hosted runner provided by this charm is not the same as the GitHub-provided runners.

The image size of the GitHub-provided runners are quite large. Without any additional installation, the GitHub-provided runners are using 50+GiB of disk:
https://github.com/canonical/github-runner-operator/actions/runs/7691255463/job/20956277160#step:3:6

One of the planned feature is custom images where each job can specify a custom image to run on.
Currently, would installing spread package as part of the workflow be fine?
If not we can look at making it part of the image used by the charm.

@upils
Copy link
Author

upils commented Jan 29, 2024

Yes, installing spread in the workflow is fine. We also even have runners dedicated to the project so this is not a big problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants