Search Issue Tracker

By Design

Votes

0

Found in [Package]

2.4.2

Issue ID

HUBX-520

Regression

No

[Hub] Errorlevel value is set to 1 when executing Hub CLI commands

Package: HUBX

-

How to reproduce:
1. Download and extract the "HubErrorLevel.zip" attachment
2. Open the Test.bat file with a text editing program
3. Change the HUBPATH variable to the actual Hub path and save
4. Execute the Test.bat file in the Command Prompt

Expected results: Errorlevel is always 0 since all the commands executed successfully
Actual results: Errorlevel is set to 1 after executing Hub CLI commands

Reproducible with: 2.4.2

Notes:
-The "cd" command at the beginning is used to make sure that the Errorlevel is 0
-Errorlevel 1 usually means that the previous command exited with an error

  1. Resolution Note:

    Works as designed. Feature improvement request. Will review with a team. 

Log in to vote on this issue

Comments (4)

  1. RageAgainstThePixel

    Dec 21, 2022 18:09

    This was fixed in HUB 3.4.0

  2. dmitriy_yesarev

    Dec 21, 2022 08:58

    yea.. say it to microsoft's robocopy

  3. stan_unity969

    Sep 02, 2022 13:40

    Does this then mean that the unity hub always returns exitcode 1 regardless of errors or does this just mean that in this case Unity Hub exitcode 1 means ok and there are other error codes for failures.

    and if so what are the other exit codes?

  4. Thygrrr

    Jul 18, 2022 20:53

    Are you kidding us?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues