You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Jonathan Hsieh <jo...@cloudera.com> on 2013/12/11 16:13:55 UTC
We haven't had a clean hadoopqa build since 10/2/13.
Just a reminder -- we do not want to introduce new javadoc warnings,
findbugs warnings, or break the docs/site compile. Please clean up after
you commits! If you are committing something else and a warning shows up,
please investigate enough in order ping to the committer responsible
(email/jira) or even better just fix the problem.
Thanks,
Jon.
--
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com
Re: We haven't had a clean hadoopqa build since 10/2/13.
Posted by Ted Yu <yu...@gmail.com>.
As of PreCommit-HBASE-Build #8138, there was no javadoc and findbugs
warning.
Let's try to keep the QA run that way.
Cheers
On Wed, Dec 11, 2013 at 12:18 PM, Nicolas Liochon <nk...@gmail.com> wrote:
> We're alone on the precommit but not on the postcommit.
>
>
> On Wed, Dec 11, 2013 at 9:15 PM, Elliott Clark <ec...@apache.org> wrote:
>
> > Fixing the site build so that it doesn't take an install first seems to
> be
> > eluding me. The other option is to make the qa bot do an install. But
> for
> > that to be safe we need to make sure that the maven repositories aren't
> > shared on any concurrently running hadoop qa runs. Can someone with
> > jenkins perms see if that's already set up ?
> >
> >
> > On Wed, Dec 11, 2013 at 7:59 AM, Jonathan Hsieh <jo...@cloudera.com>
> wrote:
> >
> > > great - the fix can be done there. I did a git bisect to find the
> commits
> > > that caused the problem and emailed the committer.
> > >
> > > On Wednesday, December 11, 2013, Ted Yu wrote:
> > >
> > > > For the site build error,
> > > > HBASE-9729<https://issues.apache.org/jira/browse/HBASE-9729> was
> > > > logged.
> > > >
> > > > I do agree with Jon that no new warnings should be introduced.
> > > >
> > > > Currently 3 new Findbugs appear in QA reports.
> > > >
> > > > Cheers
> > > >
> > > >
> > > > On Wed, Dec 11, 2013 at 7:13 AM, Jonathan Hsieh <jon@cloudera.com
> > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > Just a reminder -- we do not want to introduce new javadoc
> warnings,
> > > > > findbugs warnings, or break the docs/site compile. Please clean up
> > > after
> > > > > you commits! If you are committing something else and a warning
> > shows
> > > > up,
> > > > > please investigate enough in order ping to the committer
> responsible
> > > > > (email/jira) or even better just fix the problem.
> > > > >
> > > > > Thanks,
> > > > > Jon.
> > > > >
> > > > >
> > > > > --
> > > > > // Jonathan Hsieh (shay)
> > > > > // Software Engineer, Cloudera
> > > > > // jon@cloudera.com <javascript:;>
> > > > >
> > > >
> > >
> > >
> > > --
> > > // Jonathan Hsieh (shay)
> > > // Software Engineer, Cloudera
> > > // jon@cloudera.com
> > >
> >
>
Re: We haven't had a clean hadoopqa build since 10/2/13.
Posted by Nicolas Liochon <nk...@gmail.com>.
We're alone on the precommit but not on the postcommit.
On Wed, Dec 11, 2013 at 9:15 PM, Elliott Clark <ec...@apache.org> wrote:
> Fixing the site build so that it doesn't take an install first seems to be
> eluding me. The other option is to make the qa bot do an install. But for
> that to be safe we need to make sure that the maven repositories aren't
> shared on any concurrently running hadoop qa runs. Can someone with
> jenkins perms see if that's already set up ?
>
>
> On Wed, Dec 11, 2013 at 7:59 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
>
> > great - the fix can be done there. I did a git bisect to find the commits
> > that caused the problem and emailed the committer.
> >
> > On Wednesday, December 11, 2013, Ted Yu wrote:
> >
> > > For the site build error,
> > > HBASE-9729<https://issues.apache.org/jira/browse/HBASE-9729> was
> > > logged.
> > >
> > > I do agree with Jon that no new warnings should be introduced.
> > >
> > > Currently 3 new Findbugs appear in QA reports.
> > >
> > > Cheers
> > >
> > >
> > > On Wed, Dec 11, 2013 at 7:13 AM, Jonathan Hsieh <jon@cloudera.com
> > <javascript:;>>
> > > wrote:
> > >
> > > > Just a reminder -- we do not want to introduce new javadoc warnings,
> > > > findbugs warnings, or break the docs/site compile. Please clean up
> > after
> > > > you commits! If you are committing something else and a warning
> shows
> > > up,
> > > > please investigate enough in order ping to the committer responsible
> > > > (email/jira) or even better just fix the problem.
> > > >
> > > > Thanks,
> > > > Jon.
> > > >
> > > >
> > > > --
> > > > // Jonathan Hsieh (shay)
> > > > // Software Engineer, Cloudera
> > > > // jon@cloudera.com <javascript:;>
> > > >
> > >
> >
> >
> > --
> > // Jonathan Hsieh (shay)
> > // Software Engineer, Cloudera
> > // jon@cloudera.com
> >
>
Re: We haven't had a clean hadoopqa build since 10/2/13.
Posted by Elliott Clark <ec...@apache.org>.
Fixing the site build so that it doesn't take an install first seems to be
eluding me. The other option is to make the qa bot do an install. But for
that to be safe we need to make sure that the maven repositories aren't
shared on any concurrently running hadoop qa runs. Can someone with
jenkins perms see if that's already set up ?
On Wed, Dec 11, 2013 at 7:59 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
> great - the fix can be done there. I did a git bisect to find the commits
> that caused the problem and emailed the committer.
>
> On Wednesday, December 11, 2013, Ted Yu wrote:
>
> > For the site build error,
> > HBASE-9729<https://issues.apache.org/jira/browse/HBASE-9729> was
> > logged.
> >
> > I do agree with Jon that no new warnings should be introduced.
> >
> > Currently 3 new Findbugs appear in QA reports.
> >
> > Cheers
> >
> >
> > On Wed, Dec 11, 2013 at 7:13 AM, Jonathan Hsieh <jon@cloudera.com
> <javascript:;>>
> > wrote:
> >
> > > Just a reminder -- we do not want to introduce new javadoc warnings,
> > > findbugs warnings, or break the docs/site compile. Please clean up
> after
> > > you commits! If you are committing something else and a warning shows
> > up,
> > > please investigate enough in order ping to the committer responsible
> > > (email/jira) or even better just fix the problem.
> > >
> > > Thanks,
> > > Jon.
> > >
> > >
> > > --
> > > // Jonathan Hsieh (shay)
> > > // Software Engineer, Cloudera
> > > // jon@cloudera.com <javascript:;>
> > >
> >
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
> // jon@cloudera.com
>
Re: We haven't had a clean hadoopqa build since 10/2/13.
Posted by Jonathan Hsieh <jo...@cloudera.com>.
great - the fix can be done there. I did a git bisect to find the commits
that caused the problem and emailed the committer.
On Wednesday, December 11, 2013, Ted Yu wrote:
> For the site build error,
> HBASE-9729<https://issues.apache.org/jira/browse/HBASE-9729> was
> logged.
>
> I do agree with Jon that no new warnings should be introduced.
>
> Currently 3 new Findbugs appear in QA reports.
>
> Cheers
>
>
> On Wed, Dec 11, 2013 at 7:13 AM, Jonathan Hsieh <jon@cloudera.com<javascript:;>>
> wrote:
>
> > Just a reminder -- we do not want to introduce new javadoc warnings,
> > findbugs warnings, or break the docs/site compile. Please clean up after
> > you commits! If you are committing something else and a warning shows
> up,
> > please investigate enough in order ping to the committer responsible
> > (email/jira) or even better just fix the problem.
> >
> > Thanks,
> > Jon.
> >
> >
> > --
> > // Jonathan Hsieh (shay)
> > // Software Engineer, Cloudera
> > // jon@cloudera.com <javascript:;>
> >
>
--
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com
Re: We haven't had a clean hadoopqa build since 10/2/13.
Posted by Ted Yu <yu...@gmail.com>.
For the site build error,
HBASE-9729<https://issues.apache.org/jira/browse/HBASE-9729> was
logged.
I do agree with Jon that no new warnings should be introduced.
Currently 3 new Findbugs appear in QA reports.
Cheers
On Wed, Dec 11, 2013 at 7:13 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
> Just a reminder -- we do not want to introduce new javadoc warnings,
> findbugs warnings, or break the docs/site compile. Please clean up after
> you commits! If you are committing something else and a warning shows up,
> please investigate enough in order ping to the committer responsible
> (email/jira) or even better just fix the problem.
>
> Thanks,
> Jon.
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
> // jon@cloudera.com
>