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

travis failed on master / not running #85

Closed
belm0 opened this issue Nov 9, 2018 · 4 comments
Closed

travis failed on master / not running #85

belm0 opened this issue Nov 9, 2018 · 4 comments

Comments

@belm0
Copy link
Member

belm0 commented Nov 9, 2018

@belm0
Copy link
Member Author

belm0 commented Nov 9, 2018

https://travis-ci.org/HyperionGray/trio-websocket/jobs/453122094

$ make test
pytest --cov=trio_websocket
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/pluggy/__init__.py", line 397, in load_setuptools_entrypoints
    plugin = ep.load()
  File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2404, in load
    self.require(*args, **kwargs)
  File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2427, in require
    items = working_set.resolve(reqs, env, installer, extras=self.extras)
  File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 875, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (pytest 3.3.0 (/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages), Requirement.parse('pytest>=3.6'))

I have no idea why travis isn't running on those two PR's.

@belm0
Copy link
Member Author

belm0 commented Nov 10, 2018

build and build badge are fixed

still no idea why travis is not running on some PR's

@mehaase
Copy link
Contributor

mehaase commented Nov 10, 2018

I think it didn't build because I changed Travis settings. I had both the "branch" and "PR" triggers turned on, but it was building twice for each PR, so I turned off the PR trigger. But I guess the branch trigger doesn't apply to external repos...

screen shot 2018-11-10 at 1 03 43 pm

I've turned the PR trigger back on just now.

@belm0
Copy link
Member Author

belm0 commented Nov 10, 2018

thank you

@belm0 belm0 closed this as completed Nov 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants