CodeQL causes qmake to segfault when building C++ project #67835
Replies: 2 comments 8 replies
-
|
I've never seen that happen before. Could you re-run the failed job and enable debug logging? That should cause the codeql-action to upload a debug artifact. Hopefully the detailed logs (especially build-tracer.log) help explain what is going wrong. See also: https://github.blog/changelog/2022-05-24-github-actions-re-run-jobs-with-debug-logging/ |
Beta Was this translation helpful? Give feedback.
-
|
After upgrading my code base from Qt 5.15.2 to Qt 6.9.1, my C++ GitHub build is experiencing the behaviour described in this ticket. It's quite strange as qmake6 runs successfully in the job's 'Renderer' step but consistently fails with a segmentation fault in the cpp-language 'Compile' step. I've re-run the job with debug logging but I did not find any meaningful information in the expanded build log. You can analyze the build log here: Cheers, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
I'm attempting to add CodeQL to my C++ Qt project. dail8859/NotepadNext#445
It is set for analyzing "python" and "cpp". The job to analyze python builds the C++ application and works correctly, however when analyzing cpp it attempts to run the exact same
qmakecommand to build the application but fails:The weird thing is there is no differences in the python or cpp jobs (no conditional steps). So my only conclusion is github/codeql-action/init@v2 is doing something odd behind the scenes when the language is set to cpp.
Has anyone else ran across something like this?
Beta Was this translation helpful? Give feedback.
All reactions