-
Notifications
You must be signed in to change notification settings - Fork 148
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
Build fails on SDK 2.1.300-rc1-008669 at BuildServer step #328
Comments
/cc @cartermp |
@YunWeiaa did you try with a RTM version? |
This is for .NET Core 2.1 preview validation. Myself and @KevinRansom can take a look, since the bits in the report are on an internal file share. |
That would be great. |
@forki @YunWeiaa the issue seems to be that the bookstore is downloading a 64-bit version of the CLI, but the VM that this was tested on is an x86 Windows 7 machine. So there isn't any action we'll take on our end. The FAKE module could be updated to handle this, or the requirements for the bookstore could be changed to x64. |
Thanks for investigating this. I'll try to patch it in fake 4 tomorrow. /cc
8
Phillip Carter <[email protected]> schrieb am Mo., 30. Apr. 2018,
23:10:
… @forki <https://github.com/forki> @YunWeiaa <https://github.com/YunWeiaa>
the issue seems to be that the bookstore is downloading a 64-bit version of
the CLI, but the VM that this was tested on is an x86 Windows 7 machine. So
there isn't any action we'll take on our end. The FAKE module could be
updated to handle this, or the requirements for the bookstore could be
changed to x64.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#328 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNEclOIlpO0rbb5KU5_CAn6LZkRmbks5tt322gaJpZM4Tpur4>
.
|
Ok, I got it. Thanks. |
ok. latest should install the x86 dotnet core if you are on x86. |
Verified this issue on VS build: d15.7/27702.01 (15.7 Preview 7) + CLI/SDK 2.1.300-rtm-008701 (x86) on Win 7 x86 ENU, but it also failed. |
@cartermp ideas? |
Yoof, none come to mind. Sounds like some generic failure. The previous error message was typical of x86/x64 errors but this one doesn’t give a hint unfortunately. Do we know if webpack works on x86 windows? |
That is a good question. Tbh I didn't even know that you could still use
x86. If we don't find something then I'm personally fine with requiring
x64.
Phillip Carter <[email protected]> schrieb am Sa., 5. Mai 2018,
17:26:
… Yoof, none come to mind. Sounds like some generic failure. The previous
error message was typical of x86/x64 errors but this one doesn’t give a
hint unfortunately. Do we know if webpack works on x86 windows?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#328 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNBm1jIf_7WPfcWe_DQnYhMegfIoFks5tvcSxgaJpZM4Tpur4>
.
|
Environmental info
Windows Win 7 x86 ENU
VS:D15.7/27625.00 (15.7 Preview 5)
Node.js: V8.11.1 LTS
Yarn --version:1.6.0
CLI/SDK: 2.1.300-rc1-008669 (runtime - 2.1.0-rc1-26425-07)
Repro steps
Master branch of SAFE Bookstore

Install the needed deps for SAFE-Bookstore and run build.cmd. Error produced:
The text was updated successfully, but these errors were encountered: