-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
jitformat failing on linux x64 #84780
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=237232 Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "syntax error near unexpected token",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
}
|
It seems that we are not able to download the clang tools although the code in the script that verifies the url seems correct. I have sent out dotnet/jitutils#368 to log the download url links. Edit: I verified it locally and it works. |
Looks like making available the clang-format/clang-tidy wasn't good enough. Now on linux-x64 we have:
So maybe the "configureonly" build is failing? @jkoritzinsky ideas? |
Tagging subscribers to this area: @hoyosjs Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=237232 Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "syntax error near unexpected token",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
} Report
Summary
|
Looks like the Docker container is |
This looks like the same issue as #84822: the Docker container used to build changed from centos to mariner |
This is due to #84148 |
Guessing we need to pass the |
Fixes dotnet/runtime#84780. Tested by hooking up the changes locally with runtime's `jitformat.py` and running `python3 ./src/coreclr/scripts/jitformat.py -c /runtime/src/coreclr -o linux -a x64` in our mariner build container. This might break scenarios where jitutils are used outside of ci on a non-mariner build image. Per discussion with @BruceForstall let's make a quick fix to unblock ci, and if this is problematic we could for example add an extra argument that controls whether the `-cross` argument is passed to the runtime build. For context, the `-cross` argument is necessary after dotnet/runtime#84148 because our linux build images have change from centos 7 to CBL-mariner, and the linux builds are now cross-builds that use a rootfs (even x64 and x64-musl).
I verified the fix with test PR #84862 |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=237232
Build error leg or test failing: Build / Formatting linux x64 / Run jitformat.py
Pull request: #84741
Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: