Skip to content

ci: do not fail CI when Codecov test-results upload errors#1918

Merged
WilliamBergamin merged 1 commit into
mainfrom
ci-codecov-test-results-no-fail
Jul 20, 2026
Merged

ci: do not fail CI when Codecov test-results upload errors#1918
WilliamBergamin merged 1 commit into
mainfrom
ci-codecov-test-results-no-fail

Conversation

@WilliamBergamin

Copy link
Copy Markdown
Contributor

Summary

The unittest job's Upload test results to Codecov step currently sets fail_ci_if_error: true, so a transient Codecov outage or upload hiccup fails the whole CI pipeline even when every test passed.

Uploading test results to Codecov is a best-effort reporting side-channel, not a gate on code correctness. This PR flips that step to fail_ci_if_error: false — a "send and forget" upload — so a third-party upload failure no longer reddens an otherwise green build.

Scope is intentionally limited to the test-results upload. The separate coverage upload step (report_type: coverage) is left unchanged.

This mirrors slackapi/bolt-python#1552.

Testing

  • fail_ci_if_error: false is a documented codecov/codecov-action input; the workflow YAML still parses.
  • CI behavior is exercised by the workflow running on this PR.

Category

  • slack_sdk.web.WebClient (sync/async) (Web API client)
  • slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
  • slack_sdk.socket_mode (Socket Mode client)
  • slack_sdk.signature (Request Signature Verifier)
  • slack_sdk.oauth (OAuth Flow Utilities)
  • slack_sdk.models (UI component builders)
  • slack_sdk.scim (SCIM API client)
  • slack_sdk.audit_logs (Audit Logs API client)
  • slack_sdk.rtm_v2 (RTM client)
  • /docs (Documents)
  • /tutorial (PythOnBoardingBot tutorial)
  • Others (CI workflow — .github/workflows/ci-build.yml)

Requirements

  • I've read and understood the Contributing Guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've run python3 -m venv .venv && source .venv/bin/activate && ./scripts/run_validation.sh after making the changes. (CI-only change; no source code affected.)

🤖 Generated with Claude Code

The "Upload test results to Codecov" step in the unittest job is a
best-effort reporting side-channel, not a gate on code correctness. Set
fail_ci_if_error to false so a transient Codecov outage or upload error
no longer fails an otherwise passing build.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@WilliamBergamin
WilliamBergamin requested a review from a team as a code owner July 20, 2026 16:51

@zimeg zimeg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@WilliamBergamin squash and merge! 😉

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.17%. Comparing base (2cd7796) to head (ebb998a).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1918   +/-   ##
=======================================
  Coverage   84.17%   84.17%           
=======================================
  Files         118      118           
  Lines       13423    13423           
=======================================
  Hits        11299    11299           
  Misses       2124     2124           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

@WilliamBergamin
WilliamBergamin enabled auto-merge (squash) July 20, 2026 17:01
@WilliamBergamin WilliamBergamin self-assigned this Jul 20, 2026
@WilliamBergamin WilliamBergamin added the github_actions Pull requests that update GitHub Actions code label Jul 20, 2026
@WilliamBergamin
WilliamBergamin merged commit cff3dc1 into main Jul 20, 2026
31 of 32 checks passed
@WilliamBergamin
WilliamBergamin deleted the ci-codecov-test-results-no-fail branch July 20, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants