-
Notifications
You must be signed in to change notification settings - Fork 899
Fix random build failure due to System.IO.FileSystem not found #1464
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
Conversation
I see the Travis CI failure from this. Very odd as I wouldn't expect this to cause a build failure, and the failure in particular looks unrelated to the change. But I'll look more into it. |
I found a machine I could repro the problem on. I had forgotten that "no project info for P2P" is code for "the build failed on the referenced project". |
Evidently I inadvertently targeted a newer (1.0.5 instead of 1.0.4) version of the CoreCLR runtime. |
The Mac build failed due to what appears to be an unrelated issue:
Any ideas, @bording? |
This seems non-deterministic as well, since it passed on my own travis CI account. |
I'll kick it. I have yet to comprehend how we're ticking back in time but alas, we sometimes do. |
Thanks, @ethomson |
I've seen that kind of failure before. I wonder if its some sort of rounding/truncation error? For example, one code path rounds up to 22 seconds, and another truncates to 21. |
Ping? |
Applies fix for AArnott/CodeGeneration.Roslyn#25