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

Enable max path detection #3631

Merged
merged 3 commits into from
Dec 2, 2018

Conversation

ccastanedaucf
Copy link
Contributor

Also might be useful to have the ability to revert to old behavior if necessary. Should this be controlled via environment variable?

Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

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

Yes, I think we should have an escape hatch for this. Can you add one in src/shared/Traits.cs, modeled after for example

https://github.com/Microsoft/msbuild/blob/7b3a457540ab87cf02f6d41ce6095e6ecbbb6ea7/src/Shared/Traits.cs#L152-L155

?

@ccastanedaucf
Copy link
Contributor Author

Well that's a new one. Test ForceSomeOutOfDate kept failing on .NET Core both locally and on CI for a few hours while I couldn't figure out what could have possibly changed in behavior. Then it started passing locally and on CI again.

@rainersigwald
Copy link
Member

I looked at the test and the failing assertion and I don't think I can explain that 😕

@ccastanedaucf ccastanedaucf force-pushed the enable-maxpath-detection branch from 74ed9af to 5bab36f Compare November 26, 2018 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants