ctubbsii opened a new issue #1841:
URL: https://github.com/apache/accumulo/issues/1841
**Test name(s)**
- ConcurrentDeleteTableIT.testConcurrentDeleteTablesOps took 587 seconds
(nearly 10 minutes)
- ConcurrentDeleteTableIT.testConcurrentFateOpsWithDelete took 1,152
seconds (nearly 20 minutes)
**Describe the failure observed**
These tests take *WAY* too long to run. There has to be a better way to get
the coverage needed from these tests.
**Testing Environment:**
- Version of this project: 2.1.0-SNAPSHOT
- First commit known to fail (or current commit):
243e5771b03281c64115a625da83a20cd586adde
```
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home/christopher/apps/maven/current
Java version: 11.0.9.1, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-11-openjdk-11.0.9.11-4.fc32.x86_64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.9.13-100.fc32.x86_64", arch: "amd64", family:
"unix"
```
**What have you tried already?**
```
mvn clean verify -Dtest=nosuchtest -Dit.test=ConcurrentDeleteTableIT
-PskipQA -DskipTests=false -DskipITs=false
```
**Additional context**
On a Jenkins instance I run, I've seen these tests time out after 10 minutes
before retrying them. I'm not sure why, though, because the test doesn't have a
timeout configured. It's possible Jenkins does, though. If that's the case,
it'd be weird that it wouldn't fail more often if one test takes 20 minutes to
pass... it would mean that sometimes it takes less than 10 minutes to pass,
which is a wide variance, even on different hardware.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
