pnoltes commented on PR #817: URL: https://github.com/apache/celix/pull/817#issuecomment-3861930657
> > In my view, we should either accept a slower build (limiting parallelism to (.i.e.) -j4) or postpone the analyzer's introduction. I personally prefer the slower build. We can look into ASF-hosted runners later to optimize. > > > > > well i tried to make it slow by enable -j2 and i ran the workflow on my forked repo the debug build reached memory limit and has `exit code of 143` check [forked repo workflow](https://github.com/moelksasbyahmed/celix/actions/runs/21686945878/job/62536446202) so i guess the valid options is making the build so slow by making ninja -j1 or making a specific Ci pipeline with test disabled but i agree with you the build should be compatible with test as well so i guess the only valid option is making the build slow by ninja -j1 and it can be optimized later i will search for valid solutions Maybe I missing something, but the current build uses gcc static analyzer with RelWithDebInfo and `ninja -j8`: https://github.com/apache/celix/actions/runs/21716569744/job/62701713167?pr=817#step:6:23 So looks good to me. I want to wait till have have 2 approvals and then merge the PR. -- 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]
