-
Notifications
You must be signed in to change notification settings - Fork 78
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
IT's error out when calling mvn verify #971
Comments
Did you try doing a Another thing that can cause problems is if Eclipse or another IDE is open and building your project while trying to do a build from the command-line. |
Also, the test in error seems to be FluoAdminImplIT. There were a few recent changes with that to fix some things. Make sure your workspace is up to date. You can check with |
@ctubbsii I tried |
Ah, right, I should have paid more attention to the initial post. Have you tried checking to see if there's an old ZK running that won't die ( |
Rebooted and still getting the same list of errors. |
Hmm. This is a tricky one and I'm running low on ideas. Just to throw some more ideas out there to try: You could try clearing out all of your local maven repository, in case one of the dependencies are corrupt. You could ensure that it is configured to use You could also check to ensure that you don't have any strange items on your class path either in your environment ( You could try cloning the git repo from scratch to a different location, and running there, to ensure there's not anything wrong with your local workspace. You could also check any logs in the target directories, for a possible hint, but I'm not really sure what to look for. You could run |
Are there any stack trace lines after the messages like I ask because I am curious if this has anything to do with the changes in #899. Each node in ZK can have an auth set. Accumulo sets auths in ZK and Fluo does optionally with the changes in #899. The paths in the error messages If you are not seeing the stack traces, then its possible that adding the mvn -X -l /tmp/fluo-build.log clean verify
# search for NoAuth
less /tmp/fluo-build.log |
@ctubbsii @keith-turner
(EDIT: extra lines truncated by @cltubbs for easier scrolling; it was just repeats of the same error above) |
Try |
@cjmctague yeah you can email me the log. If you can bzip2 or gzip it. bzip will probably compress better. |
|
Ugh, so - Also there may be info of interest in Make sure to get a video of the laptop toss, could be a hit on /r/osha or /r/wcgw |
Something else to look at is |
Another thing you could try (very much doubt this is the issue) is disabling your firewall and/or selinux (if that applies to you). The problem could also be your host name. Check the host name in any zoo.cfg and/or accumulo-site.xml files in your target directory. |
@keith-turner
There are 30 .txt files in those logs for all the various IT's failing. |
@ctubbsii |
@cjmctague what about the zookeeper server logs, anything there? |
@keith-turner
I can email them to you if you want to see the rest. Not sure if anything of these logs could be sensitive information. Edit more goodies
|
@cjmctague can you find the test org.apache.fluo.integration.impl.ZKSecretIT and delete it? I am wondering if that test is mucking things up for you. |
I noticed in the logs you emailed me that ZKSecretIT runs first and then everything after that fails. That test does modify auths in Zookeeper. |
After removing the Now the only thing preventing me from getting a successful
|
I looked at a successful Travis build and this test ran in the middle of the ITs. There are two possibilities. When this test runs first, it leaves everything in a bad state OR there is something in your environment that exposing a bug. I suspect its the latter, but not sure. I will take a look at the test and see if better cleanup could be done. Re the OracleIT, some of the error messages from it are expected. The timeout is not. Does that test consistently timeout? Could try bumping its timeout up by adding public Timeout globalTimeout = Timeout.seconds(2 * getTestTimeout()); |
My environment currently is on a mid 2012 macOS laptop with the latest version that the issues are occurring on. I run The timeout did not change anything other than it taking longer to time out. I just started an environment on my Centos7 server at school. Was able to run |
@cjmctague can you try removing the timeout rule and see if it ever completes... or set it really high. Also when its stuck, can you find the java process running the IT and run jstack on it? |
@keith-turner Removing the timeout rule just made the test never end. I just emailed you the jStack dump |
I looked at the jstack you sent, it seems like the file contains 4 jstacks. Are those for 4 different test runs? It seems in two the of the jstacks the main test thread is stuck waiting to get a timestamp from the oracle. In one of the jstacks, the main thread is stuck trying to connect to zookeeper. In the other jstack I am not sure what it is doing. |
I am seeing the same problem with |
@keith-turner Yea sorry those were four different test runs. |
It looks like some of this is related to #1000. What is the status on this issue if I may politely ask? |
I don't have a Mac to reproduce. @mikewalch , were you ever able to reproduce this? |
I have a MacBook with OS Capitan and built Fluo last week on it with maven.
Could I help somehow?
…On Jan 25, 2018 2:41 PM, "Christopher Tubbs" ***@***.***> wrote:
I don't have a Mac to reproduce. @mikewalch <https://github.com/mikewalch>
, were you ever able to reproduce this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#971 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Acg-LPdQ7f-3YnTqNSdTOqHbqSd-F6Jmks5tOQMggaJpZM4QjoYx>
.
|
@kpm1985 I think the issue needs to be reproduced. It may or may not affect only Macs. From the discussion above, we know it affects @cjmctague 's Mac builds, at the very least. If it can be reproduced, we'd need to track down the cause of the problem. If you can help with reproducing and figuring out why it's happening, please feel free to do so. |
Im curious about @cjmctague specs. Eliminating variables and such. I saw
it's around 2012 with brew, was there more info about the hardware I missed?
…On Jan 25, 2018 2:54 PM, "Christopher Tubbs" ***@***.***> wrote:
@kpm1985 <https://github.com/kpm1985> I think the issue needs to be
reproduced. It may or may not affect only Macs. From the discussion above,
we know it affects @cjmctague <https://github.com/cjmctague> 's Mac
builds, at the very least. If it can be reproduced, we'd need to track down
the cause of the problem. If you can help with reproducing and figuring out
why it's happening, please feel free to do so.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#971 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Acg-LLamxOgFD2EmGSFR4nyE6xgLDb2jks5tOQYNgaJpZM4QjoYx>
.
|
Setting the secret here is messing up the config for the rest of the IT's in my environment. The secret should return to the default after this test is done. Where is the default for this property being set? |
I think this test needs to completely clear zookeeper after it runs. I can look into doing that. |
Is it using its own ZK, or the one from the accumulo-maven-plugin? If the latter, best not to completely clear it. |
I'm trying to vote in the parent-pom release and I can't get
mvn verify
to run properly even before checking it against the new parent-pomIt appears to be a bug with accessing zookeeper as all the IT's error out with
I've tried to rebuild the project but it did not help. I'm sure it's something wrong with my project as @keith-turner and @ctubbsii have been able to successfully test it recently but I can't figure out the problem.
Note this error came before trying to test the new Parent-pom.
The text was updated successfully, but these errors were encountered: