https://github.com/osquery/osquery logo
#core
Title
# core
s

seph

02/24/2023, 9:18 PM
Now I’m playing whackamole with the github actions
s

Stefano Bonicatti

02/24/2023, 9:22 PM
We hit the space limit again I see, but now it's at the build phase, which is quite problematic
s

seph

02/24/2023, 9:22 PM
Is that what happened? I didn’t see a clear error on the arm builds
I’m currently chasing down the macOS signing issue
on the bottom of the build section
Copy code
[100%] Linking CXX executable tests_integration_tables-test
ld.lld: error: failed to open tests_integration_tables-test: No space left on device
s

seph

02/24/2023, 9:23 PM
Ah, yes.
That’s on the arm machines… Which we host in AWS
s

Stefano Bonicatti

02/24/2023, 9:24 PM
That's annoying, when I tested last time it seemed that there were at least 2GB free post build (which though weren't enough for subsequent steps)
Which is why I then added those steps to delete some of the unused build artifacts
s

seph

02/24/2023, 9:42 PM
I’m not sure how to fix that issue, but I’m starting to see the problem with the macOS code signing
Okay, I fixed the apple issue. I don’t know what to do about the space issue.
@Stefano Bonicatti I’m not sure if you’re looking at this, but if not can you outline what actions we can take?
s

Stefano Bonicatti

02/27/2023, 12:17 PM
I don't know if there's a way to reduce space usage just before the build, but the core problem here is how we register tables and plugins, which affects how we have to build osquery and relative tests, which in turn causes bringing in the code for all the tables and dependencies for each test binary, even if totally unused: https://github.com/osquery/osquery/issues/6397#issuecomment-1431724082
This is not a quick fix, but it's a much needed one because it negatively affects linking time, space usage, ability to bring in additional feature and in general, development.