-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Skip slow tests on Travis #12697
Skip slow tests on Travis #12697
Conversation
Hmm, these tests started failing on master on Travis a while ago. #10738 I'm not familiar with gz so I never figured out the cause. |
shouldn't you put XFAIL on them rather than SKIP... |
I will merge this as it just surfaced an issue but at least it now runs all tests. |
@bukka |
yeah but it marks test as having potentially issue that might need to be investigated. But I see that you also created an issue for that so it's fine |
Right. It would be more useful if CI failed if XFAIL succeeds, as it only warns and people rarely look at the CI output of succeeded jobs it's not very helpful. This would require writing more precise |
Some XFAIL tests are actually flaky which I think is ok because one might not need to spend too much time to investigate XFAIL. I think the useful think about XFAIL is that it's listed in CI output compare to skip ones. So if something is skipped, it will more likely get forgotten. But if there's also GH issue which is ideal case, then it's fine I think. |
I don't think
Yes, user indication is arguably the best part about xfail. |
Travis jobs often fails due to not completing in 50 minutes. When it's successful, it's very close to 50 minutes so we need to do something about reducing the time of tests of travis. The most effective option should be to skip all slow tests which is probably fine on travis as it's just for s390x arch which is primarily to test a big endian so missing out on few slow tests should be hopefully fine...