-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Problems encountered by codeql in building chromium QL library 2 #13489
Comments
"Just to clarify, the compilation was successful, it's just that many cc files will not appear in the CodeQL database."
|
The error about You said there were many CC files missing. Could you search for a couple of them in the build-tracer.log to see if they are mentioned at all. If they are not mentioned then they are likely not needed by the build process (they may have already been compiled earlier or are part of a different build target). If the files are mentioned in Attaching the entire build-tracer log to this issue is probably not possible, but if you can attach a snippet with of the log related to the trace of a single CC file that would be great for debugging. |
Deleted Obj file list
|
Thanks for providing a build-tracer log. I see a couple of things like :
I think these could explain why some files are missing. I'll pass it on to the team, hopefully they know what is causing the problem. |
There may be a fix for your problem in the pre-release version of CodeQL 2.13.4. Could you try if that helps? See: https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.13.4 |
build-tracer.log Deleted Obj file list
|
Thanks for the updated log. The log seems to indicate that only one file was compiled, not the 8 from #13489 (comment). Is that correct? |
yes, i only delete one obj file (obj\chrome\browser\ui\ui\manage_passwords_ui_controller.obj) |
Can you delete all the relevant object files and re-try and share the log. Currently I cannot judge how severe the problem is. |
|
Thanks for the complete log. I cannot easily reproduce this. I'll add this problem to our internal tracking issue for these kinds of problems, but I cannot promise this will be solved any time soon. |
Reproduce step: build args.gn Set build arguments here. See
|
Thanks. I'm fully aware how to build Chromium. This doesn't mean it's easy to create a test case that reproduces the problem. |
According to the method mentioned here,
i removed \out\debug\obj\components\autofill
The text was updated successfully, but these errors were encountered: