Skip to content

Disable tests that fail on non-master branches - #45455

Merged
tvolkert merged 1 commit into
flutter:masterfrom
tvolkert:devbeta
Nov 25, 2019
Merged

tvolkert merged 1 commit into
flutter:masterfrom
tvolkert:devbeta

Conversation

@tvolkert

Copy link
Copy Markdown
Contributor

Description

Failing tests in non-master branches make us blind to real failures. This disables the ones that are currently failing (some because we've explicitly turned functionality off in non-master channels - others due to issues).

Related Issues

#45453

Checklist

  • I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
  • I signed the [CLA].
  • I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
  • I updated/added relevant documentation (doc comments with ///).
  • All existing and new tests are passing.
  • The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
  • I am willing to follow-up on review comments in a timely manner.

@fluttergithubbot

Copy link
Copy Markdown
Contributor

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@fluttergithubbot fluttergithubbot added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Nov 23, 2019
@tvolkert
tvolkert requested a review from Hixie November 23, 2019 07:59
@tvolkert

Copy link
Copy Markdown
Contributor Author

@fkorotkov can you review the changes to the Cirrus config file?

@xster

xster commented Nov 23, 2019

Copy link
Copy Markdown
Member

Is this a temporary disable for #45453? If so, do we just need to do it for the failing shard?

@xster

xster commented Nov 23, 2019

Copy link
Copy Markdown
Member

LGTM

@fkorotkov

Copy link
Copy Markdown
Contributor

Agreed with @xster about just disabling the failing shard. 🤔

@tvolkert

Copy link
Copy Markdown
Contributor Author

do we just need to do it for the failing shard?

But it passes on PRs and on master. I'd prefer not to regress by having no test coverage at ToT.

@tvolkert

Copy link
Copy Markdown
Contributor Author

@fkorotkov is the syntax correct (i.e. are grouping parenthesis supported in .cirrus.yml)?

@fkorotkov

Copy link
Copy Markdown
Contributor

Syntax is correct! () are supported. 👌

@xster

xster commented Nov 24, 2019

Copy link
Copy Markdown
Member

<just nitting/feel free to ignore> I don't mean to disable them across the board. I just meant to add the master filter like you're doing on fewer shards</>

@tvolkert

Copy link
Copy Markdown
Contributor Author

Gonna merge as-is since I'm afk for the next 24 hours 🙂

@tvolkert
tvolkert merged commit bae92c3 into flutter:master Nov 25, 2019
@tvolkert
tvolkert deleted the devbeta branch December 3, 2019 19:10
@tvolkert

tvolkert commented Dec 3, 2019

Copy link
Copy Markdown
Contributor Author

@fkorotkov how come the tests are still running here: https://github.com/flutter/flutter/runs/331679315

@fkorotkov

Copy link
Copy Markdown
Contributor

@tvolkert I think it was triggered because of the chnagesInclude part for Windows tasks: https://github.com/flutter/flutter/blob/beta/.cirrus.yml#L406

I see that Cirrus found 300 files changed for the branch. 🤔

@tvolkert

tvolkert commented Dec 3, 2019

Copy link
Copy Markdown
Contributor Author

Ah, I see - thanks! I'll have to adjust the condition 🙂

tvolkert added a commit that referenced this pull request Dec 4, 2019
tvolkert added a commit that referenced this pull request Dec 4, 2019
This is a follow-on to #45455 - the test failures indicated a
real problem, so re-enabling the tests on non-master.

#45453
@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

c: contributor-productivity Team-specific productivity, code health, technical debt.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants