Skip to content

Fix test build error when BuildAsStandalone is true#93457

Merged
jkotas merged 1 commit into
dotnet:mainfrom
clamp03:fix
Oct 17, 2023
Merged

Fix test build error when BuildAsStandalone is true#93457
jkotas merged 1 commit into
dotnet:mainfrom
clamp03:fix

Conversation

@clamp03

@clamp03 clamp03 commented Oct 13, 2023

Copy link
Copy Markdown
Member

Build error of provider.ilproj test when BuildAsStandalone is true
EXEC : error : No entry point declared for executable

This is due to #92029
Restore OutputType to Library.

Build error of provider.ilproj test when BuildAsStandalone is true
`EXEC : error : No entry point declared for executable`

This is due to dotnet#92029
Restore OutputType to Library.
@ghost ghost added community-contribution Indicates that the PR has been added by a community member area-Infrastructure-coreclr Only use for closed issues labels Oct 13, 2023
@ghost

ghost commented Oct 13, 2023

Copy link
Copy Markdown

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

Issue Details

Build error of provider.ilproj test when BuildAsStandalone is true
EXEC : error : No entry point declared for executable

This is due to #92029
Restore OutputType to Library.

Author: clamp03
Assignees: -
Labels:

area-Infrastructure-coreclr, community-contribution

Milestone: -

@trylek trylek left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this, I'm however somewhat surprised why we need to explicitly specify the Library OutputType, I was under the impression that it's the default, why isn't the default logic kicking in here?

@clamp03

clamp03 commented Oct 16, 2023

Copy link
Copy Markdown
Member Author

Actually, I don't know well about tests in dotnet/runtime. I am just guessing that OutputType set to Exe when BuildAsStandalone is set like

<OutputType Condition="$(BuildAsStandalone)">Exe</OutputType>

@clamp03

clamp03 commented Oct 17, 2023

Copy link
Copy Markdown
Member Author

@trylek @jkotas I think the failures are not caused by the PR. Could you merge if it doesn't have any issue?

@jkotas jkotas merged commit b38e86d into dotnet:main Oct 17, 2023
@clamp03

clamp03 commented Oct 17, 2023

Copy link
Copy Markdown
Member Author

CC @gbalykov Our internal CI fails for days because of this issue. Thank you.

@gbalykov gbalykov left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gbalykov

Copy link
Copy Markdown
Member

@clamp03 thank you!

@clamp03 clamp03 deleted the fix branch October 24, 2023 03:47
@ghost ghost locked as resolved and limited conversation to collaborators Nov 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Infrastructure-coreclr Only use for closed issues community-contribution Indicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants