You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am also having problems analyzing errors related to the error stream not clearly marked in the output.
Is it possible to better surface the error stream contents for analysis purposes?
==> Downloading from https://github-production-release-asset-2e65be.s3.amazonaws.com/45861018/d7233980-b740-11e8-8a89-b30a1e0ac118?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20191025%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20191025T032427Z&X-Amz-Expires=300&X-Amz-Signature=3b8eb6339119ea8413ec2b27a14273171621c38b47d64e9fa132b7e185313db8&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dgit-credential-manager-2.0.4.jar&response-content-type=application%2Foctet-stream
🍺 /usr/local/Cellar/git-credential-manager/2.0.4: 4 files, 2.4MB, built in 4 seconds
Cloning spec repo `msblox` from `[email protected]:v3/msblox/CocoaPods/CocoaPods`
##[error]Bash wrote one or more lines to the standard error stream.
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment
Server - Azure Pipelines
Account name -https://wavespacemadrid.visualstudio.com
-Team project name - SIRE
Agent - Hosted
Issue Description
In the build definition, the customer runs tests using the following script in the BASH task :
docker logs $(docker ps -aq)
docker exec $(docker ps -q) python3 manage.py test --keepdb
docker exec $(docker ps -q) ls -la SIRE/tests
and gets the error - "Bash wrote one or more lines to the standard error stream"
It is a Django Unit Test.
Attached is the complete build log.
How can he see the error in the logs?
Is there a way to get the error message on our build console?
Any inputs on this?
Task logs
Error logs
logs_320.zip
The text was updated successfully, but these errors were encountered: