Uh oh!
There was an error while loading. Please reload this page.
[SPARK-9818][SQL][WIP]Revert SPARK-6136 to enable jdbc tests using docker - #8101
[SPARK-9818][SQL][WIP]Revert SPARK-6136 to enable jdbc tests using docker#8101yjshen wants to merge 9 commits into
Conversation
SparkQA
commented
Aug 11, 2015
Test build #40441 has finished for PR 8101 at commit
|
SparkQA
commented
Aug 11, 2015
Test build #40444 has finished for PR 8101 at commit
|
yjshen
commented
Aug 11, 2015
Jenkins, retest this please. |
SparkQA
commented
Aug 11, 2015
Test build #40448 has finished for PR 8101 at commit
|
JoshRosen
commented
Aug 11, 2015
I think that our Jenkins actually has Docker installed now, so in principle there should be a way to automate these tests once we get them working. |
SparkQA
commented
Aug 12, 2015
Test build #40632 has finished for PR 8101 at commit
|
marmbrus
commented
Aug 12, 2015
Thanks for working on this! I'd love to get these tests running again. |
SparkQA
commented
Aug 12, 2015
Test build #40649 has finished for PR 8101 at commit
|
yjshen
commented
Aug 13, 2015
|
SparkQA
commented
Aug 13, 2015
Test build #40725 has finished for PR 8101 at commit
|
yjshen
commented
Aug 13, 2015
Jenkins, retest this please. |
SparkQA
commented
Aug 13, 2015
Test build #40727 has finished for PR 8101 at commit
|
yjshen
commented
Aug 13, 2015
Jenkins, retest this please. |
SparkQA
commented
Aug 13, 2015
Test build #40751 has finished for PR 8101 at commit
|
yjshen
commented
Aug 13, 2015
pull |
marmbrus
commented
Aug 13, 2015
Can we retry? Only do it if it doesn't exist?
|
SparkQA
commented
Aug 14, 2015
Test build #40861 has finished for PR 8101 at commit
|
SparkQA
commented
Aug 14, 2015
Test build #40865 has finished for PR 8101 at commit
|
SparkQA
commented
Aug 14, 2015
Test build #40878 has finished for PR 8101 at commit
|
SparkQA
commented
Aug 15, 2015
Test build #40945 has finished for PR 8101 at commit
|
SparkQA
commented
Aug 15, 2015
Test build #40943 has finished for PR 8101 at commit
|
SparkQA
commented
Aug 15, 2015
Test build #40957 has finished for PR 8101 at commit
|
SparkQA
commented
Sep 2, 2015
Test build #41921 has finished for PR 8101 at commit
|
SparkQA
commented
Sep 2, 2015
Test build #41926 has finished for PR 8101 at commit
|
yjshen
commented
Sep 2, 2015
Pull mysql image would sometimes fail even with 5 retries... |
rxin
commented
Sep 3, 2015
cc @marmbrus what do you think? Is there a way we can preload the images on Jenkins? |
marmbrus
commented
Sep 3, 2015
Where are the errors with pulling the image? |
yjshen
commented
Sep 8, 2015
Sorry for my late reply. PostgresIntegrationSuite would fail with: |
yjshen
commented
Sep 15, 2015
After exploring all the build failure above, Mysql test only fails with |
yjshen
commented
Sep 15, 2015
I'll trigger more test build now. |
yjshen
commented
Sep 15, 2015
Jenkins, retest this please. |
3 similar comments
yjshen
commented
Sep 15, 2015
Jenkins, retest this please. |
yjshen
commented
Sep 15, 2015
Jenkins, retest this please. |
yjshen
commented
Sep 15, 2015
Jenkins, retest this please. |
SparkQA
commented
Sep 15, 2015
Test build #42476 has finished for PR 8101 at commit
|
SparkQA
commented
Sep 15, 2015
Test build #42473 has finished for PR 8101 at commit
|
SparkQA
commented
Sep 15, 2015
Test build #42474 has finished for PR 8101 at commit
|
SparkQA
commented
Sep 15, 2015
Test build #42480 has finished for PR 8101 at commit
|
yjshen
commented
Sep 15, 2015
It seems when test build triggered for multiple times in a row, only the first test build would fail and all subsequent builds success. |
JoshRosen
commented
Oct 1, 2015
I'd like to help get this patch merged so that we can re-run these tests, but before we put a lot more work into polishing it I would like to figure out whether our regular Jenkins build is the right place to run these tests. These tests are fairly heavyweight to run (since they have to download a bunch of Docker images) and might add significant amounts of time to the test runs. Therefore, I think we should skip them for the majority of pull requests and should only run them when JDBC-related code is changed (maybe just code under the Similarly, we may not want to run these tests as part of every master build. Over time, I imagine that we'll accumulate larger-and-larger regression test suites here and they're going to add a huge cost for most builds. Therefore, I think that we should try to tag these suites so that they're not run as part of most master builds but are only run once per day or something like that. |
There was a problem hiding this comment.
One concern: this has the potential to become flaky if the image is updated. I'd prefer to freeze a particular version here, for the same reason that I like things like Maven and pip --freeze.
There was a problem hiding this comment.
+1, at least we should keep on the same version of the rdbms in question (as sometimes there are tweaks, enhancements on the docker image itself)
There was a problem hiding this comment.
Hey, so what's the deal with this? Is this factory still necessary or was it an artifact of legacy Docker bugs or docker-client issues?
JoshRosen
commented
Nov 5, 2015
This patch re-enables tests for the Docker JDBC data source. These tests were reverted in #4872 due to transitive dependency conflicts introduced by the `docker-client` library. This patch should avoid those problems by using a version of `docker-client` which shades its transitive dependencies and by performing some build-magic to work around problems with that shaded JAR. In addition, I significantly refactored the tests to simplify the setup and teardown code and to fix several Docker networking issues which caused problems when running in `boot2docker`. Closes#8101. Author: Josh Rosen <joshrosen@databricks.com> Author: Yijie Shen <henry.yijieshen@gmail.com> Closes#9503 from JoshRosen/docker-jdbc-tests. (cherry picked from commit 1dde39d) Signed-off-by: Reynold Xin <rxin@databricks.com>
It's just working in progress, not ready to be reviewed.
I'd like to see if this breaks something.