-
Notifications
You must be signed in to change notification settings - Fork 26
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
Use vmtest-action version 0.8 in CI #795
base: main
Are you sure you want to change the base?
Conversation
It's not at all clear why, but various tests fail when run in a vmtest VM that has the hosts /tmp/ mounted inside. The issue seems fixed once we switch to using named temporary files ¯\_(°ペ)_/¯ Switch over to using them, which makes a lot more sense in many cases anyway, because some tests are currently making up a path that does not represent reality. Signed-off-by: Daniel Müller <[email protected]>
c33d706
to
a8e0302
Compare
With vmtest-action version 0.8 released, it makes the most sense for us to consume this version as opposed to the current snapshot from the master branch. This way, we anticipate to consume stable releases and have Dependabot manage version bumps for us. Signed-off-by: Daniel Müller <[email protected]>
a8e0302
to
4d2fa41
Compare
91a0c35
to
4d2fa41
Compare
So the issue here is with 9P. See discussion here: danobi/vmtest#83 Hence, this PR is blocked until this issue is resolved, I suppose. |
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label or comment or it will be closed in 5 days. |
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label or comment or it will be closed in 5 days. |
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label or comment or it will be closed in 5 days. |
Closing pull request as it is stale. |
With vmtest-action version 0.8 released, it makes the most sense for us to consume this version as opposed to the current snapshot from the master branch. This way, we anticipate to consume stable releases and have Dependabot manage version bumps for us.