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

Better error reporting when a file is not found in the copy task #173

Open
gijsroge opened this issue May 14, 2020 · 0 comments
Open

Better error reporting when a file is not found in the copy task #173

gijsroge opened this issue May 14, 2020 · 0 comments

Comments

@gijsroge
Copy link
Member

gijsroge commented May 14, 2020

Is this something I can implement in the current state? Or are you planning on revising the entire copy functionality any time soon?

This is the current output when you have a file that cannot be found:

[14:29:43] Starting 'setEnvironment'...
[14:29:43] Finished 'setEnvironment' after 537 μs
[14:29:43] Starting 'clean'...
[14:29:43] Finished 'clean' after 3.21 ms
[14:29:43] Starting 'copy'...
[14:29:43] The following tasks did not complete: build, copy
[14:29:43] Did you forget to signal async completion?
error Command failed with exit code 1.
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

1 participant