Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
tests: add the slow tag for ros snapd integration test #1602
Conversation
kyrofa
approved these changes
Oct 10, 2017
This looks excellent. I do have one question: What if we have slow integration tests outside of the snapd suite? Should the slow_test attribute be moved up a class?
|
@kyrofa if that happens, we need to talk about it. The other suites shouldn't be slow, ideally. If we need it, we just move the var to the parent class and add it to the debian control. |
|
can someone re-trigger the failing test jobs? |
|
@sergiusens This won't pass on
|
|
We're skipping instead, as in #1621, which has now landed. I just updated the branch, and will re-run the tests. |
| + | ||
| +Some tests take too long. This affects the pull requests because we have to wait for a long time, and they will make Travis CI timeout because we have only 50 minutes per suite in there. The solution is to tag these tests as slow, and don't run them in all pull requests. These tests will only be run in autopkgtests. | ||
| + | ||
| +To mark a test as slow, set `slow_test = True` before the test `setUp`. |
sergiusens
Oct 17, 2017
Collaborator
all implementations in here set it as a class attribute instead of in setUp. While working it is confusing and potentially error prone.
elopio
Oct 17, 2017
Member
I think it makes it less error prone to put it as a class attribute, because that assignment will always run before setUp.
From your comment, it's not clear what's your preference. I could document that the slow_test = True must be set in a class attribute, which is not totally correct, but could make it easier to understand.
elopio commentedOct 10, 2017
•
Edited 1 time
-
elopio
Oct 10, 2017
./runtests.sh static?./runtests.sh unit?Requires #1603