Mike,
I had that failure as well when running mvn verify. But when I ran the
IT test by itself it completed successfully. I had several IT tests fail
(different ones each run) during the 'mvn verify' runs, but when run in
isolation they succeeded.
The exception to that was the
KerberosRenewalIT.testReadAndWriteThroughTicketLifetime test. On my
local system I could only get that one to succeed if I adjusted the
TIME_DURATION value slightly. I think from 9 minutes to 11 in my
particular case. Did you have any issues with that particular test?
mark
------ Original Message ------
From: "Mike Miller" <michaelpmil...@gmail.com>
To: dev@accumulo.apache.org
Sent: 2/26/2018 4:56:24 PM
Subject: Re: [TEST][VOTE] Accumulo 1.7.4-rc0
Results from "mvn clean verify" on my MAC work machine:
[ERROR] Failures:
[ERROR] TabletStateChangeIteratorIT.test:100 No tables should need
attention expected:<0> but was:<1>
[ERROR] Errors:
[ERROR] NamespacesIT>AccumuloClusterIT.teardownCluster:223 »
TestTimedOut
test timed o...
[ERROR] ChaoticBalancerIT.test:80->Object.wait:502->Object.wait:-2 »
TestTimedOut test...
[ERROR] KerberosRenewalIT.testReadAndWriteThroughTicketLifetime »
TestTimedOut test ti...
I believe the ones that timed out are known to be finicky but I haven't
seen that failure before.
On Mon, Feb 26, 2018 at 1:56 PM, Keith Turner <ke...@deenlo.com> wrote:
I found the following while running continuous ingest test. I can fix
this, unless someone else wants to try.
https://issues.apache.org/jira/browse/ACCUMULO-4832
On Wed, Feb 21, 2018 at 6:10 PM, Christopher <ctubb...@apache.org>
wrote:
> Accumulo Developers,
>
> The following is a **TEST** release candidate (no need to vote) for
> Accumulo 1.7.4.
> As recently discussed, it's time for a 1.7.4 release. This candidate
> represents my test of the build system as it currently exists.
Please use
> these artifacts to do any relevant testing.
>
> If there's no activity in the next few days, I'll create an rc1 to
vote
on.
> I'm also willing to pass off to another release manager if somebody
feels
> strongly about taking on that task, but I've got my dev environment
set
up
> for it, so I don't mind.
>
> Git Commit:
> dbeca4335c850750ef90c2086c19527c7d73e729
> Branch:
> 1.7.4-rc0
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4
> dbeca4335c850750ef90c2086c19527c7d73e729
>
> Staging repo:
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1066
> Source (official release artifact):
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1066/org/apache/accumulo/accumulo/1.7.
4/accumulo-1.7.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1066/org/apache/accumulo/accumulo/1.7.
4/accumulo-1.7.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at
https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>
> Release notes (in progress) can be found at:
> https://github.com/apache/accumulo-website/pull/58
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote
against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.7.4 release of Apache Accumulo.
>
> This vote will remain open until at least Sat Feb 24 23:30:00 UTC
2018
> (Sat Feb 24 18:30:00 EST 2018 / Sat Feb 24 15:30:00 PST 2018).
> Voting continues until the release manager sends an email closing
the
vote.
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1066/
> # note the trailing slash is needed
