Skip to content

Conversation

@christopherfujino
Copy link
Contributor

Only run tool_coverage test shard on master, which should in turn lead to codecov only evaluating master commits. We only really care about running on master, and we don't want unreliable red checks to mark release builds.

Fixes #46098.

Copy link
Contributor

@tvolkert tvolkert left a comment

Choose a reason for hiding this comment

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

This change looks ok, but it wasn't this Cirrus shard that is failing on beta - it's codecov/patch and codecov/project

Copy link
Contributor

@tvolkert tvolkert left a comment

Choose a reason for hiding this comment

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

After discussing with @christopherfujino, LGTM!

@christopherfujino
Copy link
Contributor Author

This change looks ok, but it wasn't this Cirrus shard that is failing on beta - it's codecov/patch and codecov/project

chatted offline, the end of the tool_coverage shard test uploads a report to the codecov service, which then triggers a test on their server, and results in a codecov github check.

@fluttergithubbot fluttergithubbot merged commit d88345e into flutter:master Dec 4, 2019
@christopherfujino christopherfujino deleted the better-codecov-on-master branch December 5, 2019 00:27
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Codecov is marking dev/beta releases red on github

4 participants