Uh oh!
There was an error while loading. Please reload this page.
[SPARK-9818] Re-enable Docker tests for JDBC data source - #9503
[SPARK-9818] Re-enable Docker tests for JDBC data source#9503JoshRosen wants to merge 21 commits into
Conversation
JoshRosen
commented
Nov 5, 2015
/cc @marmbrus for review. |
JoshRosen
commented
Nov 5, 2015
Although the tests should automatically pull any missing Docker images, I went ahead and manually pulled them on all of the AMP Jenkins workers. This uncovered an issue where two of the workers' Docker filesystems had entered a safe mode that prevented image pulling, so I logged in and fixed that. |
There was a problem hiding this comment.
I always forget your can do this...
marmbrus
commented
Nov 5, 2015
For posterity, is there any easy way to do the parallel pull if we upgrade one of the images or add a new one? |
JoshRosen
commented
Nov 5, 2015
Here's the command that I used: |
marmbrus
commented
Nov 5, 2015
Tested this locally and other than needing to set |
SparkQA
commented
Nov 5, 2015
Test build #1990 has finished for PR 9503 at commit
|
SparkQA
commented
Nov 5, 2015
Test build #45145 has finished for PR 9503 at commit
|
SparkQA
commented
Nov 5, 2015
Test build #1992 has finished for PR 9503 at commit
|
SparkQA
commented
Nov 5, 2015
Test build #1991 has finished for PR 9503 at commit
|
There was a problem hiding this comment.
Woah, this is an ancient version of docker-client. I'll try using a newer release to see if that magically fixes the ASM issues.
SparkQA
commented
Nov 6, 2015
Test build #45172 has finished for PR 9503 at commit
|
SparkQA
commented
Nov 6, 2015
Test build #45176 has finished for PR 9503 at commit
|
SparkQA
commented
Nov 6, 2015
Test build #45214 has finished for PR 9503 at commit
|
SparkQA
commented
Nov 6, 2015
Test build #45215 has finished for PR 9503 at commit
|
JoshRosen
commented
Nov 10, 2015
Something really weird is going on here. Following the advice at http://stackoverflow.com/a/21876380/590203, I added the following line to When I run this locally with I get This doesn't make sense, though: I still don't see where that JAR is coming from. |
JoshRosen
commented
Nov 10, 2015
In fact, I used some of the handy classpath-debugging tools in JHades to dump more information and it looks like According to the Java 7 JAR specification (emphasis mine):
Assuming that "relative" means "relative to the JAR containing the manifest", I think that what's happening is that this is causing the What a giant mess. It looks like the |
pwendell
commented
Nov 10, 2015
I only reviewed the build changes, but they look good to me. |
JoshRosen
commented
Nov 10, 2015
I found this Manifest class-path issue to be extremely puzzling, but it looks like other people have hit it as well: https://dzone.com/articles/jar-manifest-class-path-is-not-for-java-applicatio Quote:
This puzzling behavior is described a bit more explicitly in Java 8's JAR specification. |
SparkQA
commented
Nov 10, 2015
Test build #45495 has finished for PR 9503 at commit
|
JoshRosen
commented
Nov 10, 2015
Created https://tachyon.atlassian.net/browse/TACHYON-1254 for this; this will be worked around in Spark via my |
JoshRosen
commented
Nov 10, 2015
And just to be 100%-sure that it was the Tachyon manifests's fault, I used the following command to delete them and verified that doing so fixed the tests: |
JoshRosen
commented
Nov 10, 2015
Jenkins, retest this please. |
SparkQA
commented
Nov 10, 2015
Test build #45536 has finished for PR 9503 at commit
|
JoshRosen
commented
Nov 10, 2015
Looks like a flaky streaming test? Jenkins, retest this please. |
SparkQA
commented
Nov 10, 2015
Test build #2030 has finished for PR 9503 at commit
|
rxin
commented
Nov 10, 2015
I'm merging this. Thanks. |
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>
tedyu
commented
Nov 13, 2015
|
markhamstra
commented
Nov 13, 2015
Similar failure with both |
JoshRosen
commented
Nov 13, 2015
Maybe the docker daemon didn't get started / restarted on a subset of the machines? |
tedyu
commented
Nov 14, 2015
Should MySQLIntegrationSuite be disabled since the test failure is reproducible ? |
JoshRosen
commented
Nov 14, 2015
If you don't have Docker set up locally, you can use the |
lvc
commented
Oct 3, 2016
The backward compatibility reports for Jersey* libraries are now available in the API Tracker project: https://abi-laboratory.pro/java/tracker/timeline/jersey-core/ The JAPICC tool detected some servlet related changes in jersey-core 1.10: |
nonsleepr
commented
May 22, 2018
Adding following for better visibility. The problem while using The solution is to use libraryDependencies +="com.spotify"%"docker-client"%"8.11.3" classifier "shaded" |
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-clientlibrary. This patch should avoid those problems by using a version ofdocker-clientwhich 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.