Hello,
Currently we run 3 actions on every PR/update. I'm including sample
runtimes from the most recent PR:
https://github.com/apache/lucene/pull/478
* gradle check -x test: 8 minutes, 15 seconds
* gradle test: 9 minutes, 8 seconds
* lift: 84 minutes
First question: should we combine the first two actions into a simple
"gradle check"?
We are doing some redundant work in both builds:
* ~ 40 second setup time
* 59.79 sec. compileJava
* 42.04 sec. compileTestJava
Second question: what is "lift"? It seems to take an eternity, almost
an hour and a half. Do we need this?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Currently we run 3 actions on every PR/update. I'm including sample
runtimes from the most recent PR:
https://github.com/apache/lucene/pull/478
* gradle check -x test: 8 minutes, 15 seconds
* gradle test: 9 minutes, 8 seconds
* lift: 84 minutes
First question: should we combine the first two actions into a simple
"gradle check"?
We are doing some redundant work in both builds:
* ~ 40 second setup time
* 59.79 sec. compileJava
* 42.04 sec. compileTestJava
Second question: what is "lift"? It seems to take an eternity, almost
an hour and a half. Do we need this?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org