-
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
Failure to create CodeQL database with latest Visual Studio (17.8.1) #14927
Comments
Hi @matlimatli, Thanks for raising this issue. It seems that we no longer capture the output of |
We believe we have fixed this. The fix should be part of CodeQL 2.15.4, which should be released a few days from now. |
@jketema Sounds great! However, since HLK testing requires CodeQL 2.6.3, this might still be a problem in some cases. I'm not sure where that issue should be raised. |
HLK testing issues should be raised with Microsoft. From our perspective 2.6.3 is no longer supported. |
Closing as this was fixed. I believe Microsoft also has put into place some mitigating measures for HLK. |
Description of the issue
After upgrading the Visual Studio environment from 17.4 to 17.8.1, we can not create a CodeQL database.
It looks like the compiler detection is failing. Se extract of build below.
Full logging available as attachment:
codeql.zip
Reproduction steps
For reproduction, a standard Visual Studio HelloWorld template project was used. Latest stable vs_buildtools (17.8.1) and latest CodeQL release (2.15.3) was installed in a docker container (based on mcr.microsoft.com/windows/servercore:ltsc2022)
An attempt to create a new database was done with the command:
C:\devtools\CodeQL\codeql.2.15.3\codeql.exe database create -v -v -v .\HelloWorld\codeql --language=cpp --overwrite --command="msbuild /t:rebuild /p:Configuration=Release /p:Platform=x64 ${PWD}\HelloWorld.sln"
This resulted in the output in the attached logs.
For reference, the output of
cl.exe --version
isThe exact same steps with Visual Studio/vs_buildtools 17.4 works flawlessly.
The text was updated successfully, but these errors were encountered: