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

GetClrDbg.sh returned a non-zero code: 1 #531

Closed
NishiokaTakeo opened this issue Jan 15, 2017 · 2 comments
Closed

GetClrDbg.sh returned a non-zero code: 1 #531

NishiokaTakeo opened this issue Jan 15, 2017 · 2 comments

Comments

@NishiokaTakeo
Copy link

NishiokaTakeo commented Jan 15, 2017

I completely followed this tutorial to make the DotNet Core with Docker project.
However When I run the command with './dockerTask.sh build debug' , I have got an error at following point.

Step 5 : RUN curl -SL https://raw.githubusercontent.com/Microsoft/MIEngine/getclrdbg-release/scripts/GetClrDbg.sh --output GetClrDbg.sh && chmod 700 GetClrDbg.sh && ./GetClrDbg.sh $CLRDBG_VERSION && rm GetClrDbg.sh
---> Running in 049cb0e71b0a
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15024 100 15024 0 0 1862 0 0:00:08 0:00:08 --:--:-- 3318
Using arguments
Version : 'VS2015U2'
Location : ''
SkipDownloads : 'false'
LaunchClrDbgAfter : 'false'
RemoveExistingOnUpgrade : 'false'
Info: Using clrdbg version '15.0.26022.0'
Info: Previous installation at not found
Error: Install location is not set
ERROR: Service 'api' failed to build: The command '/bin/sh -c curl -SL https://raw.githubusercontent.com/Microsoft/MIEngine/getclrdbg-release/scripts/GetClrDbg.sh --output GetClrDbg.sh && chmod 700 GetClrDbg.sh && ./GetClrDbg.sh $CLRDBG_VERSION && rm GetClrDbg.sh' returned a non-zero code: 1

I have updated brew and dotnet core SDK.

api_ -bash 141x57_and_new_issue _microsoft_miengine

@rajkumar42
Copy link
Contributor

@CStyle ./GetClrDbg.sh takes two parameters version and location. It looks like the location is missing and hence the failure. @weidazhao can you please take a look?

@ptoonen
Copy link
Contributor

ptoonen commented Jan 21, 2017

Issue seems to be on line 270, fixed in #533

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

No branches or pull requests

3 participants