Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1697/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1694/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1649/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1648/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1647/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1646/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1645/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1644/console

Re: Still Failing: HBase Generate Website

[Peter Somogyi]

Thanks for checking on this William!
Stack and I are working on this issue on HBASE-2, it is caused by the 
protobuf upgrade in hbase-thirdparty. 

Peter

On 2019/04/12 20:42:56, William Shen  wrote: 
> Sorry, one step behind in my inbox. Seems like discussion is ongoing in
> https://issues.apache.org/jira/browse/HBASE-2
> 
> On Fri, Apr 12, 2019 at 1:40 PM William Shen 
> wrote:
> 
> > Is this something to be concerned about, or is someone looking into this?
> >
> > On Fri, Apr 12, 2019 at 7:48 AM Apache Jenkins Server <
> > jenk...@builds.apache.org> wrote:
> >
> >> Build status: Still Failing
> >>
> >> The HBase website has not been updated to incorporate HBase commit
> >> ${CURRENT_HBASE_COMMIT}.
> >>
> >> See https://builds.apache.org/job/hbase_generate_website/1643/console
> >
> >
> 

Re: Still Failing: HBase Generate Website

[William Shen]

Sorry, one step behind in my inbox. Seems like discussion is ongoing in
https://issues.apache.org/jira/browse/HBASE-2

On Fri, Apr 12, 2019 at 1:40 PM William Shen 
wrote:

> Is this something to be concerned about, or is someone looking into this?
>
> On Fri, Apr 12, 2019 at 7:48 AM Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
>> Build status: Still Failing
>>
>> The HBase website has not been updated to incorporate HBase commit
>> ${CURRENT_HBASE_COMMIT}.
>>
>> See https://builds.apache.org/job/hbase_generate_website/1643/console
>
>

Re: Still Failing: HBase Generate Website

[William Shen]

Is this something to be concerned about, or is someone looking into this?

On Fri, Apr 12, 2019 at 7:48 AM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1643/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1643/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1642/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1440/console

Re: Still Failing: HBase Generate Website

[Duo Zhang]

There is only one node under the label git-websites and it is offline. I
tried adding the ubuntu label but seems the machine can not be used for
generating web site. It will fail with

Publishing changes to remote repo...
> fatal: could not read Username for 'https://git-wip-us.apache.org': No such 
> device or address
> Failed to push to asf-site. Website not updated.
> Build step 'Execute shell' marked build as failure
>
>
Let me file an infra issue.

2018-07-20 8:07 GMT+08:00 Apache Jenkins Server :

> Build status: Still Failing
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1403/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1403/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1275/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1274/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1273/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1272/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1271/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1270/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1269/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1268/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1267/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1266/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1265/console

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

Thanks. I'll take a look when I can but it may be tomorrow.

On Feb 24, 2018 8:54 AM, "Sean Busbey"  wrote:

> triaged in HBASE-20070
>
> On Sat, Feb 24, 2018 at 10:00 AM, Sean Busbey  wrote:
> > I'll open a jira for this later today. It's been failing for several days
> > now, I think something changed in the git version on the build hosts.
> >
> > On Feb 24, 2018 08:44, "Apache Jenkins Server" <
> jenk...@builds.apache.org>
> > wrote:
> >>
> >> Build status: Still Failing
> >>
> >> The HBase website has not been updated to incorporate HBase commit
> >> ${CURRENT_HBASE_COMMIT}.
> >>
> >> See https://builds.apache.org/job/hbase_generate_website/1264/console
>

Re: Still Failing: HBase Generate Website

[Sean Busbey]

triaged in HBASE-20070

On Sat, Feb 24, 2018 at 10:00 AM, Sean Busbey  wrote:
> I'll open a jira for this later today. It's been failing for several days
> now, I think something changed in the git version on the build hosts.
>
> On Feb 24, 2018 08:44, "Apache Jenkins Server" 
> wrote:
>>
>> Build status: Still Failing
>>
>> The HBase website has not been updated to incorporate HBase commit
>> ${CURRENT_HBASE_COMMIT}.
>>
>> See https://builds.apache.org/job/hbase_generate_website/1264/console

Re: Still Failing: HBase Generate Website

[Sean Busbey]

I'll open a jira for this later today. It's been failing for several days
now, I think something changed in the git version on the build hosts.

On Feb 24, 2018 08:44, "Apache Jenkins Server" 
wrote:

> Build status: Still Failing
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1264/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1264/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1263/console

Re: Still Failing: HBase Generate Website

[Stack]

On Thu, Aug 10, 2017 at 3:40 PM, Misty Stanley-Jones 
wrote:

> The patch has now been merged and the Jenkins jobs have been converted to
> use the scripts from version control. The website-generation script has
> successfully run and the link checker script is currently running and looks
> like it will be fine. Thanks for the quick turnaround on reviews!
>
> Sweet.
S



> On Wed, Aug 9, 2017 at 2:39 PM, Misty Stanley-Jones 
> wrote:
>
> > https://issues.apache.org/jira/browse/HBASE-18548 Patch attached and
> > ready for review. Thanks, y'all!
> >
> > On Wed, Aug 9, 2017 at 1:22 PM, Misty Stanley-Jones 
> > wrote:
> >
> >> I got this.
> >>
> >> On Wed, Aug 9, 2017 at 12:17 PM, Sean Busbey  wrote:
> >>
> >>> could someone file a JIRA to get the website update job into source
> >>> control? it should be pretty straight forward; even if just the shell
> >>> script goes into dev-support it would make this a lot easier to
> >>> maintain over time. I'm happy to do the implementation, I'm just
> >>> likely to forget about it when I end up with the time.
> >>>
> >>> On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
> >>> > I pushed a fix on HBASE-18545 that should take care of it.
> >>> >
> >>> > I repro'd the issue by running commands found in the jenkins config.
> >>> >
> >>> > HBASE-18545 is the issue. Building rsgroups, it couldn't find protos
> >>> files
> >>> > it depends on that are over in hbase-protocol.
> >>> >
> >>> > S
> >>> >
> >>> >
> >>> > On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
> >>> >
> >>> >> I tried to look at this failure on Jenkins, but couldn't make sense
> >>> of it
> >>> >> -- there's barely any information there. Does anybody else have
> >>> experience
> >>> >> with this job?
> >>> >>
> >>> >> Mike
> >>> >>
> >>> >> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
> >>> >> jenk...@builds.apache.org> wrote:
> >>> >>
> >>> >> > Build status: Still Failing
> >>> >> >
> >>> >> > The HBase website has not been updated to incorporate HBase commit
> >>> >> > ${HBASE_GIT_SHA}.
> >>> >> >
> >>> >> > See https://builds.apache.org/job/hbase_generate_website/1075/co
> >>> nsole
> >>> >>
> >>>
> >>
> >>
> >
>

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

The patch has now been merged and the Jenkins jobs have been converted to
use the scripts from version control. The website-generation script has
successfully run and the link checker script is currently running and looks
like it will be fine. Thanks for the quick turnaround on reviews!

On Wed, Aug 9, 2017 at 2:39 PM, Misty Stanley-Jones 
wrote:

> https://issues.apache.org/jira/browse/HBASE-18548 Patch attached and
> ready for review. Thanks, y'all!
>
> On Wed, Aug 9, 2017 at 1:22 PM, Misty Stanley-Jones 
> wrote:
>
>> I got this.
>>
>> On Wed, Aug 9, 2017 at 12:17 PM, Sean Busbey  wrote:
>>
>>> could someone file a JIRA to get the website update job into source
>>> control? it should be pretty straight forward; even if just the shell
>>> script goes into dev-support it would make this a lot easier to
>>> maintain over time. I'm happy to do the implementation, I'm just
>>> likely to forget about it when I end up with the time.
>>>
>>> On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
>>> > I pushed a fix on HBASE-18545 that should take care of it.
>>> >
>>> > I repro'd the issue by running commands found in the jenkins config.
>>> >
>>> > HBASE-18545 is the issue. Building rsgroups, it couldn't find protos
>>> files
>>> > it depends on that are over in hbase-protocol.
>>> >
>>> > S
>>> >
>>> >
>>> > On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
>>> >
>>> >> I tried to look at this failure on Jenkins, but couldn't make sense
>>> of it
>>> >> -- there's barely any information there. Does anybody else have
>>> experience
>>> >> with this job?
>>> >>
>>> >> Mike
>>> >>
>>> >> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
>>> >> jenk...@builds.apache.org> wrote:
>>> >>
>>> >> > Build status: Still Failing
>>> >> >
>>> >> > The HBase website has not been updated to incorporate HBase commit
>>> >> > ${HBASE_GIT_SHA}.
>>> >> >
>>> >> > See https://builds.apache.org/job/hbase_generate_website/1075/co
>>> nsole
>>> >>
>>>
>>
>>
>

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

https://issues.apache.org/jira/browse/HBASE-18548 Patch attached and ready
for review. Thanks, y'all!

On Wed, Aug 9, 2017 at 1:22 PM, Misty Stanley-Jones 
wrote:

> I got this.
>
> On Wed, Aug 9, 2017 at 12:17 PM, Sean Busbey  wrote:
>
>> could someone file a JIRA to get the website update job into source
>> control? it should be pretty straight forward; even if just the shell
>> script goes into dev-support it would make this a lot easier to
>> maintain over time. I'm happy to do the implementation, I'm just
>> likely to forget about it when I end up with the time.
>>
>> On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
>> > I pushed a fix on HBASE-18545 that should take care of it.
>> >
>> > I repro'd the issue by running commands found in the jenkins config.
>> >
>> > HBASE-18545 is the issue. Building rsgroups, it couldn't find protos
>> files
>> > it depends on that are over in hbase-protocol.
>> >
>> > S
>> >
>> >
>> > On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
>> >
>> >> I tried to look at this failure on Jenkins, but couldn't make sense of
>> it
>> >> -- there's barely any information there. Does anybody else have
>> experience
>> >> with this job?
>> >>
>> >> Mike
>> >>
>> >> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
>> >> jenk...@builds.apache.org> wrote:
>> >>
>> >> > Build status: Still Failing
>> >> >
>> >> > The HBase website has not been updated to incorporate HBase commit
>> >> > ${HBASE_GIT_SHA}.
>> >> >
>> >> > See https://builds.apache.org/job/hbase_generate_website/1075/co
>> nsole
>> >>
>>
>
>

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

I got this.

On Wed, Aug 9, 2017 at 12:17 PM, Sean Busbey  wrote:

> could someone file a JIRA to get the website update job into source
> control? it should be pretty straight forward; even if just the shell
> script goes into dev-support it would make this a lot easier to
> maintain over time. I'm happy to do the implementation, I'm just
> likely to forget about it when I end up with the time.
>
> On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
> > I pushed a fix on HBASE-18545 that should take care of it.
> >
> > I repro'd the issue by running commands found in the jenkins config.
> >
> > HBASE-18545 is the issue. Building rsgroups, it couldn't find protos
> files
> > it depends on that are over in hbase-protocol.
> >
> > S
> >
> >
> > On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
> >
> >> I tried to look at this failure on Jenkins, but couldn't make sense of
> it
> >> -- there's barely any information there. Does anybody else have
> experience
> >> with this job?
> >>
> >> Mike
> >>
> >> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
> >> jenk...@builds.apache.org> wrote:
> >>
> >> > Build status: Still Failing
> >> >
> >> > The HBase website has not been updated to incorporate HBase commit
> >> > ${HBASE_GIT_SHA}.
> >> >
> >> > See https://builds.apache.org/job/hbase_generate_website/1075/console
> >>
>

Re: Still Failing: HBase Generate Website

[Sean Busbey]

could someone file a JIRA to get the website update job into source
control? it should be pretty straight forward; even if just the shell
script goes into dev-support it would make this a lot easier to
maintain over time. I'm happy to do the implementation, I'm just
likely to forget about it when I end up with the time.

On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
> I pushed a fix on HBASE-18545 that should take care of it.
>
> I repro'd the issue by running commands found in the jenkins config.
>
> HBASE-18545 is the issue. Building rsgroups, it couldn't find protos files
> it depends on that are over in hbase-protocol.
>
> S
>
>
> On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
>
>> I tried to look at this failure on Jenkins, but couldn't make sense of it
>> -- there's barely any information there. Does anybody else have experience
>> with this job?
>>
>> Mike
>>
>> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
>>
>> > Build status: Still Failing
>> >
>> > The HBase website has not been updated to incorporate HBase commit
>> > ${HBASE_GIT_SHA}.
>> >
>> > See https://builds.apache.org/job/hbase_generate_website/1075/console
>>

Re: Still Failing: HBase Generate Website

[Stack]

I pushed a fix on HBASE-18545 that should take care of it.

I repro'd the issue by running commands found in the jenkins config.

HBASE-18545 is the issue. Building rsgroups, it couldn't find protos files
it depends on that are over in hbase-protocol.

S


On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:

> I tried to look at this failure on Jenkins, but couldn't make sense of it
> -- there's barely any information there. Does anybody else have experience
> with this job?
>
> Mike
>
> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Still Failing
> >
> > The HBase website has not been updated to incorporate HBase commit
> > ${HBASE_GIT_SHA}.
> >
> > See https://builds.apache.org/job/hbase_generate_website/1075/console
>

Re: Still Failing: HBase Generate Website

[Ted Yu]

Have you looked at the following ?

https://builds.apache.org/job/hbase_generate_website/1072/artifact/hbase-install-log-82d554e3783372cc6b05489452c815b57c06f6cd.txt

Cheers

On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:

> I tried to look at this failure on Jenkins, but couldn't make sense of it
> -- there's barely any information there. Does anybody else have experience
> with this job?
>
> Mike
>
> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Still Failing
> >
> > The HBase website has not been updated to incorporate HBase commit
> > ${HBASE_GIT_SHA}.
> >
> > See https://builds.apache.org/job/hbase_generate_website/1075/console
>

Re: Still Failing: HBase Generate Website

[Mike Drob]

I tried to look at this failure on Jenkins, but couldn't make sense of it
-- there's barely any information there. Does anybody else have experience
with this job?

Mike

On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> The HBase website has not been updated to incorporate HBase commit
> ${HBASE_GIT_SHA}.
>
> See https://builds.apache.org/job/hbase_generate_website/1075/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1075/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1074/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1073/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1046/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/956/console

Re: Still Failing: HBase Generate Website

[Sean Busbey]

patch is up on:

https://issues.apache.org/jira/browse/HBASE-17192

On Tue, Nov 29, 2016 at 3:37 AM, Sean Busbey  wrote:
> I have figured out the problem. jira in a few.
>
> On Tue, Nov 29, 2016 at 3:23 AM, Sean Busbey  wrote:
>> git bisect led me to the commit immediately after our last known good
>> job. Reverting that commit didn't fix things. Attempting a new build
>> from the same commit used in our last known good job also failed with
>> the current error.
>>
>> I'm checking on some other leads and will follow up tomorrow.
>>
>> On Mon, Nov 28, 2016 at 4:03 PM, Sean Busbey  wrote:
>>> no idea. it's not often I see new cryptic maven errors. :/
>>>
>>> anyone have time to do a git bisect? about a week of changes shouldn't
>>> take too long.
>>>
>>> On Mon, Nov 28, 2016 at 10:01 AM, Dima Spivak  wrote:
 Anyone know what's up here? I don't see any obvious breaking changes, but
 mvn site fails in parent module with:

 
 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
 project hbase: Execution default-site of goal
 org.apache.maven.plugins:maven-site-plugin:3.4:site failed: For artifact
 {null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
 [ERROR]

 On Mon, Nov 28, 2016 at 6:34 AM Apache Jenkins Server <
 jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O-
> https://builds.apache.org/job/hbase_generate_website/419/artifact/website.patch.zip
> | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/419/console
>>>
>>>
>>>
>>> --
>>> busbey

Re: Still Failing: HBase Generate Website

[Sean Busbey]

I have figured out the problem. jira in a few.

On Tue, Nov 29, 2016 at 3:23 AM, Sean Busbey  wrote:
> git bisect led me to the commit immediately after our last known good
> job. Reverting that commit didn't fix things. Attempting a new build
> from the same commit used in our last known good job also failed with
> the current error.
>
> I'm checking on some other leads and will follow up tomorrow.
>
> On Mon, Nov 28, 2016 at 4:03 PM, Sean Busbey  wrote:
>> no idea. it's not often I see new cryptic maven errors. :/
>>
>> anyone have time to do a git bisect? about a week of changes shouldn't
>> take too long.
>>
>> On Mon, Nov 28, 2016 at 10:01 AM, Dima Spivak  wrote:
>>> Anyone know what's up here? I don't see any obvious breaking changes, but
>>> mvn site fails in parent module with:
>>>
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
>>> project hbase: Execution default-site of goal
>>> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: For artifact
>>> {null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
>>> [ERROR]
>>>
>>> On Mon, Nov 28, 2016 at 6:34 AM Apache Jenkins Server <
>>> jenk...@builds.apache.org> wrote:
>>>
 Build status: Still Failing

 If successful, the website and docs have been generated. To update the
 live site, follow the instructions below. If failed, skip to the bottom of
 this email.

 Use the following commands to download the patch and apply it to a clean
 branch based on origin/asf-site. If you prefer to keep the hbase-site repo
 around permanently, you can skip the clone step.

   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

   cd hbase-site
   wget -O-
 https://builds.apache.org/job/hbase_generate_website/419/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
   git fetch
   git checkout -b asf-site-${GIT_SHA} origin/asf-site
   git am --whitespace=fix $GIT_SHA.patch

 At this point, you can preview the changes by opening index.html or any of
 the other HTML pages in your local asf-site-${GIT_SHA} branch.

 There are lots of spurious changes, such as timestamps and CSS styles in
 tables, so a generic git diff is not very useful. To see a list of files
 that have been added, deleted, renamed, changed type, or are otherwise
 interesting, use the following command:

   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

 To see only files that had 100 or more lines changed:

   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

 When you are satisfied, publish your changes to origin/asf-site using
 these commands:

   git commit --allow-empty -m "Empty commit" # to work around a current
 ASF INFRA bug
   git push origin asf-site-${GIT_SHA}:asf-site
   git checkout asf-site
   git branch -D asf-site-${GIT_SHA}

 Changes take a couple of minutes to be propagated. You can verify whether
 they have been propagated by looking at the Last Published date at the
 bottom of http://hbase.apache.org/. It should match the date in the
 index.html on the asf-site branch in Git.

 As a courtesy- reply-all to this email to let other committers know you
 pushed the site.



 If failed, see
 https://builds.apache.org/job/hbase_generate_website/419/console
>>
>>
>>
>> --
>> busbey

Re: Still Failing: HBase Generate Website

[Sean Busbey]

git bisect led me to the commit immediately after our last known good
job. Reverting that commit didn't fix things. Attempting a new build
from the same commit used in our last known good job also failed with
the current error.

I'm checking on some other leads and will follow up tomorrow.

On Mon, Nov 28, 2016 at 4:03 PM, Sean Busbey  wrote:
> no idea. it's not often I see new cryptic maven errors. :/
>
> anyone have time to do a git bisect? about a week of changes shouldn't
> take too long.
>
> On Mon, Nov 28, 2016 at 10:01 AM, Dima Spivak  wrote:
>> Anyone know what's up here? I don't see any obvious breaking changes, but
>> mvn site fails in parent module with:
>>
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
>> project hbase: Execution default-site of goal
>> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: For artifact
>> {null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
>> [ERROR]
>>
>> On Mon, Nov 28, 2016 at 6:34 AM Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
>>
>>> Build status: Still Failing
>>>
>>> If successful, the website and docs have been generated. To update the
>>> live site, follow the instructions below. If failed, skip to the bottom of
>>> this email.
>>>
>>> Use the following commands to download the patch and apply it to a clean
>>> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
>>> around permanently, you can skip the clone step.
>>>
>>>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>>>
>>>   cd hbase-site
>>>   wget -O-
>>> https://builds.apache.org/job/hbase_generate_website/419/artifact/website.patch.zip
>>> | funzip > ${GIT_SHA}.patch
>>>   git fetch
>>>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>>>   git am --whitespace=fix $GIT_SHA.patch
>>>
>>> At this point, you can preview the changes by opening index.html or any of
>>> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>>>
>>> There are lots of spurious changes, such as timestamps and CSS styles in
>>> tables, so a generic git diff is not very useful. To see a list of files
>>> that have been added, deleted, renamed, changed type, or are otherwise
>>> interesting, use the following command:
>>>
>>>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>>>
>>> To see only files that had 100 or more lines changed:
>>>
>>>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>>>
>>> When you are satisfied, publish your changes to origin/asf-site using
>>> these commands:
>>>
>>>   git commit --allow-empty -m "Empty commit" # to work around a current
>>> ASF INFRA bug
>>>   git push origin asf-site-${GIT_SHA}:asf-site
>>>   git checkout asf-site
>>>   git branch -D asf-site-${GIT_SHA}
>>>
>>> Changes take a couple of minutes to be propagated. You can verify whether
>>> they have been propagated by looking at the Last Published date at the
>>> bottom of http://hbase.apache.org/. It should match the date in the
>>> index.html on the asf-site branch in Git.
>>>
>>> As a courtesy- reply-all to this email to let other committers know you
>>> pushed the site.
>>>
>>>
>>>
>>> If failed, see
>>> https://builds.apache.org/job/hbase_generate_website/419/console
>
>
>
> --
> busbey

Re: Still Failing: HBase Generate Website

[Sean Busbey]

no idea. it's not often I see new cryptic maven errors. :/

anyone have time to do a git bisect? about a week of changes shouldn't
take too long.

On Mon, Nov 28, 2016 at 10:01 AM, Dima Spivak  wrote:
> Anyone know what's up here? I don't see any obvious breaking changes, but
> mvn site fails in parent module with:
>
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project hbase: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: For artifact
> {null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
> [ERROR]
>
> On Mon, Nov 28, 2016 at 6:34 AM Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
>> Build status: Still Failing
>>
>> If successful, the website and docs have been generated. To update the
>> live site, follow the instructions below. If failed, skip to the bottom of
>> this email.
>>
>> Use the following commands to download the patch and apply it to a clean
>> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
>> around permanently, you can skip the clone step.
>>
>>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>>
>>   cd hbase-site
>>   wget -O-
>> https://builds.apache.org/job/hbase_generate_website/419/artifact/website.patch.zip
>> | funzip > ${GIT_SHA}.patch
>>   git fetch
>>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>>   git am --whitespace=fix $GIT_SHA.patch
>>
>> At this point, you can preview the changes by opening index.html or any of
>> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>>
>> There are lots of spurious changes, such as timestamps and CSS styles in
>> tables, so a generic git diff is not very useful. To see a list of files
>> that have been added, deleted, renamed, changed type, or are otherwise
>> interesting, use the following command:
>>
>>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>>
>> To see only files that had 100 or more lines changed:
>>
>>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>>
>> When you are satisfied, publish your changes to origin/asf-site using
>> these commands:
>>
>>   git commit --allow-empty -m "Empty commit" # to work around a current
>> ASF INFRA bug
>>   git push origin asf-site-${GIT_SHA}:asf-site
>>   git checkout asf-site
>>   git branch -D asf-site-${GIT_SHA}
>>
>> Changes take a couple of minutes to be propagated. You can verify whether
>> they have been propagated by looking at the Last Published date at the
>> bottom of http://hbase.apache.org/. It should match the date in the
>> index.html on the asf-site branch in Git.
>>
>> As a courtesy- reply-all to this email to let other committers know you
>> pushed the site.
>>
>>
>>
>> If failed, see
>> https://builds.apache.org/job/hbase_generate_website/419/console



-- 
busbey

Re: Still Failing: HBase Generate Website

[Dima Spivak]

Anyone know what's up here? I don't see any obvious breaking changes, but
mvn site fails in parent module with:


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
project hbase: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: For artifact
{null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
[ERROR]

On Mon, Nov 28, 2016 at 6:34 AM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O-
> https://builds.apache.org/job/hbase_generate_website/419/artifact/website.patch.zip
> | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/419/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/419/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/419/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/418/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/418/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/417/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/417/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/416/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/416/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/415/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/415/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/414/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/414/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/413/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/413/console

Re: Still Failing: HBase Generate Website

[张铎]

You can setup a branch with that commit in I think.

Maybe we can setup a new jenkins job that only executes on H0 and H1?

2016-10-11 9:37 GMT+08:00 Ted Yu :

> Adding '-Xnative.verbose=true' can be done - but the commit has been
> reverted, not sure if the output is useful.
>
> To my knowledge, nobody has access to H0 (or any other Jenkins machines)
> other than Apache admins.
>
> On Mon, Oct 10, 2016 at 6:32 PM, 张铎  wrote:
>
> > Could the infra team give us a temporary permission to login H0 and run
> > some builds manually?
> >
> > https://github.com/jruby/jruby/issues/2913
> >
> > Here they suggest adding -Xnative.verbose=true when building to see the
> > root cause. We could also do this.
> >
> > 2016-10-11 4:24 GMT+08:00 Ted Yu :
> >
> > > For those who are not watching HBASE-16750. We had successful build
> with
> > > the following Ubuntu OS.
> > >
> > > Saravanan and I will keep working on this issue till resolution.
> > >
> > > Thanks to Dima who kept an eye on website builds.
> > >
> > > jenkins@u12-slave-4c6292b0-1:~/workspace/build-support$ uname -a
> > > Linux u12-slave-4c6292b0-1 3.2.0-74-virtual #109-Ubuntu SMP Tue Dec 9
> > > 17:04:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> > > JAVA: /grid/0/jenkins/tools/jdk7/jdk1.7.0_21
> > > Maven: /grid/0/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn
> > >
> > >
> > > On Mon, Oct 10, 2016 at 8:01 AM, Dima Spivak 
> > > wrote:
> > >
> > > > I'll revert and rerun on the same build machine. Whether the problem
> is
> > > > with the environment or not, I don't recall it ever happening before
> > this
> > > > commit and this kind of regression is unacceptable.
> > > >
> > > > On Sunday, October 9, 2016, stack  wrote:
> > > >
> > > > > Did you do the revert meantime Ted?
> > > > >
> > > > > On Oct 8, 2016 19:01, "Ted Yu"  >
> > > > wrote:
> > > > >
> > > > > > Logged INFRA-12731
> > > > > >
> > > > > > On Sat, Oct 8, 2016 at 6:56 PM, 张铎  > > > >
> > > > > wrote:
> > > > > >
> > > > > > > Build environment issue IS a issue. If we do not consider H0
> and
> > H1
> > > > as
> > > > > > > broken, we need to fix the problem.
> > > > > > >
> > > > > > > And we are not sure if all other machines are OK right? As for
> > now,
> > > > the
> > > > > > > failed machines wins, 2 vs. 1.
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > 2016-10-09 9:36 GMT+08:00 Ted Yu  > > > >:
> > > > > > >
> > > > > > > > This seems to be build environment issue.
> > > > > > > >
> > > > > > > > Build #368 (green) was on H4 while #369 was on H0. #370 was
> on
> > > H1.
> > > > > > > >
> > > > > > > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  > > > > > wrote:
> > > > > > > >
> > > > > > > > > This maybe related to a jruby issue.
> > > > > > > > >
> > > > > > > > > https://github.com/jruby/jruby/issues/2913
> > > > > > > > >
> > > > > > > > > It depends on the environment thus it may fail on some
> > machines
> > > > > while
> > > > > > > > > success on some other machines.
> > > > > > > > >
> > > > > > > > > 2016-10-09 9:29 GMT+08:00 Ted Yu  > > > > >:
> > > > > > > > >
> > > > > > > > > > This was the build 16750 went into:
> > > > > > > > > >
> > > > > > > > > > https://builds.apache.org/job/
> hbase_generate_website/368/
> > > > > > > > > >
> > > > > > > > > > which was green.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey <
> > > > bus...@cloudera.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > If the website can't build on the build machine then it
> > > can't
> > > > > > > build.
> > > > > > > > > > >
> > > > > > > > > > > We've worked hard as a community to automate this stuff
> > > and I
> > > > > > don't
> > > > > > > > > want
> > > > > > > > > > to
> > > > > > > > > > > go backwards.
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Sean Busbey
> > > > > > > > > > >
> > > > > > > > > > > On Oct 8, 2016 14:48, "Ted Yu"  > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I did a local build:
> > > > > > > > > > > >
> > > > > > > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c0
> > > > > 7478323dc5;
> > > > > > > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > > > > > > OS name: "linux", version:
> > "3.10.0-327.28.2.el7.x86_64",
> > > > > arch:
> > > > > > > > > "amd64",
> > > > > > > > > > > > family: "unix"
> > > > > > > > > > > >
> > > > > > > 

Re: Still Failing: HBase Generate Website

[Dima Spivak]

If you have a test case they can run, feel free a ticket for INFRA and they
might be able to help you out.

On Monday, October 10, 2016, Ted Yu  wrote:

> Adding '-Xnative.verbose=true' can be done - but the commit has been
> reverted, not sure if the output is useful.
>
> To my knowledge, nobody has access to H0 (or any other Jenkins machines)
> other than Apache admins.
>
> On Mon, Oct 10, 2016 at 6:32 PM, 张铎 >
> wrote:
>
> > Could the infra team give us a temporary permission to login H0 and run
> > some builds manually?
> >
> > https://github.com/jruby/jruby/issues/2913
> >
> > Here they suggest adding -Xnative.verbose=true when building to see the
> > root cause. We could also do this.
> >
> > 2016-10-11 4:24 GMT+08:00 Ted Yu >:
> >
> > > For those who are not watching HBASE-16750. We had successful build
> with
> > > the following Ubuntu OS.
> > >
> > > Saravanan and I will keep working on this issue till resolution.
> > >
> > > Thanks to Dima who kept an eye on website builds.
> > >
> > > jenkins@u12-slave-4c6292b0-1:~/workspace/build-support$ uname -a
> > > Linux u12-slave-4c6292b0-1 3.2.0-74-virtual #109-Ubuntu SMP Tue Dec 9
> > > 17:04:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> > > JAVA: /grid/0/jenkins/tools/jdk7/jdk1.7.0_21
> > > Maven: /grid/0/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn
> > >
> > >
> > > On Mon, Oct 10, 2016 at 8:01 AM, Dima Spivak  >
> > > wrote:
> > >
> > > > I'll revert and rerun on the same build machine. Whether the problem
> is
> > > > with the environment or not, I don't recall it ever happening before
> > this
> > > > commit and this kind of regression is unacceptable.
> > > >
> > > > On Sunday, October 9, 2016, stack  > wrote:
> > > >
> > > > > Did you do the revert meantime Ted?
> > > > >
> > > > > On Oct 8, 2016 19:01, "Ted Yu" 
> >
> > > > wrote:
> > > > >
> > > > > > Logged INFRA-12731
> > > > > >
> > > > > > On Sat, Oct 8, 2016 at 6:56 PM, 张铎  
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > > Build environment issue IS a issue. If we do not consider H0
> and
> > H1
> > > > as
> > > > > > > broken, we need to fix the problem.
> > > > > > >
> > > > > > > And we are not sure if all other machines are OK right? As for
> > now,
> > > > the
> > > > > > > failed machines wins, 2 vs. 1.
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > 2016-10-09 9:36 GMT+08:00 Ted Yu  
> > > > >:
> > > > > > >
> > > > > > > > This seems to be build environment issue.
> > > > > > > >
> > > > > > > > Build #368 (green) was on H4 while #369 was on H0. #370 was
> on
> > > H1.
> > > > > > > >
> > > > > > > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > This maybe related to a jruby issue.
> > > > > > > > >
> > > > > > > > > https://github.com/jruby/jruby/issues/2913
> > > > > > > > >
> > > > > > > > > It depends on the environment thus it may fail on some
> > machines
> > > > > while
> > > > > > > > > success on some other machines.
> > > > > > > > >
> > > > > > > > > 2016-10-09 9:29 GMT+08:00 Ted Yu  
> > > > > >:
> > > > > > > > >
> > > > > > > > > > This was the build 16750 went into:
> > > > > > > > > >
> > > > > > > > > > https://builds.apache.org/job/
> hbase_generate_website/368/
> > > > > > > > > >
> > > > > > > > > > which was green.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey <
> > > > bus...@cloudera.com 
> > > > > >
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > If the website can't build on the build machine then it
> > > can't
> > > > > > > build.
> > > > > > > > > > >
> > > > > > > > > > > We've worked hard as a community to automate this stuff
> > > and I
> > > > > > don't
> > > > > > > > > want
> > > > > > > > > > to
> > > > > > > > > > > go backwards.
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Sean Busbey
> > > > > > > > > > >
> > > > > > > > > > > On Oct 8, 2016 14:48, "Ted Yu"  
> > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I did a local build:
> > > > > > > > > > > >
> > > > > > > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c0
> > > > > 7478323dc5;
> > > > > > > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > > > > > > OS 

Re: Still Failing: HBase Generate Website

[Ted Yu]

Adding '-Xnative.verbose=true' can be done - but the commit has been
reverted, not sure if the output is useful.

To my knowledge, nobody has access to H0 (or any other Jenkins machines)
other than Apache admins.

On Mon, Oct 10, 2016 at 6:32 PM, 张铎  wrote:

> Could the infra team give us a temporary permission to login H0 and run
> some builds manually?
>
> https://github.com/jruby/jruby/issues/2913
>
> Here they suggest adding -Xnative.verbose=true when building to see the
> root cause. We could also do this.
>
> 2016-10-11 4:24 GMT+08:00 Ted Yu :
>
> > For those who are not watching HBASE-16750. We had successful build with
> > the following Ubuntu OS.
> >
> > Saravanan and I will keep working on this issue till resolution.
> >
> > Thanks to Dima who kept an eye on website builds.
> >
> > jenkins@u12-slave-4c6292b0-1:~/workspace/build-support$ uname -a
> > Linux u12-slave-4c6292b0-1 3.2.0-74-virtual #109-Ubuntu SMP Tue Dec 9
> > 17:04:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> > JAVA: /grid/0/jenkins/tools/jdk7/jdk1.7.0_21
> > Maven: /grid/0/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn
> >
> >
> > On Mon, Oct 10, 2016 at 8:01 AM, Dima Spivak 
> > wrote:
> >
> > > I'll revert and rerun on the same build machine. Whether the problem is
> > > with the environment or not, I don't recall it ever happening before
> this
> > > commit and this kind of regression is unacceptable.
> > >
> > > On Sunday, October 9, 2016, stack  wrote:
> > >
> > > > Did you do the revert meantime Ted?
> > > >
> > > > On Oct 8, 2016 19:01, "Ted Yu" >
> > > wrote:
> > > >
> > > > > Logged INFRA-12731
> > > > >
> > > > > On Sat, Oct 8, 2016 at 6:56 PM, 张铎  > > >
> > > > wrote:
> > > > >
> > > > > > Build environment issue IS a issue. If we do not consider H0 and
> H1
> > > as
> > > > > > broken, we need to fix the problem.
> > > > > >
> > > > > > And we are not sure if all other machines are OK right? As for
> now,
> > > the
> > > > > > failed machines wins, 2 vs. 1.
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > 2016-10-09 9:36 GMT+08:00 Ted Yu  > > >:
> > > > > >
> > > > > > > This seems to be build environment issue.
> > > > > > >
> > > > > > > Build #368 (green) was on H4 while #369 was on H0. #370 was on
> > H1.
> > > > > > >
> > > > > > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  > > > > wrote:
> > > > > > >
> > > > > > > > This maybe related to a jruby issue.
> > > > > > > >
> > > > > > > > https://github.com/jruby/jruby/issues/2913
> > > > > > > >
> > > > > > > > It depends on the environment thus it may fail on some
> machines
> > > > while
> > > > > > > > success on some other machines.
> > > > > > > >
> > > > > > > > 2016-10-09 9:29 GMT+08:00 Ted Yu  > > > >:
> > > > > > > >
> > > > > > > > > This was the build 16750 went into:
> > > > > > > > >
> > > > > > > > > https://builds.apache.org/job/hbase_generate_website/368/
> > > > > > > > >
> > > > > > > > > which was green.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey <
> > > bus...@cloudera.com
> > > > >
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > If the website can't build on the build machine then it
> > can't
> > > > > > build.
> > > > > > > > > >
> > > > > > > > > > We've worked hard as a community to automate this stuff
> > and I
> > > > > don't
> > > > > > > > want
> > > > > > > > > to
> > > > > > > > > > go backwards.
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Sean Busbey
> > > > > > > > > >
> > > > > > > > > > On Oct 8, 2016 14:48, "Ted Yu"  > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > I did a local build:
> > > > > > > > > > >
> > > > > > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c0
> > > > 7478323dc5;
> > > > > > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > > > > > OS name: "linux", version:
> "3.10.0-327.28.2.el7.x86_64",
> > > > arch:
> > > > > > > > "amd64",
> > > > > > > > > > > family: "unix"
> > > > > > > > > > >
> > > > > > > > > > > [INFO] Final Memory: 30M/1928M
> > > > > > > > > > > [INFO]
> > > > > > > > > > > --
> > > --
> > > > > > > > > 
> > > > > > > > > > > [INFO] Archetype project created in
> > > > > > > > > > > /hbase/hbase-archetypes/hbase-
> > client-project/target/build-
> > > > > > > > > > > archetype/target/generated-sources/archetype
> > > > > > > > > > > [INFO]
> > > > > > > > > > > 

Re: Still Failing: HBase Generate Website

[张铎]

Could the infra team give us a temporary permission to login H0 and run
some builds manually?

https://github.com/jruby/jruby/issues/2913

Here they suggest adding -Xnative.verbose=true when building to see the
root cause. We could also do this.

2016-10-11 4:24 GMT+08:00 Ted Yu :

> For those who are not watching HBASE-16750. We had successful build with
> the following Ubuntu OS.
>
> Saravanan and I will keep working on this issue till resolution.
>
> Thanks to Dima who kept an eye on website builds.
>
> jenkins@u12-slave-4c6292b0-1:~/workspace/build-support$ uname -a
> Linux u12-slave-4c6292b0-1 3.2.0-74-virtual #109-Ubuntu SMP Tue Dec 9
> 17:04:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> JAVA: /grid/0/jenkins/tools/jdk7/jdk1.7.0_21
> Maven: /grid/0/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn
>
>
> On Mon, Oct 10, 2016 at 8:01 AM, Dima Spivak 
> wrote:
>
> > I'll revert and rerun on the same build machine. Whether the problem is
> > with the environment or not, I don't recall it ever happening before this
> > commit and this kind of regression is unacceptable.
> >
> > On Sunday, October 9, 2016, stack  wrote:
> >
> > > Did you do the revert meantime Ted?
> > >
> > > On Oct 8, 2016 19:01, "Ted Yu" >
> > wrote:
> > >
> > > > Logged INFRA-12731
> > > >
> > > > On Sat, Oct 8, 2016 at 6:56 PM, 张铎  > >
> > > wrote:
> > > >
> > > > > Build environment issue IS a issue. If we do not consider H0 and H1
> > as
> > > > > broken, we need to fix the problem.
> > > > >
> > > > > And we are not sure if all other machines are OK right? As for now,
> > the
> > > > > failed machines wins, 2 vs. 1.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > 2016-10-09 9:36 GMT+08:00 Ted Yu  > >:
> > > > >
> > > > > > This seems to be build environment issue.
> > > > > >
> > > > > > Build #368 (green) was on H4 while #369 was on H0. #370 was on
> H1.
> > > > > >
> > > > > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  > > > wrote:
> > > > > >
> > > > > > > This maybe related to a jruby issue.
> > > > > > >
> > > > > > > https://github.com/jruby/jruby/issues/2913
> > > > > > >
> > > > > > > It depends on the environment thus it may fail on some machines
> > > while
> > > > > > > success on some other machines.
> > > > > > >
> > > > > > > 2016-10-09 9:29 GMT+08:00 Ted Yu  > > >:
> > > > > > >
> > > > > > > > This was the build 16750 went into:
> > > > > > > >
> > > > > > > > https://builds.apache.org/job/hbase_generate_website/368/
> > > > > > > >
> > > > > > > > which was green.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey <
> > bus...@cloudera.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > If the website can't build on the build machine then it
> can't
> > > > > build.
> > > > > > > > >
> > > > > > > > > We've worked hard as a community to automate this stuff
> and I
> > > > don't
> > > > > > > want
> > > > > > > > to
> > > > > > > > > go backwards.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Sean Busbey
> > > > > > > > >
> > > > > > > > > On Oct 8, 2016 14:48, "Ted Yu"  > > > wrote:
> > > > > > > > >
> > > > > > > > > > I did a local build:
> > > > > > > > > >
> > > > > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c0
> > > 7478323dc5;
> > > > > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64",
> > > arch:
> > > > > > > "amd64",
> > > > > > > > > > family: "unix"
> > > > > > > > > >
> > > > > > > > > > [INFO] Final Memory: 30M/1928M
> > > > > > > > > > [INFO]
> > > > > > > > > > --
> > --
> > > > > > > > 
> > > > > > > > > > [INFO] Archetype project created in
> > > > > > > > > > /hbase/hbase-archetypes/hbase-
> client-project/target/build-
> > > > > > > > > > archetype/target/generated-sources/archetype
> > > > > > > > > > [INFO]
> > > > > > > > > > --
> > --
> > > > > > > > 
> > > > > > > > > > [INFO] BUILD SUCCESS
> > > > > > > > > > [INFO]
> > > > > > > > > > --
> > --
> > > > > > > > 
> > > > > > > > > > [INFO] Total time: 3.168 s
> > > > > > > > > >
> > > > > > > > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > > > > > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > > > > > > > 

Re: Still Failing: HBase Generate Website

[Ted Yu]

For those who are not watching HBASE-16750. We had successful build with
the following Ubuntu OS.

Saravanan and I will keep working on this issue till resolution.

Thanks to Dima who kept an eye on website builds.

jenkins@u12-slave-4c6292b0-1:~/workspace/build-support$ uname -a
Linux u12-slave-4c6292b0-1 3.2.0-74-virtual #109-Ubuntu SMP Tue Dec 9
17:04:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
JAVA: /grid/0/jenkins/tools/jdk7/jdk1.7.0_21
Maven: /grid/0/jenkins/tools/maven/apache-maven-3.3.9/bin/mvn


On Mon, Oct 10, 2016 at 8:01 AM, Dima Spivak  wrote:

> I'll revert and rerun on the same build machine. Whether the problem is
> with the environment or not, I don't recall it ever happening before this
> commit and this kind of regression is unacceptable.
>
> On Sunday, October 9, 2016, stack  wrote:
>
> > Did you do the revert meantime Ted?
> >
> > On Oct 8, 2016 19:01, "Ted Yu" >
> wrote:
> >
> > > Logged INFRA-12731
> > >
> > > On Sat, Oct 8, 2016 at 6:56 PM, 张铎  >
> > wrote:
> > >
> > > > Build environment issue IS a issue. If we do not consider H0 and H1
> as
> > > > broken, we need to fix the problem.
> > > >
> > > > And we are not sure if all other machines are OK right? As for now,
> the
> > > > failed machines wins, 2 vs. 1.
> > > >
> > > > Thanks.
> > > >
> > > > 2016-10-09 9:36 GMT+08:00 Ted Yu  >:
> > > >
> > > > > This seems to be build environment issue.
> > > > >
> > > > > Build #368 (green) was on H4 while #369 was on H0. #370 was on H1.
> > > > >
> > > > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  > > wrote:
> > > > >
> > > > > > This maybe related to a jruby issue.
> > > > > >
> > > > > > https://github.com/jruby/jruby/issues/2913
> > > > > >
> > > > > > It depends on the environment thus it may fail on some machines
> > while
> > > > > > success on some other machines.
> > > > > >
> > > > > > 2016-10-09 9:29 GMT+08:00 Ted Yu  > >:
> > > > > >
> > > > > > > This was the build 16750 went into:
> > > > > > >
> > > > > > > https://builds.apache.org/job/hbase_generate_website/368/
> > > > > > >
> > > > > > > which was green.
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey <
> bus...@cloudera.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > If the website can't build on the build machine then it can't
> > > > build.
> > > > > > > >
> > > > > > > > We've worked hard as a community to automate this stuff and I
> > > don't
> > > > > > want
> > > > > > > to
> > > > > > > > go backwards.
> > > > > > > >
> > > > > > > > --
> > > > > > > > Sean Busbey
> > > > > > > >
> > > > > > > > On Oct 8, 2016 14:48, "Ted Yu"  > > wrote:
> > > > > > > >
> > > > > > > > > I did a local build:
> > > > > > > > >
> > > > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c0
> > 7478323dc5;
> > > > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64",
> > arch:
> > > > > > "amd64",
> > > > > > > > > family: "unix"
> > > > > > > > >
> > > > > > > > > [INFO] Final Memory: 30M/1928M
> > > > > > > > > [INFO]
> > > > > > > > > --
> --
> > > > > > > 
> > > > > > > > > [INFO] Archetype project created in
> > > > > > > > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > > > > > > > archetype/target/generated-sources/archetype
> > > > > > > > > [INFO]
> > > > > > > > > --
> --
> > > > > > > 
> > > > > > > > > [INFO] BUILD SUCCESS
> > > > > > > > > [INFO]
> > > > > > > > > --
> --
> > > > > > > 
> > > > > > > > > [INFO] Total time: 3.168 s
> > > > > > > > >
> > > > > > > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > > > > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > > > > > > ./target/site/apache_hbase_reference_guide.pdf
> > > > > > > > >
> > > > > > > > > I can attach the generated pdf to the JIRA if you want. It
> > > > contains
> > > > > > the
> > > > > > > > new
> > > > > > > > > guide on protobuf 3.
> > > > > > > > >
> > > > > > > > > The fstat error may be related to the build machine.
> > > > > > > > >
> > > > > > > > > Cheers
> > > > > > > > >
> > > > > > > > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu <
> yuzhih...@gmail.com
> > >
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > > This error didn't appear when the v1 was committed.
> > > > > > > 

Re: Still Failing: HBase Generate Website

[Dima Spivak]

I'll revert and rerun on the same build machine. Whether the problem is
with the environment or not, I don't recall it ever happening before this
commit and this kind of regression is unacceptable.

On Sunday, October 9, 2016, stack  wrote:

> Did you do the revert meantime Ted?
>
> On Oct 8, 2016 19:01, "Ted Yu" > wrote:
>
> > Logged INFRA-12731
> >
> > On Sat, Oct 8, 2016 at 6:56 PM, 张铎 >
> wrote:
> >
> > > Build environment issue IS a issue. If we do not consider H0 and H1 as
> > > broken, we need to fix the problem.
> > >
> > > And we are not sure if all other machines are OK right? As for now, the
> > > failed machines wins, 2 vs. 1.
> > >
> > > Thanks.
> > >
> > > 2016-10-09 9:36 GMT+08:00 Ted Yu >:
> > >
> > > > This seems to be build environment issue.
> > > >
> > > > Build #368 (green) was on H4 while #369 was on H0. #370 was on H1.
> > > >
> > > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  > wrote:
> > > >
> > > > > This maybe related to a jruby issue.
> > > > >
> > > > > https://github.com/jruby/jruby/issues/2913
> > > > >
> > > > > It depends on the environment thus it may fail on some machines
> while
> > > > > success on some other machines.
> > > > >
> > > > > 2016-10-09 9:29 GMT+08:00 Ted Yu  >:
> > > > >
> > > > > > This was the build 16750 went into:
> > > > > >
> > > > > > https://builds.apache.org/job/hbase_generate_website/368/
> > > > > >
> > > > > > which was green.
> > > > > >
> > > > > >
> > > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey  >
> > > > wrote:
> > > > > >
> > > > > > > If the website can't build on the build machine then it can't
> > > build.
> > > > > > >
> > > > > > > We've worked hard as a community to automate this stuff and I
> > don't
> > > > > want
> > > > > > to
> > > > > > > go backwards.
> > > > > > >
> > > > > > > --
> > > > > > > Sean Busbey
> > > > > > >
> > > > > > > On Oct 8, 2016 14:48, "Ted Yu"  > wrote:
> > > > > > >
> > > > > > > > I did a local build:
> > > > > > > >
> > > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c0
> 7478323dc5;
> > > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64",
> arch:
> > > > > "amd64",
> > > > > > > > family: "unix"
> > > > > > > >
> > > > > > > > [INFO] Final Memory: 30M/1928M
> > > > > > > > [INFO]
> > > > > > > > 
> > > > > > 
> > > > > > > > [INFO] Archetype project created in
> > > > > > > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > > > > > > archetype/target/generated-sources/archetype
> > > > > > > > [INFO]
> > > > > > > > 
> > > > > > 
> > > > > > > > [INFO] BUILD SUCCESS
> > > > > > > > [INFO]
> > > > > > > > 
> > > > > > 
> > > > > > > > [INFO] Total time: 3.168 s
> > > > > > > >
> > > > > > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > > > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > > > > > ./target/site/apache_hbase_reference_guide.pdf
> > > > > > > >
> > > > > > > > I can attach the generated pdf to the JIRA if you want. It
> > > contains
> > > > > the
> > > > > > > new
> > > > > > > > guide on protobuf 3.
> > > > > > > >
> > > > > > > > The fstat error may be related to the build machine.
> > > > > > > >
> > > > > > > > Cheers
> > > > > > > >
> > > > > > > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu  >
> > > > wrote:
> > > > > > > >
> > > > > > > > > This error didn't appear when the v1 was committed.
> > > > > > > > >
> > > > > > > > > Let me see if I can reproduce it locally on Linux.
> > > > > > > > >
> > > > > > > > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > > > > > > > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project
> > > hbase:
> > > > > > > > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > > > > > > > maven-plugin:1.5.3:process-asciidoc failed:
> > > org.jruby.exceptions.
> > > > > > > RaiseException:
> > > > > > > > (NotImplementedError) fstat unimplemented unsupported or
> native
> > > > > support
> > > > > > > > failed to load -> [Help 1]
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak <
> > > > > dimaspi...@apache.org >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >> Looks like HBASE-16750 again. Please 

Re: Still Failing: HBase Generate Website

[stack]

Did you do the revert meantime Ted?

On Oct 8, 2016 19:01, "Ted Yu"  wrote:

> Logged INFRA-12731
>
> On Sat, Oct 8, 2016 at 6:56 PM, 张铎  wrote:
>
> > Build environment issue IS a issue. If we do not consider H0 and H1 as
> > broken, we need to fix the problem.
> >
> > And we are not sure if all other machines are OK right? As for now, the
> > failed machines wins, 2 vs. 1.
> >
> > Thanks.
> >
> > 2016-10-09 9:36 GMT+08:00 Ted Yu :
> >
> > > This seems to be build environment issue.
> > >
> > > Build #368 (green) was on H4 while #369 was on H0. #370 was on H1.
> > >
> > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  wrote:
> > >
> > > > This maybe related to a jruby issue.
> > > >
> > > > https://github.com/jruby/jruby/issues/2913
> > > >
> > > > It depends on the environment thus it may fail on some machines while
> > > > success on some other machines.
> > > >
> > > > 2016-10-09 9:29 GMT+08:00 Ted Yu :
> > > >
> > > > > This was the build 16750 went into:
> > > > >
> > > > > https://builds.apache.org/job/hbase_generate_website/368/
> > > > >
> > > > > which was green.
> > > > >
> > > > >
> > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey 
> > > wrote:
> > > > >
> > > > > > If the website can't build on the build machine then it can't
> > build.
> > > > > >
> > > > > > We've worked hard as a community to automate this stuff and I
> don't
> > > > want
> > > > > to
> > > > > > go backwards.
> > > > > >
> > > > > > --
> > > > > > Sean Busbey
> > > > > >
> > > > > > On Oct 8, 2016 14:48, "Ted Yu"  wrote:
> > > > > >
> > > > > > > I did a local build:
> > > > > > >
> > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch:
> > > > "amd64",
> > > > > > > family: "unix"
> > > > > > >
> > > > > > > [INFO] Final Memory: 30M/1928M
> > > > > > > [INFO]
> > > > > > > 
> > > > > 
> > > > > > > [INFO] Archetype project created in
> > > > > > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > > > > > archetype/target/generated-sources/archetype
> > > > > > > [INFO]
> > > > > > > 
> > > > > 
> > > > > > > [INFO] BUILD SUCCESS
> > > > > > > [INFO]
> > > > > > > 
> > > > > 
> > > > > > > [INFO] Total time: 3.168 s
> > > > > > >
> > > > > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > > > > ./target/site/apache_hbase_reference_guide.pdf
> > > > > > >
> > > > > > > I can attach the generated pdf to the JIRA if you want. It
> > contains
> > > > the
> > > > > > new
> > > > > > > guide on protobuf 3.
> > > > > > >
> > > > > > > The fstat error may be related to the build machine.
> > > > > > >
> > > > > > > Cheers
> > > > > > >
> > > > > > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu 
> > > wrote:
> > > > > > >
> > > > > > > > This error didn't appear when the v1 was committed.
> > > > > > > >
> > > > > > > > Let me see if I can reproduce it locally on Linux.
> > > > > > > >
> > > > > > > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > > > > > > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project
> > hbase:
> > > > > > > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > > > > > > maven-plugin:1.5.3:process-asciidoc failed:
> > org.jruby.exceptions.
> > > > > > RaiseException:
> > > > > > > (NotImplementedError) fstat unimplemented unsupported or native
> > > > support
> > > > > > > failed to load -> [Help 1]
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak <
> > > > dimaspi...@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Looks like HBASE-16750 again. Please revert this again, Ted,
> > and
> > > > > close
> > > > > > > as
> > > > > > > >> "won't fix" if we can't test it before pushing commits.
> > > > > > > >>
> > > > > > > >> On Saturday, October 8, 2016, Apache Jenkins Server <
> > > > > > > >> jenk...@builds.apache.org> wrote:
> > > > > > > >>
> > > > > > > >> > Build status: Still Failing
> > > > > > > >> >
> > > > > > > >> > If successful, the website and docs have been generated.
> To
> > > > update
> > > > > > the
> > > > > > > >> > live site, follow the instructions below. If failed, skip
> to
> > > the
> > > > > > > bottom
> > > > > > > >> of
> > > > > > > >> > this email.
> > > > > > > >> >
> > > > > > 

Re: Still Failing: HBase Generate Website

[Ted Yu]

Logged INFRA-12731

On Sat, Oct 8, 2016 at 6:56 PM, 张铎  wrote:

> Build environment issue IS a issue. If we do not consider H0 and H1 as
> broken, we need to fix the problem.
>
> And we are not sure if all other machines are OK right? As for now, the
> failed machines wins, 2 vs. 1.
>
> Thanks.
>
> 2016-10-09 9:36 GMT+08:00 Ted Yu :
>
> > This seems to be build environment issue.
> >
> > Build #368 (green) was on H4 while #369 was on H0. #370 was on H1.
> >
> > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  wrote:
> >
> > > This maybe related to a jruby issue.
> > >
> > > https://github.com/jruby/jruby/issues/2913
> > >
> > > It depends on the environment thus it may fail on some machines while
> > > success on some other machines.
> > >
> > > 2016-10-09 9:29 GMT+08:00 Ted Yu :
> > >
> > > > This was the build 16750 went into:
> > > >
> > > > https://builds.apache.org/job/hbase_generate_website/368/
> > > >
> > > > which was green.
> > > >
> > > >
> > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey 
> > wrote:
> > > >
> > > > > If the website can't build on the build machine then it can't
> build.
> > > > >
> > > > > We've worked hard as a community to automate this stuff and I don't
> > > want
> > > > to
> > > > > go backwards.
> > > > >
> > > > > --
> > > > > Sean Busbey
> > > > >
> > > > > On Oct 8, 2016 14:48, "Ted Yu"  wrote:
> > > > >
> > > > > > I did a local build:
> > > > > >
> > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > Maven home: /apache-maven-3.3.9
> > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch:
> > > "amd64",
> > > > > > family: "unix"
> > > > > >
> > > > > > [INFO] Final Memory: 30M/1928M
> > > > > > [INFO]
> > > > > > 
> > > > 
> > > > > > [INFO] Archetype project created in
> > > > > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > > > > archetype/target/generated-sources/archetype
> > > > > > [INFO]
> > > > > > 
> > > > 
> > > > > > [INFO] BUILD SUCCESS
> > > > > > [INFO]
> > > > > > 
> > > > 
> > > > > > [INFO] Total time: 3.168 s
> > > > > >
> > > > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > > > ./target/site/apache_hbase_reference_guide.pdf
> > > > > >
> > > > > > I can attach the generated pdf to the JIRA if you want. It
> contains
> > > the
> > > > > new
> > > > > > guide on protobuf 3.
> > > > > >
> > > > > > The fstat error may be related to the build machine.
> > > > > >
> > > > > > Cheers
> > > > > >
> > > > > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu 
> > wrote:
> > > > > >
> > > > > > > This error didn't appear when the v1 was committed.
> > > > > > >
> > > > > > > Let me see if I can reproduce it locally on Linux.
> > > > > > >
> > > > > > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > > > > > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project
> hbase:
> > > > > > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > > > > > maven-plugin:1.5.3:process-asciidoc failed:
> org.jruby.exceptions.
> > > > > RaiseException:
> > > > > > (NotImplementedError) fstat unimplemented unsupported or native
> > > support
> > > > > > failed to load -> [Help 1]
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak <
> > > dimaspi...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Looks like HBASE-16750 again. Please revert this again, Ted,
> and
> > > > close
> > > > > > as
> > > > > > >> "won't fix" if we can't test it before pushing commits.
> > > > > > >>
> > > > > > >> On Saturday, October 8, 2016, Apache Jenkins Server <
> > > > > > >> jenk...@builds.apache.org> wrote:
> > > > > > >>
> > > > > > >> > Build status: Still Failing
> > > > > > >> >
> > > > > > >> > If successful, the website and docs have been generated. To
> > > update
> > > > > the
> > > > > > >> > live site, follow the instructions below. If failed, skip to
> > the
> > > > > > bottom
> > > > > > >> of
> > > > > > >> > this email.
> > > > > > >> >
> > > > > > >> > Use the following commands to download the patch and apply
> it
> > > to a
> > > > > > clean
> > > > > > >> > branch based on origin/asf-site. If you prefer to keep the
> > > > > hbase-site
> > > > > > >> repo
> > > > > > >> > around permanently, you can skip the clone step.
> > > > > > >> >
> > > > > > >> >   git clone https://git-wip-us.apache.org/
> > > > 

Re: Still Failing: HBase Generate Website

[张铎]

Build environment issue IS a issue. If we do not consider H0 and H1 as
broken, we need to fix the problem.

And we are not sure if all other machines are OK right? As for now, the
failed machines wins, 2 vs. 1.

Thanks.

2016-10-09 9:36 GMT+08:00 Ted Yu :

> This seems to be build environment issue.
>
> Build #368 (green) was on H4 while #369 was on H0. #370 was on H1.
>
> On Sat, Oct 8, 2016 at 6:32 PM, 张铎  wrote:
>
> > This maybe related to a jruby issue.
> >
> > https://github.com/jruby/jruby/issues/2913
> >
> > It depends on the environment thus it may fail on some machines while
> > success on some other machines.
> >
> > 2016-10-09 9:29 GMT+08:00 Ted Yu :
> >
> > > This was the build 16750 went into:
> > >
> > > https://builds.apache.org/job/hbase_generate_website/368/
> > >
> > > which was green.
> > >
> > >
> > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey 
> wrote:
> > >
> > > > If the website can't build on the build machine then it can't build.
> > > >
> > > > We've worked hard as a community to automate this stuff and I don't
> > want
> > > to
> > > > go backwards.
> > > >
> > > > --
> > > > Sean Busbey
> > > >
> > > > On Oct 8, 2016 14:48, "Ted Yu"  wrote:
> > > >
> > > > > I did a local build:
> > > > >
> > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > > > 2015-11-10T16:41:47+00:00)
> > > > > Maven home: /apache-maven-3.3.9
> > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > Java home: /jdk1.8.0_101/jre
> > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch:
> > "amd64",
> > > > > family: "unix"
> > > > >
> > > > > [INFO] Final Memory: 30M/1928M
> > > > > [INFO]
> > > > > 
> > > 
> > > > > [INFO] Archetype project created in
> > > > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > > > archetype/target/generated-sources/archetype
> > > > > [INFO]
> > > > > 
> > > 
> > > > > [INFO] BUILD SUCCESS
> > > > > [INFO]
> > > > > 
> > > 
> > > > > [INFO] Total time: 3.168 s
> > > > >
> > > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > > ./target/site/apache_hbase_reference_guide.pdf
> > > > >
> > > > > I can attach the generated pdf to the JIRA if you want. It contains
> > the
> > > > new
> > > > > guide on protobuf 3.
> > > > >
> > > > > The fstat error may be related to the build machine.
> > > > >
> > > > > Cheers
> > > > >
> > > > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu 
> wrote:
> > > > >
> > > > > > This error didn't appear when the v1 was committed.
> > > > > >
> > > > > > Let me see if I can reproduce it locally on Linux.
> > > > > >
> > > > > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > > > > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project hbase:
> > > > > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > > > > maven-plugin:1.5.3:process-asciidoc failed: org.jruby.exceptions.
> > > > RaiseException:
> > > > > (NotImplementedError) fstat unimplemented unsupported or native
> > support
> > > > > failed to load -> [Help 1]
> > > > > >
> > > > > >
> > > > > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak <
> > dimaspi...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > >> Looks like HBASE-16750 again. Please revert this again, Ted, and
> > > close
> > > > > as
> > > > > >> "won't fix" if we can't test it before pushing commits.
> > > > > >>
> > > > > >> On Saturday, October 8, 2016, Apache Jenkins Server <
> > > > > >> jenk...@builds.apache.org> wrote:
> > > > > >>
> > > > > >> > Build status: Still Failing
> > > > > >> >
> > > > > >> > If successful, the website and docs have been generated. To
> > update
> > > > the
> > > > > >> > live site, follow the instructions below. If failed, skip to
> the
> > > > > bottom
> > > > > >> of
> > > > > >> > this email.
> > > > > >> >
> > > > > >> > Use the following commands to download the patch and apply it
> > to a
> > > > > clean
> > > > > >> > branch based on origin/asf-site. If you prefer to keep the
> > > > hbase-site
> > > > > >> repo
> > > > > >> > around permanently, you can skip the clone step.
> > > > > >> >
> > > > > >> >   git clone https://git-wip-us.apache.org/
> > > repos/asf/hbase-site.git
> > > > > >> >
> > > > > >> >   cd hbase-site
> > > > > >> >   wget -O- https://builds.apache.org/job/
> > > > hbase_generate_website/370/
> > > > > >> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> > > > > >> >   git fetch
> > > > > >> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> > > > > >> >   git am --whitespace=fix 

Re: Still Failing: HBase Generate Website

[Ted Yu]

This seems to be build environment issue.

Build #368 (green) was on H4 while #369 was on H0. #370 was on H1.

On Sat, Oct 8, 2016 at 6:32 PM, 张铎  wrote:

> This maybe related to a jruby issue.
>
> https://github.com/jruby/jruby/issues/2913
>
> It depends on the environment thus it may fail on some machines while
> success on some other machines.
>
> 2016-10-09 9:29 GMT+08:00 Ted Yu :
>
> > This was the build 16750 went into:
> >
> > https://builds.apache.org/job/hbase_generate_website/368/
> >
> > which was green.
> >
> >
> > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey  wrote:
> >
> > > If the website can't build on the build machine then it can't build.
> > >
> > > We've worked hard as a community to automate this stuff and I don't
> want
> > to
> > > go backwards.
> > >
> > > --
> > > Sean Busbey
> > >
> > > On Oct 8, 2016 14:48, "Ted Yu"  wrote:
> > >
> > > > I did a local build:
> > > >
> > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > > 2015-11-10T16:41:47+00:00)
> > > > Maven home: /apache-maven-3.3.9
> > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > Java home: /jdk1.8.0_101/jre
> > > > Default locale: en_US, platform encoding: UTF-8
> > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch:
> "amd64",
> > > > family: "unix"
> > > >
> > > > [INFO] Final Memory: 30M/1928M
> > > > [INFO]
> > > > 
> > 
> > > > [INFO] Archetype project created in
> > > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > > archetype/target/generated-sources/archetype
> > > > [INFO]
> > > > 
> > 
> > > > [INFO] BUILD SUCCESS
> > > > [INFO]
> > > > 
> > 
> > > > [INFO] Total time: 3.168 s
> > > >
> > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > ./target/site/apache_hbase_reference_guide.pdf
> > > >
> > > > I can attach the generated pdf to the JIRA if you want. It contains
> the
> > > new
> > > > guide on protobuf 3.
> > > >
> > > > The fstat error may be related to the build machine.
> > > >
> > > > Cheers
> > > >
> > > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu  wrote:
> > > >
> > > > > This error didn't appear when the v1 was committed.
> > > > >
> > > > > Let me see if I can reproduce it locally on Linux.
> > > > >
> > > > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > > > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project hbase:
> > > > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > > > maven-plugin:1.5.3:process-asciidoc failed: org.jruby.exceptions.
> > > RaiseException:
> > > > (NotImplementedError) fstat unimplemented unsupported or native
> support
> > > > failed to load -> [Help 1]
> > > > >
> > > > >
> > > > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak <
> dimaspi...@apache.org>
> > > > > wrote:
> > > > >
> > > > >> Looks like HBASE-16750 again. Please revert this again, Ted, and
> > close
> > > > as
> > > > >> "won't fix" if we can't test it before pushing commits.
> > > > >>
> > > > >> On Saturday, October 8, 2016, Apache Jenkins Server <
> > > > >> jenk...@builds.apache.org> wrote:
> > > > >>
> > > > >> > Build status: Still Failing
> > > > >> >
> > > > >> > If successful, the website and docs have been generated. To
> update
> > > the
> > > > >> > live site, follow the instructions below. If failed, skip to the
> > > > bottom
> > > > >> of
> > > > >> > this email.
> > > > >> >
> > > > >> > Use the following commands to download the patch and apply it
> to a
> > > > clean
> > > > >> > branch based on origin/asf-site. If you prefer to keep the
> > > hbase-site
> > > > >> repo
> > > > >> > around permanently, you can skip the clone step.
> > > > >> >
> > > > >> >   git clone https://git-wip-us.apache.org/
> > repos/asf/hbase-site.git
> > > > >> >
> > > > >> >   cd hbase-site
> > > > >> >   wget -O- https://builds.apache.org/job/
> > > hbase_generate_website/370/
> > > > >> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> > > > >> >   git fetch
> > > > >> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> > > > >> >   git am --whitespace=fix $GIT_SHA.patch
> > > > >> >
> > > > >> > At this point, you can preview the changes by opening index.html
> > or
> > > > any
> > > > >> of
> > > > >> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> > > > >> >
> > > > >> > There are lots of spurious changes, such as timestamps and CSS
> > > styles
> > > > in
> > > > >> > tables, so a generic git diff is not very useful. To see a list
> of
> > > > files
> > > > >> > that have been added, deleted, renamed, changed type, or are
> > > otherwise
> > > > >> > interesting, use the following 

Re: Still Failing: HBase Generate Website

[张铎]

This maybe related to a jruby issue.

https://github.com/jruby/jruby/issues/2913

It depends on the environment thus it may fail on some machines while
success on some other machines.

2016-10-09 9:29 GMT+08:00 Ted Yu :

> This was the build 16750 went into:
>
> https://builds.apache.org/job/hbase_generate_website/368/
>
> which was green.
>
>
> On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey  wrote:
>
> > If the website can't build on the build machine then it can't build.
> >
> > We've worked hard as a community to automate this stuff and I don't want
> to
> > go backwards.
> >
> > --
> > Sean Busbey
> >
> > On Oct 8, 2016 14:48, "Ted Yu"  wrote:
> >
> > > I did a local build:
> > >
> > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > 2015-11-10T16:41:47+00:00)
> > > Maven home: /apache-maven-3.3.9
> > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > Java home: /jdk1.8.0_101/jre
> > > Default locale: en_US, platform encoding: UTF-8
> > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch: "amd64",
> > > family: "unix"
> > >
> > > [INFO] Final Memory: 30M/1928M
> > > [INFO]
> > > 
> 
> > > [INFO] Archetype project created in
> > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > archetype/target/generated-sources/archetype
> > > [INFO]
> > > 
> 
> > > [INFO] BUILD SUCCESS
> > > [INFO]
> > > 
> 
> > > [INFO] Total time: 3.168 s
> > >
> > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > ./target/site/apache_hbase_reference_guide.pdf
> > >
> > > I can attach the generated pdf to the JIRA if you want. It contains the
> > new
> > > guide on protobuf 3.
> > >
> > > The fstat error may be related to the build machine.
> > >
> > > Cheers
> > >
> > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu  wrote:
> > >
> > > > This error didn't appear when the v1 was committed.
> > > >
> > > > Let me see if I can reproduce it locally on Linux.
> > > >
> > > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project hbase:
> > > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > > maven-plugin:1.5.3:process-asciidoc failed: org.jruby.exceptions.
> > RaiseException:
> > > (NotImplementedError) fstat unimplemented unsupported or native support
> > > failed to load -> [Help 1]
> > > >
> > > >
> > > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak 
> > > > wrote:
> > > >
> > > >> Looks like HBASE-16750 again. Please revert this again, Ted, and
> close
> > > as
> > > >> "won't fix" if we can't test it before pushing commits.
> > > >>
> > > >> On Saturday, October 8, 2016, Apache Jenkins Server <
> > > >> jenk...@builds.apache.org> wrote:
> > > >>
> > > >> > Build status: Still Failing
> > > >> >
> > > >> > If successful, the website and docs have been generated. To update
> > the
> > > >> > live site, follow the instructions below. If failed, skip to the
> > > bottom
> > > >> of
> > > >> > this email.
> > > >> >
> > > >> > Use the following commands to download the patch and apply it to a
> > > clean
> > > >> > branch based on origin/asf-site. If you prefer to keep the
> > hbase-site
> > > >> repo
> > > >> > around permanently, you can skip the clone step.
> > > >> >
> > > >> >   git clone https://git-wip-us.apache.org/
> repos/asf/hbase-site.git
> > > >> >
> > > >> >   cd hbase-site
> > > >> >   wget -O- https://builds.apache.org/job/
> > hbase_generate_website/370/
> > > >> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> > > >> >   git fetch
> > > >> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> > > >> >   git am --whitespace=fix $GIT_SHA.patch
> > > >> >
> > > >> > At this point, you can preview the changes by opening index.html
> or
> > > any
> > > >> of
> > > >> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> > > >> >
> > > >> > There are lots of spurious changes, such as timestamps and CSS
> > styles
> > > in
> > > >> > tables, so a generic git diff is not very useful. To see a list of
> > > files
> > > >> > that have been added, deleted, renamed, changed type, or are
> > otherwise
> > > >> > interesting, use the following command:
> > > >> >
> > > >> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> > > >> >
> > > >> > To see only files that had 100 or more lines changed:
> > > >> >
> > > >> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> > > >> >
> > > >> > When you are satisfied, publish your changes to origin/asf-site
> > using
> > > >> > these commands:
> > > >> >
> > > >> >   git commit --allow-empty -m "Empty commit" # to work around 

Re: Still Failing: HBase Generate Website

[Ted Yu]

This was the build 16750 went into:

https://builds.apache.org/job/hbase_generate_website/368/

which was green.


On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey  wrote:

> If the website can't build on the build machine then it can't build.
>
> We've worked hard as a community to automate this stuff and I don't want to
> go backwards.
>
> --
> Sean Busbey
>
> On Oct 8, 2016 14:48, "Ted Yu"  wrote:
>
> > I did a local build:
> >
> > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > 2015-11-10T16:41:47+00:00)
> > Maven home: /apache-maven-3.3.9
> > Java version: 1.8.0_101, vendor: Oracle Corporation
> > Java home: /jdk1.8.0_101/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch: "amd64",
> > family: "unix"
> >
> > [INFO] Final Memory: 30M/1928M
> > [INFO]
> > 
> > [INFO] Archetype project created in
> > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > archetype/target/generated-sources/archetype
> > [INFO]
> > 
> > [INFO] BUILD SUCCESS
> > [INFO]
> > 
> > [INFO] Total time: 3.168 s
> >
> > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > ./target/site/apache_hbase_reference_guide.pdf
> >
> > I can attach the generated pdf to the JIRA if you want. It contains the
> new
> > guide on protobuf 3.
> >
> > The fstat error may be related to the build machine.
> >
> > Cheers
> >
> > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu  wrote:
> >
> > > This error didn't appear when the v1 was committed.
> > >
> > > Let me see if I can reproduce it locally on Linux.
> > >
> > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project hbase:
> > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > maven-plugin:1.5.3:process-asciidoc failed: org.jruby.exceptions.
> RaiseException:
> > (NotImplementedError) fstat unimplemented unsupported or native support
> > failed to load -> [Help 1]
> > >
> > >
> > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak 
> > > wrote:
> > >
> > >> Looks like HBASE-16750 again. Please revert this again, Ted, and close
> > as
> > >> "won't fix" if we can't test it before pushing commits.
> > >>
> > >> On Saturday, October 8, 2016, Apache Jenkins Server <
> > >> jenk...@builds.apache.org> wrote:
> > >>
> > >> > Build status: Still Failing
> > >> >
> > >> > If successful, the website and docs have been generated. To update
> the
> > >> > live site, follow the instructions below. If failed, skip to the
> > bottom
> > >> of
> > >> > this email.
> > >> >
> > >> > Use the following commands to download the patch and apply it to a
> > clean
> > >> > branch based on origin/asf-site. If you prefer to keep the
> hbase-site
> > >> repo
> > >> > around permanently, you can skip the clone step.
> > >> >
> > >> >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> > >> >
> > >> >   cd hbase-site
> > >> >   wget -O- https://builds.apache.org/job/
> hbase_generate_website/370/
> > >> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> > >> >   git fetch
> > >> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> > >> >   git am --whitespace=fix $GIT_SHA.patch
> > >> >
> > >> > At this point, you can preview the changes by opening index.html or
> > any
> > >> of
> > >> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> > >> >
> > >> > There are lots of spurious changes, such as timestamps and CSS
> styles
> > in
> > >> > tables, so a generic git diff is not very useful. To see a list of
> > files
> > >> > that have been added, deleted, renamed, changed type, or are
> otherwise
> > >> > interesting, use the following command:
> > >> >
> > >> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> > >> >
> > >> > To see only files that had 100 or more lines changed:
> > >> >
> > >> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> > >> >
> > >> > When you are satisfied, publish your changes to origin/asf-site
> using
> > >> > these commands:
> > >> >
> > >> >   git commit --allow-empty -m "Empty commit" # to work around a
> > current
> > >> > ASF INFRA bug
> > >> >   git push origin asf-site-${GIT_SHA}:asf-site
> > >> >   git checkout asf-site
> > >> >   git branch -D asf-site-${GIT_SHA}
> > >> >
> > >> > Changes take a couple of minutes to be propagated. You can verify
> > >> whether
> > >> > they have been propagated by looking at the Last Published date at
> the
> > >> > bottom of http://hbase.apache.org/. It should match the date in the
> > >> > index.html on the asf-site branch in Git.
> > >> >
> > >> > As a courtesy- 

Re: Still Failing: HBase Generate Website

[Sean Busbey]

If the website can't build on the build machine then it can't build.

We've worked hard as a community to automate this stuff and I don't want to
go backwards.

-- 
Sean Busbey

On Oct 8, 2016 14:48, "Ted Yu"  wrote:

> I did a local build:
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T16:41:47+00:00)
> Maven home: /apache-maven-3.3.9
> Java version: 1.8.0_101, vendor: Oracle Corporation
> Java home: /jdk1.8.0_101/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch: "amd64",
> family: "unix"
>
> [INFO] Final Memory: 30M/1928M
> [INFO]
> 
> [INFO] Archetype project created in
> /hbase/hbase-archetypes/hbase-client-project/target/build-
> archetype/target/generated-sources/archetype
> [INFO]
> 
> [INFO] BUILD SUCCESS
> [INFO]
> 
> [INFO] Total time: 3.168 s
>
> $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> ./target/site/apache_hbase_reference_guide.pdf
>
> I can attach the generated pdf to the JIRA if you want. It contains the new
> guide on protobuf 3.
>
> The fstat error may be related to the build machine.
>
> Cheers
>
> On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu  wrote:
>
> > This error didn't appear when the v1 was committed.
> >
> > Let me see if I can reproduce it locally on Linux.
> >
> > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> maven-plugin:1.5.3:process-asciidoc (output-pdf) on project hbase:
> Execution output-pdf of goal org.asciidoctor:asciidoctor-
> maven-plugin:1.5.3:process-asciidoc failed: 
> org.jruby.exceptions.RaiseException:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> >
> >
> > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak 
> > wrote:
> >
> >> Looks like HBASE-16750 again. Please revert this again, Ted, and close
> as
> >> "won't fix" if we can't test it before pushing commits.
> >>
> >> On Saturday, October 8, 2016, Apache Jenkins Server <
> >> jenk...@builds.apache.org> wrote:
> >>
> >> > Build status: Still Failing
> >> >
> >> > If successful, the website and docs have been generated. To update the
> >> > live site, follow the instructions below. If failed, skip to the
> bottom
> >> of
> >> > this email.
> >> >
> >> > Use the following commands to download the patch and apply it to a
> clean
> >> > branch based on origin/asf-site. If you prefer to keep the hbase-site
> >> repo
> >> > around permanently, you can skip the clone step.
> >> >
> >> >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >> >
> >> >   cd hbase-site
> >> >   wget -O- https://builds.apache.org/job/hbase_generate_website/370/
> >> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> >> >   git fetch
> >> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> >> >   git am --whitespace=fix $GIT_SHA.patch
> >> >
> >> > At this point, you can preview the changes by opening index.html or
> any
> >> of
> >> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> >> >
> >> > There are lots of spurious changes, such as timestamps and CSS styles
> in
> >> > tables, so a generic git diff is not very useful. To see a list of
> files
> >> > that have been added, deleted, renamed, changed type, or are otherwise
> >> > interesting, use the following command:
> >> >
> >> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >> >
> >> > To see only files that had 100 or more lines changed:
> >> >
> >> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >> >
> >> > When you are satisfied, publish your changes to origin/asf-site using
> >> > these commands:
> >> >
> >> >   git commit --allow-empty -m "Empty commit" # to work around a
> current
> >> > ASF INFRA bug
> >> >   git push origin asf-site-${GIT_SHA}:asf-site
> >> >   git checkout asf-site
> >> >   git branch -D asf-site-${GIT_SHA}
> >> >
> >> > Changes take a couple of minutes to be propagated. You can verify
> >> whether
> >> > they have been propagated by looking at the Last Published date at the
> >> > bottom of http://hbase.apache.org/. It should match the date in the
> >> > index.html on the asf-site branch in Git.
> >> >
> >> > As a courtesy- reply-all to this email to let other committers know
> you
> >> > pushed the site.
> >> >
> >> >
> >> >
> >> > If failed, see https://builds.apache.org/job/
> >> hbase_generate_website/370/
> >> > console
> >>
> >>
> >>
> >> --
> >> -Dima
> >>
> >
> >
>

Re: Still Failing: HBase Generate Website

[Ted Yu]

I did a local build:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: /apache-maven-3.3.9
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: /jdk1.8.0_101/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch: "amd64",
family: "unix"

[INFO] Final Memory: 30M/1928M
[INFO]

[INFO] Archetype project created in
/hbase/hbase-archetypes/hbase-client-project/target/build-archetype/target/generated-sources/archetype
[INFO]

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time: 3.168 s

$ ls -l ./target/site/apache_hbase_reference_guide.pdf
-rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
./target/site/apache_hbase_reference_guide.pdf

I can attach the generated pdf to the JIRA if you want. It contains the new
guide on protobuf 3.

The fstat error may be related to the build machine.

Cheers

On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu  wrote:

> This error didn't appear when the v1 was committed.
>
> Let me see if I can reproduce it locally on Linux.
>
> [ERROR] Failed to execute goal 
> org.asciidoctor:asciidoctor-maven-plugin:1.5.3:process-asciidoc (output-pdf) 
> on project hbase: Execution output-pdf of goal 
> org.asciidoctor:asciidoctor-maven-plugin:1.5.3:process-asciidoc failed: 
> org.jruby.exceptions.RaiseException: (NotImplementedError) fstat 
> unimplemented unsupported or native support failed to load -> [Help 1]
>
>
> On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak 
> wrote:
>
>> Looks like HBASE-16750 again. Please revert this again, Ted, and close as
>> "won't fix" if we can't test it before pushing commits.
>>
>> On Saturday, October 8, 2016, Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
>>
>> > Build status: Still Failing
>> >
>> > If successful, the website and docs have been generated. To update the
>> > live site, follow the instructions below. If failed, skip to the bottom
>> of
>> > this email.
>> >
>> > Use the following commands to download the patch and apply it to a clean
>> > branch based on origin/asf-site. If you prefer to keep the hbase-site
>> repo
>> > around permanently, you can skip the clone step.
>> >
>> >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>> >
>> >   cd hbase-site
>> >   wget -O- https://builds.apache.org/job/hbase_generate_website/370/
>> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>> >   git fetch
>> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>> >   git am --whitespace=fix $GIT_SHA.patch
>> >
>> > At this point, you can preview the changes by opening index.html or any
>> of
>> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
>> >
>> > There are lots of spurious changes, such as timestamps and CSS styles in
>> > tables, so a generic git diff is not very useful. To see a list of files
>> > that have been added, deleted, renamed, changed type, or are otherwise
>> > interesting, use the following command:
>> >
>> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>> >
>> > To see only files that had 100 or more lines changed:
>> >
>> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>> >
>> > When you are satisfied, publish your changes to origin/asf-site using
>> > these commands:
>> >
>> >   git commit --allow-empty -m "Empty commit" # to work around a current
>> > ASF INFRA bug
>> >   git push origin asf-site-${GIT_SHA}:asf-site
>> >   git checkout asf-site
>> >   git branch -D asf-site-${GIT_SHA}
>> >
>> > Changes take a couple of minutes to be propagated. You can verify
>> whether
>> > they have been propagated by looking at the Last Published date at the
>> > bottom of http://hbase.apache.org/. It should match the date in the
>> > index.html on the asf-site branch in Git.
>> >
>> > As a courtesy- reply-all to this email to let other committers know you
>> > pushed the site.
>> >
>> >
>> >
>> > If failed, see https://builds.apache.org/job/
>> hbase_generate_website/370/
>> > console
>>
>>
>>
>> --
>> -Dima
>>
>
>

Re: Still Failing: HBase Generate Website

[Ted Yu]

This error didn't appear when the v1 was committed.

Let me see if I can reproduce it locally on Linux.

[ERROR] Failed to execute goal
org.asciidoctor:asciidoctor-maven-plugin:1.5.3:process-asciidoc
(output-pdf) on project hbase: Execution output-pdf of goal
org.asciidoctor:asciidoctor-maven-plugin:1.5.3:process-asciidoc
failed: org.jruby.exceptions.RaiseException: (NotImplementedError)
fstat unimplemented unsupported or native support failed to load ->
[Help 1]


On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak  wrote:

> Looks like HBASE-16750 again. Please revert this again, Ted, and close as
> "won't fix" if we can't test it before pushing commits.
>
> On Saturday, October 8, 2016, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Still Failing
> >
> > If successful, the website and docs have been generated. To update the
> > live site, follow the instructions below. If failed, skip to the bottom
> of
> > this email.
> >
> > Use the following commands to download the patch and apply it to a clean
> > branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> > around permanently, you can skip the clone step.
> >
> >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >
> >   cd hbase-site
> >   wget -O- https://builds.apache.org/job/hbase_generate_website/370/
> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> >   git fetch
> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> >   git am --whitespace=fix $GIT_SHA.patch
> >
> > At this point, you can preview the changes by opening index.html or any
> of
> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> >
> > There are lots of spurious changes, such as timestamps and CSS styles in
> > tables, so a generic git diff is not very useful. To see a list of files
> > that have been added, deleted, renamed, changed type, or are otherwise
> > interesting, use the following command:
> >
> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >
> > To see only files that had 100 or more lines changed:
> >
> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >
> > When you are satisfied, publish your changes to origin/asf-site using
> > these commands:
> >
> >   git commit --allow-empty -m "Empty commit" # to work around a current
> > ASF INFRA bug
> >   git push origin asf-site-${GIT_SHA}:asf-site
> >   git checkout asf-site
> >   git branch -D asf-site-${GIT_SHA}
> >
> > Changes take a couple of minutes to be propagated. You can verify whether
> > they have been propagated by looking at the Last Published date at the
> > bottom of http://hbase.apache.org/. It should match the date in the
> > index.html on the asf-site branch in Git.
> >
> > As a courtesy- reply-all to this email to let other committers know you
> > pushed the site.
> >
> >
> >
> > If failed, see https://builds.apache.org/job/hbase_generate_website/370/
> > console
>
>
>
> --
> -Dima
>

Re: Still Failing: HBase Generate Website

[Dima Spivak]

Looks like HBASE-16750 again. Please revert this again, Ted, and close as
"won't fix" if we can't test it before pushing commits.

On Saturday, October 8, 2016, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/370/
> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/hbase_generate_website/370/
> console



-- 
-Dima

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/370/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/370/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/365/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/365/console

Re: Still Failing: HBase Generate Website

[Dima Spivak]

Fixing, fixing... Sorry for the Jenkins noise.

-Dima

On Mon, Sep 12, 2016 at 10:52 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/341/
> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/hbase_generate_website/341/
> console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/341/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/341/console

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

Filed https://issues.apache.org/jira/browse/INFRA-11613.

On Thu, Apr 7, 2016 at 9:57 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> If successful, the website and docs have been generated. If failed, skip
> to the bottom of this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O-
> https://builds.apache.org/job/hbase_generate_website/192/artifact/website.patch.zip
> | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch, and you can
> review the differences by running:
>
>   git diff origin/asf-site
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables. To see a list of files that have been added, deleted, renamed,
> changed type, or are otherwise interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using this
> command:
>
>   git push origin asf-site-${GIT_SHA}:asf-site
>
> Changes take a couple of minutes to be propagated. You can then remove
> your asf-site-${GIT_SHA} branch:
>
>   git checkout asf-site && git branch -d asf-site-${GIT_SHA}
>
>
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/192/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/167/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/167/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Still Failing

If successful, the website and docs have been generated. Save the following 
link and apply it by using the following commands:

wget -O- 
https://builds.apache.org/job/hbase_generate_website/34/artifact/website.patch.zip
 | bsdtar xf -
git checkout asf-site; git pull
git am website.patch
git commit -m "Published website at $GIT_SHA"
git push origin asf-site


If failed, see https://builds.apache.org/job/hbase_generate_website/34/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Still Failing

If successful, the website and docs have been pushed. The patch has been 
attached.


If failed, see https://builds.apache.org/job/hbase_generate_website/19/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Still Failing

If successful, the website and docs have been pushed. The patch has been 
attached.


If failed, see https://builds.apache.org/job/hbase_generate_website/21/console

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

Sorry for the spam.

On Thu, Nov 5, 2015 at 1:12 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Still Failing
>
> If successful, the website and docs have been pushed. The patch has been
> attached.
>
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/21/console

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Still Failing

If successful, the website and docs have been pushed. The patch has been 
attached.


If failed, see https://builds.apache.org/job/hbase_generate_website/20/console