> On Sep 19, 2017, at 6:35 AM, Brahma Reddy Battula
> wrote:
>
> qbt is failing from two days with following errors, any idea on this..?
Nothing to be too concerned about.
This is what it looks like when a build server gets bounced or crashed.
INFRA team knows our jobs take
qbt is failing from two days with following errors, any idea on this..?
cd
/testptch/hadoop/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
/opt/maven/bin/mvn
-Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-full-1 -Ptest-patch
-Pparallel-tests -Pshel
Thanks for the pointers, Sean! According to the infrastructure team,
apparently it was a typo in the protection scheme that allowed the trunk force
push to go through.
https://issues.apache.org/jira/browse/INFRA-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focu
disallowing force pushes to trunk was done back in:
* August 2014: INFRA-8195
* February 2016: INFRA-11136
On Mon, Apr 17, 2017 at 11:18 AM, Jason Lowe
wrote:
> I found at least one commit that was dropped, MAPREDUCE-6673. I was able to
> cherry-pick the original commit hash since it was recor
I found at least one commit that was dropped, MAPREDUCE-6673. I was able to
cherry-pick the original commit hash since it was recorded in the commit email.
This begs the question of why we're allowing force pushes to trunk. I thought
we asked to have that disabled the last time trunk was accide
Hi
I had the Apr-14 eve version of trunk on my local machine. I've pushed that.
Don't know if anything was committed over the weekend though.
Cheers
-Arun
On Mon, Apr 17, 2017 at 7:17 AM, Anu Engineer
wrote:
> Hi Allen,
>
> https://issues.apache.org/jira/browse/INFRA-13902
>
> That happened wi
Hi Allen,
https://issues.apache.org/jira/browse/INFRA-13902
That happened with ozone branch too. It was an inadvertent force push. Infra
has advised us to force push the latest branch if you have it.
Thanks
Anu
On 4/17/17, 7:10 AM, "Allen Wittenauer" wrote:
>Looks like someone reset HEAD b
Looks like someone reset HEAD back to Mar 31.
Sent from my iPad
> On Apr 16, 2017, at 12:08 AM, Apache Jenkins Server
> wrote:
>
> For more details, see
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/378/
>
>
>
>
>
> -1 overall
>
>
> The following subsystems voted -1
> On Sep 13, 2016, at 7:31 AM, Apache Jenkins Server
> wrote:
>
> For more details, see
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/163/
>
> unit:
>
>
>
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/163/artifact/out/patch-unit-hadoop-mapreduc
> On Aug 26, 2016, at 7:55 AM, Apache Jenkins Server
> wrote:
>
>
>Failed CTEST tests :
>
> test_test_libhdfs_threaded_hdfs_static
> test_test_libhdfs_zerocopy_hdfs_static
Something here likely broke these tests:
[Aug 24, 2016 7:47:52 AM] (aajisaka) HADOOP-13538. Deprecat
Infra's going to start trying out the puppet stuff on H2 in about an
hour to get a better idea of what might break when the full roll out
happens. If anyone notices something amiss, just give me a ping (or
try to update labels to use "yahoo-not-h2" instead of "Hadoop")
On Thu, Jul 21, 2016 at 6:49
Okay, I have something hacked together as of this build:
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/109
It's terrible, but it will get us through when infra uses puppet
across the H* hosts. I can fix it again after that. (the puppet use
might also break all the precommit jobs,
Failing jenkins job
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/
-Akira
On 7/21/16 14:43, Sean Busbey wrote:
they've been puppetizing the Y! hosted machines, so it's probably
related. Can someone point me to the exact jenkins job? I htink I
fixed this for HBase once already.
they've been puppetizing the Y! hosted machines, so it's probably
related. Can someone point me to the exact jenkins job? I htink I
fixed this for HBase once already.
On Thu, Jul 21, 2016 at 3:31 PM, Allen Wittenauer
wrote:
>
> I've already asked on builds and infra if it was related to some othe
I've already asked on builds and infra if it was related to some other changes
they made. As usual, radio silence.
On the flip side, the PPC machines are making builds and in many ways might be
more valuable. e.g., pointing out that the leveldb changes in YARN have pretty
much completely b
Hi folks,
qbt for trunk+JDK8 on Linux/x86 is failing by
executable '/home/jenkins/tools/maven/latest3//bin/mvn' for 'maven' does
not exist.
Would someone fix this?
Regards,
Akira
On 7/21/16 00:41, Apache Jenkins Server wrote:
For more details, see
https://builds.apache.org/job/hadoop-qbt-
Thanks Allen for reporting.
Agreed that HDFS-10256 broke the tests. Filed HDFS-10561.
Regards,
Akira
On 6/19/16 03:54, Allen Wittenauer wrote:
On Jun 17, 2016, at 7:04 AM, Apache Jenkins Server
wrote:
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/6
> On Jun 17, 2016, at 7:04 AM, Apache Jenkins Server
> wrote:
>
> For more details, see
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/66/
>
I suspect this change:
> [Jun 16, 2016 11:17:06 AM] (vinayakumarb) HDFS-10256. Use
> GenericTestUtils.getTestDir method i
Interestingly, that FindBugs warning in hadoop-azure-datalake was not
flagged during pre-commit before I committed HADOOP-12666. I'm going to
propose that we address it in scope of HADOOP-12875.
--Chris Nauroth
On 6/10/16, 10:30 AM, "Apache Jenkins Server"
wrote:
>For more details, see
>htt
19 matches
Mail list logo
