-
Notifications
You must be signed in to change notification settings - Fork 599
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
vagrant: run tests with Fedora 38 #2181
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## criu-dev #2181 +/- ##
============================================
+ Coverage 70.59% 70.65% +0.05%
============================================
Files 133 133
Lines 33324 33326 +2
============================================
+ Hits 23525 23545 +20
+ Misses 9799 9781 -18 ☔ View full report in Codecov by Sentry. |
The vagrant test fails. Pls investigate what is going on there. |
It says no space left on device. @rst0git maybe you need to increase the vagrant disk size |
I tried increasing the disk size, but it fails with the same error. Here is the output of
|
That is strange. Can you re-create this error locally using Vagrant? |
Yes, the same error appears when running |
f392ea1
to
4d137b8
Compare
aaea19f
to
73ea158
Compare
This patch also updated the download URL format from https://releases.hashicorp.com/vagrant/2.3.7/vagrant_2.3.7_x86_64.deb to https://releases.hashicorp.com/vagrant/2.3.7/vagrant_2.3.7-1_amd64.deb Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
73ea158
to
e470c6d
Compare
@adrianreber sorry, I clicked rebase-and-merge and only then noticed that @rst0git requested your review. Pls take a look and if here is something wrong, we will fix on top. |
This pull request updates the version of vagrant from 2.2.19 to 2.3.7, and the base Fedora VM image from 37 to 38.