-
Notifications
You must be signed in to change notification settings - Fork 258
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
Tests fail with PathTooLongException on fresh clone #1768
Comments
@kevinkuszyk thanks for reporting this. We clone to a local folder that is typically something like |
Closing as we didn't hear back |
Apologies for taking a while to reply - I'm catching up after Christmas. I still get this error (and a few more) on the latest this afternoon: As you can see, I'm in I can send the full output from the build script if that would help? Also, can you re-open this issue? |
I would assume that either your temp folder (which is typically not under c:\temp but under the user profile) or your user profile is stored at some relatively long path. It is hard to tell, but the easiest way to deal with this is to run the tests from visual studio and figure out the broken test, and let us know. You can either submit a fix or figure out what went wrong. |
The temp folder was the culprit - I'd forgotten it defaults to I also get a load of other tests failing (there was a pull request from |
A readme update should be fine. Changing to c:\temp is not always going to work and is not always necessary |
As for public CI, we will get to our at some point, probably not in this version. |
@kevinkuszyk do you still plan on a PR here, I'm closing (since it seems low pri) but feel free to send one out. |
@yishaigalatzer thanks for the nudge - this had slipped my mind. I don't think there is any need for a PR now, as the latest clone from |
I wanted to try fixing #1743, but when I run the
build.ps1
script from 26a401e I get the following error:The text was updated successfully, but these errors were encountered: