Github user ryan-williams commented on the pull request:
https://github.com/apache/spark/pull/2848#issuecomment-66904556
interesting. this may be more appropriate on my [gigantic thread about
testing/development best
practices](http://apache-spark-developers-list.1001551.n3.nabble.com/Spurious-test-failures-testing-best-practices-td9560.html),
but do you have any recommendations for debugging this?
AFAICT, this seems to be a test that requires a full assembly-build to run;
I've tried running `mvn -Dsuites=FileServerSuite test` on a branch cut from the
same `master` that this PR is cut from
(b004150adb503ddbb54d5cd544e39ad974497c41) and I get strange failure modes,
usually just that the test seems to hang for hours. I ran a `mvn package
-DskipTests` to build a fresh assembly, and tried again, and it still hung. I'm
currently waiting on a `mvn clean package -DskipTests`, at which point I will
try again. Debugging / iterating on a particular (integration) test, like I
need to do here, remains a prohibitively slow process for me.
I'm guessing this failure must have something to do with having moved /
removed (temp?) files that this test was relying on; my naive approach will be
to comment out some of the move/removal lines and see if that fixes the test,
but on pain of running a `mvn clean package -DskipTests` every time.
Is there a better way?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
