Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Disallow failure of the coverage build in Travis? #101

Copy link
Copy link
@zware

Description

@zware
Issue body actions

Since python/cpython#1775 was merged, the coverage build in Travis actually passes all tests. Should we remove the allow_failures key to make sure that it continues to do so? That would mean an extra ~15 minutes between commit and approval from Travis, but as it's already ~20 minutes, I don't think it's that big of a deal. In my experience, I'm not going to sit around waiting for 20 minutes anyway; I'll have moved on to something else long before then and probably won't check back until long after the build has finished.

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.