Hi All
Any update on 2.7.4 ..? Gentle Remainder!! Let me know anything I can help on
this..
Regards
Brahma Reddy Battula
-Original Message-
From: Andrew Wang [mailto:andrew.w...@cloudera.com]
Sent: 08 March 2017 04:22
To: Sangjin Lee
Cc: Marton Elek; Hadoop Common; yarn-...@hadoop.a
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
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/291/
No changes
-1 overall
The following subsystems voted -1:
compile unit
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc javac
The following subsystems are con
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
