It doesn't appear to have fixed the issue, since the latest run still
only has 4372 tests run. Should we revert our repo switch since
datanucleus appears to be back now?
Are we holding off on checkins until we get this resolved?
Alan.
Brock Noland mailto:br...@cloudera.com
October 12, 2014
Yes, let's revert the change to see if that helps. We will update the ptest
slaves to use a newer version of maven (
https://issues.apache.org/jira/browse/HIVE-8441) but it's a bit of a pain
since we have to create a new AMI. Thus reverting the change makes sense.
On Mon, Oct 13, 2014 at 8:55 AM,
Alright, I've reverted HIVE-8403 in both trunk and branch 0.14 (HIVE-8442).
Alan.
Brock Noland mailto:br...@cloudera.com
October 13, 2014 at 9:06
Yes, let's revert the change to see if that helps. We will update the
ptest
slaves to use a newer version of maven (
Thanks, I removed the maven cache directory to be safe.
On Mon, Oct 13, 2014 at 10:03 AM, Alan Gates ga...@hortonworks.com wrote:
Alright, I've reverted HIVE-8403 in both trunk and branch 0.14 (HIVE-8442).
Alan.
Brock Noland br...@cloudera.com
October 13, 2014 at 9:06
Yes, let's revert
The way this is supposed to work is that after applying the patch we run
mvn test on a dummy test to download all deps required for tests to the
maven directory. Then we rsync that maven repo directory to all the slaves.
This allows the mvn test commands to run in offline mode, which is faster.
I think this was caused by our change in repos and
http://jira.codehaus.org/browse/MNG-5181
more details:
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
I moved the maven directory which will, fix it, I think...
On Sun, Oct 12, 2014 at 4:15 PM, Brock
The tests are also taking longer to complete - around 2 hr 50 mins, it
used by around 1hr 30 mins earlier. I wonder if the fewer test being
reported and longer duration are related (some kind of timeout ?)
On Fri, Oct 10, 2014 at 1:05 PM, David Schorow dscho...@hortonworks.com wrote:
Build
I dug a little bit into the logs, and it seems some kind of build error so
these tests listed above are not running:
[ERROR] Plugin org.antlr:antlr3-maven-plugin:3.4 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.antlr:antlr3-maven-plugin:jar:3.4: The
Does anyone know why our test count has dropped recently from 6k to 4k?
This shows the trend:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/
And this is the first one with 4k tests:
I see vector and some other tests have stopped running now. Couldn't find
any reason from a quick glance.
Thanks
Szehon
On Fri, Oct 10, 2014 at 10:30 AM, Gunther Hagleitner
gunther.hagleit...@gmail.com wrote:
Does anyone know why our test count has dropped recently from 6k to 4k?
This
Build #1188 had 6765 tests, #1189 had 4354 tests. The following
packages were not run in 1189. I don't know why.
Package
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1188/testReport/
Total
11 matches
Mail list logo
