-
Notifications
You must be signed in to change notification settings - Fork 10
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
exit code from mtee instead piped process even with /E #4
Comments
same issue here, sometimes it could return expected exit code, but most of time, it will exit with 259.
|
I had hit the same issue. I beleave it is some kind of synchronization or race condition issue in the expressions like this:
I think the case 2 happens here because if try to add some pause or sleep command into the
, where 100 is milliseconds The issue disappears. In mine case 30 milliseconds was enough. But in some cases even 50 ms is not enough. |
For those who suffers from the issue, there is a better implementation without need an explicit pipe from You can run instead of:
This:
It is better because it can pipe |
Hi, sorry for my english,
it seems mtee keep return an errorlevel code itself , instead errorlevel code of the piped process.
I've a 259 error code with mtee, I have 0 errorlevel with process output with >log.txt
Any idea ?
Thanks in advance for your job.
The text was updated successfully, but these errors were encountered: