8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
This build has a failing unit test but the result is: Build Success
Someone could look after why it not fails?
The text was updated successfully, but these errors were encountered:
/cc @nicolas-grekas
Sorry, something went wrong.
minor #17639 [appveyor] Fix failure reporting (nicolas-grekas)
de6e3c8
This PR was merged into the 2.3 branch. Discussion ---------- [appveyor] Fix failure reporting | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #17464 | License | MIT | Doc PR | - Status: needs work Commits ------- b58f483 [appveyor] Fix failure reporting
Closing it as fixed because AppVeyor is showing again a fail status when there are failed tests. Example: https://ci.appveyor.com/project/fabpot/symfony/build/1.0.5787
No branches or pull requests
This build has a failing unit test but the result is: Build Success
Someone could look after why it not fails?
The text was updated successfully, but these errors were encountered: