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

Alpine Legs failing to build CoreCLR #4298

Closed
ellahathaway opened this issue Apr 5, 2024 · 5 comments · Fixed by dotnet/runtime#100796
Closed

Alpine Legs failing to build CoreCLR #4298

ellahathaway opened this issue Apr 5, 2024 · 5 comments · Fixed by dotnet/runtime#100796
Assignees
Labels
ops-monitor Issues created/handled by the source build monitor role untriaged

Comments

@ellahathaway
Copy link
Member

ellahathaway commented Apr 5, 2024

The Alpine legs are failing due to issues building runtime's CoreCLR component. There are many errors for this component, but most of them are related to null values and null pointers. Below are two examples of errors that appeared in the build:

  • error: value of type 'std::nullptr_t' is not implicitly convertible to 'UINT_PTR' (aka 'unsigned long')
  • error: cannot initialize a member subobject of type 'COUNT_T' (aka 'unsigned int') with an rvalue of type 'std::nullptr_t'

I believe that dotnet/runtime#98336 may have introduced these errors.

Link to failing build (internal Microsoft link)

@ellahathaway ellahathaway added the ops-monitor Issues created/handled by the source build monitor role label Apr 5, 2024
@ellahathaway
Copy link
Member Author

cc @khushal1996 - pinging since I believe you originally opened the PR linked into the issue. Let me know if I should ping someone else.

@BruceForstall
Copy link
Member

@ellahathaway How did you determine that dotnet/runtime#97529 might be at fault?

This seems very likely related to dotnet/runtime#98336 -- @jkoritzinsky

@ellahathaway
Copy link
Member Author

Ah you're right. The commit hash pulled from the VMR build doesn't even include dotnet/runtime#97529 in the log history yet (hadn't been synced to the VMR as of that build).

I had looked through the git history of the files and saw that dotnet/runtime#98336 was merged two days ago, so I assumed that this would've gone into the VMR yesterday given that runtime syncs to sdk every day which syncs to installer every day. I've updated the issue comment to reflect the correct PR.

@jkoritzinsky
Copy link
Member

Ill take a look. I'm amazed this is only causing failures in the VMR. Don't know why that would be.

@jkoritzinsky jkoritzinsky self-assigned this Apr 6, 2024
@jkoritzinsky
Copy link
Member

Looks like it's failing due to Clang 17 introducing more strict checking for nullptr->integer conversions in compile-time-constant scenarios. I was hoping to avoid having to handle this now (and instead rewriting the infrastructure that hits this) but it should be fixable without too much trouble.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ops-monitor Issues created/handled by the source build monitor role untriaged
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants