Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fail when detecting risky tests #22387

Merged
merged 1 commit into from Apr 12, 2017
Merged

fail when detecting risky tests #22387

merged 1 commit into from Apr 12, 2017

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Apr 12, 2017

Q A
Branch? 2.7
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

The --fail-on-risky option is available since sebastianbergmann/phpunit@7e06a82 which was first released with PHPUnit 5.2.

@xabbuh
Copy link
Member Author

xabbuh commented Apr 12, 2017

see https://travis-ci.org/symfony/symfony/builds/221231962 for how such a failing build looks like

@xabbuh xabbuh force-pushed the fail-on-risky branch 2 times, most recently from a552d21 to 4a057ec Compare April 12, 2017 06:49
@@ -34,7 +34,7 @@ protected function tearDown()
}

/**
* @dataProvider testRenderProvider
* @dataProvider renderProvider
Copy link
Member Author

Choose a reason for hiding this comment

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

This change is already in the 2.8 branch because of #22379. It looks like I missed it for the 2.7 branch in #22066.

@@ -153,6 +153,8 @@ public function testSetDefault()
public function testSetDefaultAcceptsEn()
{
$this->call('setDefault', 'en');

$this->assertSame('en', $this->call('getDefault'));
Copy link
Member Author

Choose a reason for hiding this comment

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

This change is already in the 2.8 branch because of #22379. It looks like I missed it for the 2.7 branch in #22066.

@@ -22,7 +22,7 @@
"require-dev": {
"symfony/asset": "~2.7",
"symfony/finder": "~2.3",
"symfony/form": "~2.7.25|^2.8.18",
"symfony/form": "~2.7.26|^2.8.19",
Copy link
Member Author

Choose a reason for hiding this comment

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

@@ -40,7 +40,7 @@
"symfony/dom-crawler": "^2.0.5",
"symfony/intl": "~2.3",
"symfony/security": "~2.6",
"symfony/form": "~2.7.25|^2.8.18",
"symfony/form": "~2.7.26|^2.8.19",
Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

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

👍

@fabpot
Copy link
Member

fabpot commented Apr 12, 2017

Thank you @xabbuh.

@fabpot fabpot merged commit 3792ee6 into symfony:2.7 Apr 12, 2017
fabpot added a commit that referenced this pull request Apr 12, 2017
This PR was merged into the 2.7 branch.

Discussion
----------

fail when detecting risky tests

| Q             | A
| ------------- | ---
| Branch?       | 2.7
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

The `--fail-on-risky` option is available since sebastianbergmann/phpunit@7e06a82 which was first released with PHPUnit 5.2.

Commits
-------

3792ee6 fail when detecting risky tests
@xabbuh xabbuh deleted the fail-on-risky branch April 12, 2017 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants