如何在 Windows 批处理编程中获取管道中命令的错误级别?

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/877639/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-09-09 06:22:09  来源:igfitidea点击:

How do I get the error level of commands in a pipe in Windows batch programming?

windowsbatch-filebatch-processing

提问by

Batch files return the error code of the last command by default.

批处理文件默认返回最后一条命令的错误代码。

Is it somehow possible to return the error code of a former command. Most notably, is it possible to return the error code of a command in a pipe?

是否有可能以某种方式返回以前命令的错误代码。最值得注意的是,是否可以在管道中返回命令的错误代码?

For example, this one-line batch script

例如,这个单行批处理脚本

foo.exe

returns the error code of foo. But this one:

返回foo的错误代码。但是这个:

foo.exe | tee output.txt

always returns the exit code of tee, which is zero.

始终返回tee的退出代码,该代码为零。

回答by Nick Collier

I had a similar problem and settled on the following solution as I did not need to detect the exact error code just success or failure.

我遇到了类似的问题,并确定了以下解决方案,因为我不需要检测确切的错误代码,只是成功或失败。

echo > .failed.tmp    

( foo.exe && del .failed.tmp ) | tee foo.log

if exist .failed.tmp (
    del .failed.tmp
    exit /b 1
) else (
    exit /b 0
)

回答by Nashev

To call tee for entry bat-file, not for single command, and use errorlevel freely, I use trick like this:

要调用 tee 进入 bat 文件,而不是单个命令,并自由使用 errorlevel,我使用了这样的技巧:

if "%1" == "body" goto :body
call %0 body | tee log.txt
goto :eof
:body

set nls_lang=american_america
set HomePath=%~dp0

sqlplus "usr/pwd@tnsname" "@%HomePath%script.sql" 
if errorlevel 1 goto dberror

rem Here I can do something which is dependent on correct finish of script.sql    

:dberror

echo script.sqlerror failed

it separates using tee from calling any commands inside batch.

它将使用 tee 与调用批处理中的任何命令分开。

回答by whitey04

The %ERRORLEVEL% variable doesn't get updated before the piped command is run; you have to use a wrapper as advised in the other answers.

%ERRORLEVEL% 变量在管道命令运行之前不会更新;您必须按照其他答案中的建议使用包装器。

However, you canuse "IF ERRORLEVEL #". For example:

但是,您可以使用“IF ERRORLEVEL #”。例如:

(
type filename
@REM Use an existing (or not) filename to test each branch
IF ERRORLEVEL 1 (echo ERROR) ELSE (echo OKAY)
) > logfile.txt

The ECHO will only run if an error was returned; however %ERRORLEVEL% seems inconsistent.

ECHO 只会在返回错误时运行;但是 %ERRORLEVEL% 似乎不一致。

Edit:Changed example to be runnable as-is.

编辑:将示例更改为可按原样运行。

回答by whitey04

One workaround is to make an indirection through a file.

一种解决方法是通过文件进行间接访问。

Like this

像这样

foo.exe > tmp.txt
set FOOERR=%ERRORLEVEL%
cat tmp.txt
exit %FOOERR%

回答by crusader

After about one day of digging, I found a way to do that:

经过大约一天的挖掘,我找到了一种方法:

set error_=0
9>&1 1>&2 2>&9 (for /f "delims=" %%i in ('9^>^&1 1^>^&2 2^>^&9 ^(^(^(2^>^&1 call "%homeDir%%1"^) ^|^| ^(1^>^&2 2^>nul echo FAILED^)^) ^| 2^>nul "%homeDir%mtee" /T /+ "%homeDir%logs\%date_%_%1.log"^)') do (set error_=1))

exit /b %error_%

In the example above "%homeDir%%1" is being executed and its output is piped to "%homeDir%mtee". This line detects failures (I'd suggest you to draw a diagram of batch contexts and their stdin/stdout/stderr assignments in order to understand what it does :-) ). I did not find a good way to extract the actual errorlevel. The best thing I got was to replace the 'echo' command with some batch script call 'call rc.bat' which look like:

在上面的例子中,“%homeDir%%1”正在被执行,它的输出通过管道传送到“%homeDir%mtee”。此行检测失败(我建议您绘制批处理上下文及其 stdin/stdout/stderr 分配的图表,以便了解它的作用:-))。我没有找到提取实际错误级别的好方法。我得到的最好的事情是用一些批处理脚本调用 'call rc.bat' 替换 'echo' 命令,它看起来像:

@echo %errorlevel%

and then replace 'set error_=1' with 'set error_=%%i'.

然后将“set error_=1”替换为“set error_=%%i”。

But the problem is that this call may fail too, and it is not easy to detect that. Still, it is much better than nothing -- I did not find any solution for that on the Internet.

但问题是这个调用也可能失败,而且不容易检测到。尽管如此,这总比没有好——我没有在互联网上找到任何解决方案。

回答by Fritz

You can solve the problem by creating a wrapper around your command file:

您可以通过在命令文件周围创建包装器来解决问题:

rem wrapper for command file, wrapper.cmd

call foo.exe

echo %errorlevel%

if errorlevel 1 goto...

Then append tee to the wrapper:

然后将 tee 附加到包装器:

wrapper.cmd | tee result.log

Of course this does not exactly the same, e.g. if you want to log in several files in the wrapped file, it is not possible, but in my case it solved the problem.

当然这并不完全相同,例如,如果您想在包装文件中登录多个文件,这是不可能的,但在我的情况下它解决了问题。