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

Disable static restore in more locations #66567

Merged
merged 4 commits into from
Jan 30, 2023

Conversation

dibarbet
Copy link
Member

took a quick stab at fixing this

@@ -206,6 +206,7 @@ stages:
include:
- src/Compilers/*
- src/Dependencies/*
- eng/*
Copy link
Member Author

Choose a reason for hiding this comment

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

seems like we should run compiler CI when build scripts change

Copy link
Member

Choose a reason for hiding this comment

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

Since you are touching this, could you also fix #65602 in this PR?

Copy link
Member Author

Choose a reason for hiding this comment

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

Added the compiler generator tools path - let me know if there were other directories you were thinking of

@RikkiGibson
Copy link
Contributor

Is there a writeup for why disabling static restore fixes correctness jobs?

@dibarbet
Copy link
Member Author

Is there a writeup for why disabling static restore fixes correctness jobs?

It isn't just correctness - it technically affects all the builds with static restore (see the nuget restore issue). However the reason it hit correctness builds first (well technically it hit the scouting queue integration tests first) is that they are specifically requiring an image with VS preview on it (17.5) which has a version of nuget with the issue.

@dibarbet
Copy link
Member Author

@RikkiGibson or @jaredpar - any idea on what might be happening with the rebuild check? It passed on the previous commit (and I only changed the folders qualifying as a compiler change in the yaml which I don't believe should impact correctness).

I already re-ran once and hit the same error

@RikkiGibson
Copy link
Contributor

It looks like the bootstrap build is failing in that job. Why only in Rebuild? I don't think any rebuild-specific stuff is happening at that point.

@jaredpar
Copy link
Member

Merging to help unblock PRs.

@jaredpar jaredpar merged commit 3a3f4fe into main Jan 30, 2023
@ghost ghost added this to the Next milestone Jan 30, 2023
@Cosifne Cosifne modified the milestones: Next, 17.6 P1 Jan 31, 2023
ryzngard pushed a commit to ryzngard/roslyn that referenced this pull request Mar 16, 2023
* Disable static restore in more locations

* Run compilers CI when build scripts change

* Include compiler generators in compilers code change check

* Remove separate restore in bootstrap build
allisonchou pushed a commit to allisonchou/roslyn that referenced this pull request Mar 20, 2023
* Disable static restore in more locations

* Run compilers CI when build scripts change

* Include compiler generators in compilers code change check

* Remove separate restore in bootstrap build
dibarbet added a commit that referenced this pull request Apr 19, 2023
* Disable static restore in more locations

* Run compilers CI when build scripts change

* Include compiler generators in compilers code change check

* Remove separate restore in bootstrap build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants