-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Create seperate matrix for selenium test case #706
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
Create seperate matrix for selenium test case #706
Conversation
fa06141 to
f93998c
Compare
f93998c to
c1c883c
Compare
|
Build #3100.4 is failing (https://travis-ci.org/apache/incubator-zeppelin/jobs/108074063) for Which is unrelated. |
|
@doanduyhai any idea with test failure? |
| testDepRemoveBtn.click(); | ||
| driver.findElement(By.xpath("//button[contains(.,'Save')]")).submit(); | ||
| driver.switchTo().alert().accept(); | ||
| if (!endToEndTestEnabled()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it looks like this is from PR #654 - could we separate that out for review please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, its from #673, https://github.com/apache/incubator-zeppelin/pull/673/files#diff-fc9c6a01ec538e646b3e99c8fa19a3deR204
Sure, I've created a new PR #709 as a hot fix.
Will revert this whole file once that is merged. As we will need if (!endToEndTestEnabled()) { or else driver @Before will not initialize driver, resulting in this test case to fail.
|
Could you check out #708 ? We should avoid rerunning all tests for TEST_SELENIUM |
|
Closing this, as this is been taken care by #708 |
|
actually, I think they are addressing different parts of it. It might still make sense to have a separate matrix for just UI tests - to clarify, I was saying you might want to restrict the project list and test scope to avoid running duplicates. Reopen? |
### What is this PR for? While investigating CI failure with PR #706, I noticed that we were running all tests in each of 6 jobs in the test matrix. It seems we have accidentally switched back to running all tests even with older versions of Spark. (from PR #626 Filtering out interpreter tests for these runs help make test jobs faster (~30%) and also reduce the chance that an interpreter test might intermittently fail, thus hopefully improve CI reliability. Also changing Spark 1.2.1 to 1.2.2 (last 1.2.x release) ### What type of PR is it? Improvement ### Todos * [x] - Travis CI yml changes ### Is there a relevant Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-665 ### How should this be tested? Run Travis CI ### Screenshots (if appropriate) N/A ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No Author: Felix Cheung <felixcheung_m@hotmail.com> Closes #708 from felixcheung/testprofile and squashes the following commits: ac3bd72 [Felix Cheung] fix project list b0c8b9b [Felix Cheung] add spark tests 27d57fe [Felix Cheung] fix project list cd0cb97 [Felix Cheung] test project list for older spark versions
|
So as you can see, it's re-running all interpreter tests when TEST_SELENIUM="true" could you add the |
|
The error about the CassandraInterpreterTest is because for unit test, I start an embedded Cassandra server and sends CQL queries to test the interpreter. The exception stack just says that the interpreter cannot connect to the server. It means that the embedded server failed to start for some reason. Can you give me the full stack trace or give me a link to the logs ? |
|
Thanks @felixcheung So I had a look into the log file, below is some extract: If you look at the timestamp, it took more than 7 secondes to create a few tables in the embedded Cassandra. It means that the embedded Cassandra server was busy because not enough system resources. I guess the Travis CI server was quite busy when we launched the test. There is really nothing to do other than retry |
|
@doanduyhai I guess we could check on this - if it has become a frequent problem we could get travis to retry tests. I have not seen this much, on the other hand, selenium test failures seem to be more frequent. |
c8ac068 to
5fce1b2
Compare
31c4a28 to
2d334ff
Compare
|
@felixcheung made relevant changes, merged with 65b47e5, and #709 (master), CI green. |
|
looks good |
|
merging today if no more comments |
What is this PR for?
A lot of time travis CI breaks because of selenium test case, and at that point it becomes trivial to know the exact reason. Hence, in this PR creating a separate matrix for testing selenium test cases.
What type of PR is it?
Improvement
Is there a relevant Jira issue?
N/A
How should this be tested?
Check travis UI. It should have a new matrix added.