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

Why does pytest use two different CI Builds? #3418

Closed
rachel1792 opened this issue Apr 21, 2018 · 4 comments
Closed

Why does pytest use two different CI Builds? #3418

rachel1792 opened this issue Apr 21, 2018 · 4 comments
Labels
type: question general question, might be closed after 2 weeks of inactivity

Comments

@rachel1792
Copy link

And why might a branch pass one build but not the other?

screen shot 2018-04-18 at 6 57 52 pm

@pytestbot
Copy link
Contributor

GitMate.io thinks possibly related issues are #2683 (Use tox release candidates in pytest CI), #2688 (Consider using Build Stages in Travis CI), #3411 (What does Pytest use to determine the error runtime.), #1123 (does pytest support to this way to collect test cases?), and #1411 (Pytest stops).

@pytestbot pytestbot added the type: bug problem that needs to be addressed label Apr 21, 2018
@RonnyPfannschmidt
Copy link
Member

@rachel1792 on travis is linux an on appveyor is windows - we do this to ensure we dont break differtent os's

@RonnyPfannschmidt RonnyPfannschmidt added type: question general question, might be closed after 2 weeks of inactivity and removed type: bug problem that needs to be addressed labels Apr 21, 2018
@nicoddemus
Copy link
Member

@rachel1792 it seems your question has been answered so I'm closing this for now. Feel free to followup with further questions. 👍

@rachel1792
Copy link
Author

Thanks guys!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question general question, might be closed after 2 weeks of inactivity
Projects
None yet
Development

No branches or pull requests

4 participants