Skip to content

Conversation

@mravn-google
Copy link
Contributor

CocoaPods needs upgrading on the device lab before the Swift plugin test can run.

new PluginTest('ios', <String>['-i', 'objc']),
new PluginTest('ios', <String>['-i', 'swift']),
// TODO(mravn): Re-enable this once CocoaPods is upgraded on device lab.
// new PluginTest('ios', <String>['-i', 'swift']),
Copy link
Contributor

Choose a reason for hiding this comment

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

Alternatively you could mark the test as flaky until it becomes green with Swift support.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right. But it isn't flaky. It'll fail consistently...

Copy link
Contributor

Choose a reason for hiding this comment

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

We also use the flaky flag when debugging new tests or big changes to tests when we're not sure that they will pass. If they look green after a few commits, we flip the flag.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK. Test marked flaky instead.

@yjbanov
Copy link
Contributor

yjbanov commented Mar 12, 2018

lgtm

@yjbanov
Copy link
Contributor

yjbanov commented Mar 12, 2018

Force-submitting this to unbreak the build. AppVeyor and Travis don't do anything useful with the changed file anyway.

@yjbanov yjbanov merged commit a615927 into flutter:master Mar 12, 2018
@mravn-google mravn-google deleted the silence_broken_test branch March 12, 2018 19:06
@mravn-google
Copy link
Contributor Author

Thanks, @yjbanov

DaveShuckerow pushed a commit to DaveShuckerow/flutter that referenced this pull request May 14, 2018
* Silence broken test

* Mark test as flaky instead
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 11, 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.

3 participants