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

KVM-CI: Cleanup before cloning rusty-hermit #125

Merged
merged 1 commit into from
Jun 15, 2021
Merged

Conversation

mkroening
Copy link
Member

I suspect, the reason for recent CI failures is that a KVM-CI-run did not complete and clean up after itself. So why not clean up, before cloning?

@mkroening mkroening self-assigned this Jun 15, 2021
@codecov
Copy link

codecov bot commented Jun 15, 2021

Codecov Report

Merging #125 (9b75b95) into master (1656e55) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #125   +/-   ##
=======================================
  Coverage   19.82%   19.82%           
=======================================
  Files          21       21           
  Lines        5190     5190           
=======================================
  Hits         1029     1029           
  Misses       4161     4161           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1656e55...9b75b95. Read the comment docs.

@jounathaen
Copy link
Member

This, and the fact that the runner only has 10GB of disk space, which I'm fixing right now ;-)

@bors bors bot merged commit 4e206d3 into hermit-os:master Jun 15, 2021
@mkroening mkroening deleted the kvm-ci branch July 14, 2021 10:22
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

Successfully merging this pull request may close these issues.

None yet

2 participants