-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
Job with manualExit: true fails without a proper reason #578
Comments
Maybe @tobyspark you have an idea what could be wrong? |
Writing the same error as if there would have been an error is confusing and harder to debug. Additionally, validating build results through the logs is not too intuitive, therefore providing information on the missing build result section should help clarify the problem.
…-manualExit is set to true
I found the problem to be the missing build reports, also mentioned in #575, #564, #563 and #535. Since there are already other issues on the topic, I will close this one. As a workaround, you can add an output to your script that matches the expected build results. https://discord.com/channels/710946343828455455/1143838569220280321 |
Sorry for missing the mention – was out with Covid. See also PR #576 |
No worries, I hope you're feeling better again! Thanks a lot for pushing the manual exit topic, that is a very needed addition to the project ❤️ |
Bug description
I tried upgrading to current main branch to elevate the new feature of #574 with a job to update unity packages (which I was successfully using for some time with a forked version of v2 with the quit parameter removed). The file I ran is this one: JohannesDeml/UnityWebGL-LoadingTest@9a439f3#diff-20be283f9ab3995c688edbbc13b4692464de2a738a624c2ff29f5d426e5e5cef
From the logs everything worked as expected, I get to the line where I call
EditorApplication.Exit(0);
, and it looks like Unity is shutting down correctly. However, in the end I get this:Apparently something still is flagged as failed (see
##[error]There was an error building the project. Please read the logs for details.
), even though everything looks fine to me.How to reproduce
Expected behavior
Job should not fail if
EditorApplication.Exit(0);
is called at the endAdditional details
The text was updated successfully, but these errors were encountered: