This is an automated email from the ASF dual-hosted git repository.

kfaraz pushed a commit to branch 30.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git


The following commit(s) were added to refs/heads/30.0.0 by this push:
     new ff180557e75 [Backport] Disable upload of coverage report to codecov.io 
(#16347) (#16353)
ff180557e75 is described below

commit ff180557e75d68f1afb532a7e0d677df003d4f40
Author: AmatyaAvadhanula <[email protected]>
AuthorDate: Tue Apr 30 10:42:29 2024 +0530

    [Backport] Disable upload of coverage report to codecov.io (#16347) (#16353)
    
    Co-authored-by: Kashif Faraz <[email protected]>
---
 .github/scripts/unit_tests_script.sh | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/.github/scripts/unit_tests_script.sh 
b/.github/scripts/unit_tests_script.sh
index 1f5407b9584..e048a19c4af 100755
--- a/.github/scripts/unit_tests_script.sh
+++ b/.github/scripts/unit_tests_script.sh
@@ -74,5 +74,7 @@ then
   { printf "\n\n****FAILED****\nDiff code coverage check failed. To view 
coverage report, run 'mvn clean test jacoco:report' and open 
'target/site/jacoco/index.html'\nFor more details on how to run code coverage 
locally, follow instructions here - 
https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md#running-code-coverage-locally\n\n";
 && echo "coverage_failure=true" >> "$GITHUB_ENV" && false; }
 fi
 
-{ for i in 1 2 3; do curl -o codecov.sh -s https://codecov.io/bash && break || 
sleep 15; done }
-{ for i in 1 2 3; do bash codecov.sh -X gcov && break || sleep 15; done }
+# Commented out as codecov visualizations are currently not being used in the 
Druid community
+# and cause PR failures due to rate limiting (see 
https://github.com/apache/druid/pull/16347)
+# { for i in 1 2 3; do curl -o codecov.sh -s https://codecov.io/bash && break 
|| sleep 15; done }
+# { for i in 1 2 3; do bash codecov.sh -X gcov && break || sleep 15; done }


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to