Skip to content

Conversation

@nicoddemus
Copy link
Member

Using system python directly, given that the old approach no longer works.

This is related to the recently published new trusty image, given that setting group: deprecated-2017Q2 made the build work again in my tests.

Since upgrading to the latest trusty image, the previous approach
no longer works. Using system python directly was how I managed to make
this work again.
/etc/init.d/xvfb doesn't exist in the new image
@nicoddemus nicoddemus requested a review from The-Compiler July 11, 2017 23:22
@coveralls
Copy link

coveralls commented Jul 11, 2017

Coverage Status

Changes Unknown when pulling a90fd3e on nicoddemus:fix-travis into ** on pytest-dev:master**.

Copy link
Member

@The-Compiler The-Compiler left a comment

Choose a reason for hiding this comment

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

Reminds me I should pick up #165 again... 😆

- catchsegv coverage run --source=pytestqt setup.py test
- tox -e lint
- sudo catchsegv coverage run --source=pytestqt setup.py test
- sudo tox -e lint
Copy link
Member

Choose a reason for hiding this comment

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

Why do those need sudo?

Copy link
Member Author

Choose a reason for hiding this comment

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

setuptools (or distutils) would complain about not being able to write some files somewhere, I don't remember where exactly... TBH I didn't investigate it too much. 😅

@The-Compiler The-Compiler merged commit c0b22ad into pytest-dev:master Jul 12, 2017
@The-Compiler
Copy link
Member

Well, if it works, why not 😆

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

Successfully merging this pull request may close these issues.

3 participants