I am looking now into the issue, looks like it is looking for an AMI image that is no longer there to spawn the slaves, will try to see what is going on.
Thanks Szehon On Tue, Jul 7, 2015 at 11:38 AM, Szehon Ho <sze...@cloudera.com> wrote: > Yea you are right, somehow the server is not running the tests, hence no > logs. I will try to look at this today when I get a chance. > > Sergio can you also take a look if you have cycles? > > Thanks > Szehon > > On Tue, Jul 7, 2015 at 11:09 AM, Sergey Shelukhin <ser...@hortonworks.com> > wrote: > >> It looks like it’s downloading test logs from e.g. >> >> http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK >> -Build-4510 >> <http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-4510> >> >> but there are no logs there. It also appears to happen pretty fast, so >> testTailLog does nothing? It either returns prematurely or fails quickly >> w/o logs. >> >> On 15/7/6, 19:03, "Sergey Shelukhin" <ser...@hortonworks.com> wrote: >> >> >Looks like last HiveQA failed again in the same way, not sure if it was >> >before or after restart, what time zone is it in? >> >May that be related to recent Apache infra build changes? >> > >> >On 15/7/6, 17:24, "Szehon Ho" <sze...@cloudera.com> wrote: >> > >> >>I am not sure what is going on. Let me restart the Ptest server. >> >> >> >>On Mon, Jul 6, 2015 at 1:02 PM, Sergey Shelukhin < >> ser...@hortonworks.com> >> >>wrote: >> >> >> >>> Looks like all the runs are failing with: >> >>> >> >>> Exception in thread "main" java.lang.RuntimeException: 404 Not Found >> >>> at >> >>> >> >> >>>org.apache.hive.ptest.api.client.PTestClient.downloadTestResults(PTestCl >> >>>i >> >>>en >> >>> t.java:181) >> >>> at >> >>> >> >> >>>org.apache.hive.ptest.api.client.PTestClient.testStart(PTestClient.java: >> >>>1 >> >>>29 >> >>> ) >> >>> at >> >>> >> org.apache.hive.ptest.api.client.PTestClient.main(PTestClient.java:312) >> >>> + ret=1 >> >>> + cd target/ >> >>> + [[ -f test-results.tar.gz ]] >> >>> + exit 1 >> >>> + rm -f /tmp/tmp.FayzMqy1oP >> >>> Build step 'Execute shell' marked build as failure >> >>> Archiving artifacts >> >>> Recording test results >> >>> Finished: FAILURE >> >>> >> >>> >> >>> >> > >> >> >