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.

Sign up for GitHub

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

Jump to bottom

pytest takes too long #729

Open
andre-merzky opened this issue Jul 9, 2019 · 3 comments
Open

pytest takes too long #729

andre-merzky opened this issue Jul 9, 2019 · 3 comments
Labels
priority:low topic:testing type:performance

Comments

@andre-merzky
Copy link
Member

The collection phase takes 5 minutes, which seems terribly long. For comparison, it takes 0.3 seconds for RU, 0.25 seconds for RP and 0.6 seconds for RE. I could not find the reason for this - any idea? This makes running the tests after some changes rather unattractive...
@mturilli
Copy link
Contributor

mturilli commented Jul 9, 2019

'Smells' like a timeout?

@iparask
Copy link
Contributor

iparask commented Jul 9, 2019

Or way to many test cases. I saw that the test folders has a lot of tests. Do you think that the unit tests are enough? I think we should have travis run only the unit tests.

@andre-merzky
Copy link
Member Author

@iparask : SAGA has 77 test, EnTK has 119 ...

@mturilli : might well be, and strace shows indeed many timing calls - but I could not trace sufficient to see if and on what it would time out... :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority:low topic:testing type:performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@andre-merzky @mturilli @iparask @AymenFJA