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

Can't build Halide/LLVM (No space left on device) #10491

Closed
nathaniel-brough opened this issue Jun 8, 2023 · 3 comments
Closed

Can't build Halide/LLVM (No space left on device) #10491

nathaniel-brough opened this issue Jun 8, 2023 · 3 comments

Comments

@nathaniel-brough
Copy link
Contributor

I've been trying to integrate the halide project, and I'm running into issues with github's action runners.

One of Halides dependencies is libllvm which I can't build and install with the base github action runners as I am getting the error no space left on device. I'm able to build this project locally on my machine just fine.

According the github action documentation there is "14 GB of SSD space" which is just shy of what I would need to build llvm on a linux machine. In fact some of the builds are successful (they don't run out of space).

I've run into similar limitations with the base github actions previously in #10174. Would it make sense to either;

  1. Upgrade the github actions runners to the "large runners" with more space/ram OR
  2. Configure the CI to use the same machines the OSS-fuzz actually builds with on a regular basis.
@maflcko
Copy link
Contributor

maflcko commented Jun 12, 2023

Not sure if this is relevant, but it may be possible to remove junk data, see for example #9836 ?

@nathaniel-brough
Copy link
Contributor Author

Ah yeah that pr looks great. It seems to help a little but it's still running out of space.

@jonathanmetzman
Copy link
Contributor

I don't know if we're going to do either of those solutions though they would make sense. It's a lot easier just to use github actions even if they don't work on some anomalous projects. You don't need to pass CI to integrate with oss-fuzz, especially if it's because our CI is broken.

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

3 participants