Skip to content

Conversation

@kunalspathak
Copy link
Contributor

In #42053 , the superpmi pipeline files were added in wrong folder and got deleted after auto-update from dotnet/arcade. Add back those files in right folder.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Oct 12, 2020
@kunalspathak
Copy link
Contributor Author

@safern

@kunalspathak
Copy link
Contributor Author

I have triggered a run with these changes: https://dev.azure.com/dnceng/internal/_build/results?buildId=849372&view=results

Copy link
Contributor

@BruceForstall BruceForstall left a comment

Choose a reason for hiding this comment

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

src/coreclr/scripts seems like the wrong location for superpmi.proj. Wouldn't it be better in eng/pipelines/coreclr? It would be "next to" the users in that case.

@kunalspathak
Copy link
Contributor Author

src/coreclr/scripts seems like the wrong location for superpmi.proj. Wouldn't it be better in eng/pipelines/coreclr? It would be "next to" the users in that case.

True, but I didn't see any .proj files under eng/pipelines folder, so created it under src\coreclr\scripts. I am not sure if that is intentional or it is just that we have .proj files under src\coreclr. Let me know what you think and I will change it accordingly.

@safern
Copy link
Member

safern commented Oct 12, 2020

The pipelines folder usually just contains .yml files. So I think src/coreclr/* makes more sense...

I am not sure how this worked in the past with missing imports.
@kunalspathak kunalspathak merged commit 1c4f311 into dotnet:master Oct 13, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants