Skip to content
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

Closed
AndyAyersMS opened this issue Apr 13, 2023 · 10 comments · Fixed by #84799 or dotnet/jitutils#369
Closed

jitformat failing on linux x64 #84780

AndyAyersMS opened this issue Apr 13, 2023 · 10 comments · Fixed by #84799 or dotnet/jitutils#369
Assignees
Labels
area-Infrastructure-coreclr blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Milestone

Comments

@AndyAyersMS
Copy link
Member

AndyAyersMS commented Apr 13, 2023

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.

{
  "ErrorMessage": "syntax error near unexpected token",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Report

Build Definition Step Name Console log Pull Request
238577 dotnet/runtime Run jitformat.py Log #84605
238556 dotnet/runtime Run jitformat.py Log
238510 dotnet/runtime Run jitformat.py Log #84716
238380 dotnet/runtime Run jitformat.py Log
237357 dotnet/runtime Run jitformat.py Log #84605
238326 dotnet/runtime Run jitformat.py Log #84734
238210 dotnet/runtime Run jitformat.py Log #84772
238204 dotnet/runtime Run jitformat.py Log #84772
237232 dotnet/runtime Run jitformat.py Log #84741
238043 dotnet/runtime Run jitformat.py Log #84661
237909 dotnet/runtime Run jitformat.py Log #84765
237995 dotnet/runtime Run jitformat.py Log #84772
237866 dotnet/runtime Run jitformat.py Log #84661
237804 dotnet/runtime Run jitformat.py Log #84748
237792 dotnet/runtime Run jitformat.py Log
237775 dotnet/runtime Run jitformat.py Log #84275
237744 dotnet/runtime Run jitformat.py Log
237666 dotnet/runtime Run jitformat.py Log #84731
237598 dotnet/runtime Run jitformat.py Log #84275
237469 dotnet/runtime Run jitformat.py Log #84748
237373 dotnet/runtime Run jitformat.py Log #84661
237337 dotnet/runtime Run jitformat.py Log #84716
237422 dotnet/runtime Run jitformat.py Log
237416 dotnet/runtime Run jitformat.py Log #83151
237107 dotnet/runtime Run jitformat.py Log #84275
237112 dotnet/runtime Run jitformat.py Log #84275
237002 dotnet/runtime Run jitformat.py Log #84731

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
2 27 27
@AndyAyersMS AndyAyersMS added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab labels Apr 13, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Apr 13, 2023
@ghost
Copy link

ghost commented Apr 13, 2023

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

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.

{
  "ErrorMessage": "syntax error near unexpected token",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}
Author: AndyAyersMS
Assignees: -
Labels:

area-Infrastructure-libraries, blocking-clean-ci, Known Build Error

Milestone: -

@kunalspathak
Copy link
Member

kunalspathak commented Apr 13, 2023

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.

@BruceForstall BruceForstall modified the milestones: Future, 8.0.0 Apr 13, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Apr 13, 2023
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels Apr 13, 2023
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Apr 13, 2023
@BruceForstall
Copy link
Member

Looks like making available the clang-format/clang-tidy wasn't good enough. Now on linux-x64 we have:

Can't find compile_commands.json file. Running configure.
Running: /__w/1/s/src/coreclr/build-runtime.sh x64 Checked configureonly -cmakeargs -DCMAKE_EXPORT_COMPILE_COMMANDS=1
Unhandled exception. System.IO.FileNotFoundException: Could not find file '/__w/1/s/artifacts/obj/coreclr/linux.x64.Checked/compile_commands.json'.
File name: '/__w/1/s/artifacts/obj/coreclr/linux.x64.Checked/compile_commands.json'
   at System.IO.File.Move(String sourceFileName, String destFileName, Boolean overwrite)
   at ManagedCodeGen.jitformat.Main(String[] args) in /tmp/tmpe86afm5e/jitutils/src/jit-format/jit-format.cs:line 502

So maybe the "configureonly" build is failing?

@jkoritzinsky ideas?

@BruceForstall BruceForstall reopened this Apr 13, 2023
@ghost
Copy link

ghost commented Apr 13, 2023

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

Issue Details

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.

{
  "ErrorMessage": "syntax error near unexpected token",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Report

Build Definition Step Name Console log Pull Request
237357 dotnet/runtime Run jitformat.py Log #84605
237232 dotnet/runtime Run jitformat.py Log #84741
238043 dotnet/runtime Run jitformat.py Log #84661
237909 dotnet/runtime Run jitformat.py Log #84765
237995 dotnet/runtime Run jitformat.py Log #84772
237866 dotnet/runtime Run jitformat.py Log #84661
237804 dotnet/runtime Run jitformat.py Log #84748
237775 dotnet/runtime Run jitformat.py Log #84275
237744 dotnet/runtime Run jitformat.py Log
237666 dotnet/runtime Run jitformat.py Log #84731
237469 dotnet/runtime Run jitformat.py Log #84748
237373 dotnet/runtime Run jitformat.py Log #84661
237337 dotnet/runtime Run jitformat.py Log #84716
237416 dotnet/runtime Run jitformat.py Log #83151
237107 dotnet/runtime Run jitformat.py Log #84275
237112 dotnet/runtime Run jitformat.py Log #84275
237002 dotnet/runtime Run jitformat.py Log #84731

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
17 17 17
Author: AndyAyersMS
Assignees: BruceForstall
Labels:

area-Infrastructure-coreclr, blocking-clean-ci, Known Build Error

Milestone: 8.0.0

@BruceForstall
Copy link
Member

Looks like the Docker container is build.ubuntu.1804.amd64.open

@BruceForstall
Copy link
Member

This looks like the same issue as #84822: the Docker container used to build changed from centos to mariner

@sbomer @jkoritzinsky @steveisok PTAL

@BruceForstall
Copy link
Member

This is due to #84148

@sbomer
Copy link
Member

sbomer commented Apr 14, 2023

Guessing we need to pass the -cross argument to the build-runtime.sh script. I'll try to repro this.

BruceForstall pushed a commit to dotnet/jitutils that referenced this issue Apr 14, 2023
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).
@BruceForstall
Copy link
Member

I verified the fix with test PR #84862

@ghost ghost locked as resolved and limited conversation to collaborators May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-coreclr blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
5 participants