pnoltes commented on PR #817: URL: https://github.com/apache/celix/pull/817#issuecomment-3851432196
> hi @pnoltes i tried ninja -j2 and `RelWithDepInfo` and it worked but `debug` didnt should i make ninja -j1 but it will make the build so slow or should i just remove analyzer from the CI work flow I see that the debug one ran over the configured 120minute limit. I think we can test a bit more and then discuss whether we want gcc analyse in our builds and if so how. Could you provide an update with -j4 to check if that helps (a bit faster, but hopefully not parallel enough to eat too much memory)? I had a quick look and there are also ASF infra hosted runners (https://cwiki.apache.org/confluence/display/INFRA/ASF+Infra+provided+self-hosted+runners), so this could be another route. Not yet sure if this is (memory wise) a step up from the GitHub hosted runners. Maybe already good to minimise the usage of the gcc static analyzer to a single build? I think, not sure, that there is no benefit to run the gcc static analyzer in the debug build (compared to the RelWithDebInfo build) and seeing the latest build I expect the analyzer performs better with a RelWithDebInfo build. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
