Let's turn the codecov-commenter OFF

[wombatu-kun]

Does anybody really look at codecov reports?
I don't see any profit of it, only annoying spam. Too much spam.
On each commit in PRs that I raise or review, I recieve tens of emails that I dont need at all. Let's turn it off, please.

[danny0405]

+1

[wombatu-kun]

1 PR review, 6 commits => ~100 emails in 5 hours.

[wombatu-kun]

I dug into why this is so noisy. It is a combination of three things in our current setup:

1. behavior: new in .codecov.yml: on every coverage upload Codecov deletes the previous PR comment and posts a brand-new one. Each new post is a fresh GitHub comment, and that is what sends an email (status checks like codecov/project / codecov/patch do not email; comments do).
2. ~14 separate uploads per commit: in .github/workflows/bot.yml coverage is uploaded once per test job, each with its own flags: (spark-client-hadoop-common, utilities, common-and-other-modules, spark-java-tests, spark-scala-tests, hadoop-mr-java-client, ...). One commit therefore produces ~14 upload events, each starting a comment cycle.
3. No after_n_builds is set, so Codecov comments as uploads trickle in rather than once at the end. Combined with behavior: new and parallel uploads, the "delete old + post new" logic races and several comments pile up per commit.

Net effect: ~14 comment/email events per commit, which lines up with the "6 commits => ~100 emails" we are seeing.

Options, lightest to heaviest:

• comment: false: turn the PR comment off entirely. Coverage is still uploaded and the status checks stay, but no comment and no emails.
• behavior: default: keep one comment that is edited in place (edits do not send new emails). One quiet comment per PR.
• behavior: once: post once, never repost.
• after_n_builds: <N>: wait for N uploads before commenting. Fragile, because N must track the job count.
• Stop uploading: remove the upload + JaCoCo report-generation steps from bot.yml. This also drops the status checks and actually saves CI minutes, but is a bigger change and matters if any status check is required for merge.

My vote: turn it fully off with comment: false for now, at least as a temporary measure, until someone shows they actually rely on the Codecov reports and re-enables it deliberately. It is a one-line change, zero risk to merges (it does not touch the status checks), and it stops the spam immediately.

PR: #18994

[danny0405]

+1 to this, it is less useful(I actually never check it) since we have hudi-agent assist for reviewing now.