hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 张铎 <palomino...@gmail.com>
Subject Re: Still Failing: HBase Generate Website
Date Sun, 09 Oct 2016 01:32:48 GMT
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 <yuzhihong@gmail.com>:

> 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 <busbey@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" <yuzhihong@gmail.com> 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 <yuzhihong@gmail.com> 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 <dimaspivak@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 <
> > > >> jenkins@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
> > > >>
> > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message