zentol commented on a change in pull request #10976: [FLINK-13978][build
system] Add experimental support for building on Azure Pipelines
URL: https://github.com/apache/flink/pull/10976#discussion_r373455464
##########
File path: tools/travis_watchdog.sh
##########
@@ -273,27 +280,27 @@ cd ../../
case $TEST in
(misc)
if [ $EXIT_CODE == 0 ]; then
- printf
"\n\n==============================================================================\n"
- printf "Running bash end-to-end tests\n"
- printf
"==============================================================================\n"
+ echo
"\n\n==============================================================================\n"
+ echo "Running bash end-to-end tests\n"
+ echo
"==============================================================================\n"
FLINK_DIR=build-target
flink-end-to-end-tests/run-pre-commit-tests.sh
EXIT_CODE=$?
else
- printf
"\n==============================================================================\n"
- printf "Previous build failure detected, skipping bash end-to-end
tests.\n"
- printf
"==============================================================================\n"
+ echo
"\n==============================================================================\n"
+ echo "Previous build failure detected, skipping bash end-to-end
tests.\n"
+ echo
"==============================================================================\n"
fi
if [ $EXIT_CODE == 0 ]; then
- printf
"\n\n==============================================================================\n"
- printf "Running java end-to-end tests\n"
Review comment:
I didn't realize at this point that you're calling the _travis_ watchdog
from the azure scripts ;)
Consider this comment resolved. Do note however that there are plenty of
printf statements in the e2e scripts that either have to modified as well or we
figure out why printf isn't working on azure.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
