I'm encountering a bug where some error messages appear before the line that produces them in the build log. For example, the following was run on a windows remote shell executor:
11:46:15 Waiting for resources...
11:46:15 Executing job (executor: main, agent: agent1)...
11:46:15 Setting up job cache...
11:46:15 Downloading job dependencies...
11:46:15 Running step "test"...
11:46:15 * was unexpected at this time.
11:46:15
11:46:15 D:\path\to\workspace>for %i in * do echo %i
11:46:15 Step "test" is failed: Command exited with code 255
The job only consists of a "test" step, containning only this script: for %%i in * do echo %%i
rainbowwphoenixx commented 2 years ago
Failed to mention that the correct syntax for this is to add parentheses around the *
Robin Shen commented 2 years ago
Tested on Windows command prompt and it does print error message before the command:
rainbowwphoenixx commented 2 years ago
You're right, running the command in a command prompt makes this appear in the right order, but I did not test with a batch file, which does have this behavior. Sorry for the inconvenience
I'm encountering a bug where some error messages appear before the line that produces them in the build log. For example, the following was run on a windows remote shell executor:
The job only consists of a "test" step, containning only this script:
for %%i in * do echo %%i