tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Wohlstadter <wohls...@cs.ubc.ca>
Subject Fwd: Switched PreCommit-Admin over to Apache Yetus
Date Fri, 19 Jan 2018 00:01:02 GMT
I think we may be experiencing this problem on Tez JIRA (failure of
PreCommit-Admin hook).

Has anyone tried submitting a patch in the last few days?

My patch submissions aren't triggering test results ...

If anyone knows how to fix this, that would be awesome. Otherwise I can
reach out to people.

---------- Forwarded message ----------
From: Vihang Karajgaonkar <vihang@cloudera.com>
Date: Tue, Jan 16, 2018 at 7:40 PM
Subject: Re: Switched PreCommit-Admin over to Apache Yetus
To: dev <dev@hive.apache.org>
Cc: Allen Wittenauer <aw@effectivemachines.com>

Thanks Allen for fixing the precommit-admin job.


The issue with precommit hive job reported in
https://issues.apache.org/jira/browse/HIVE-18461 is fixed as well. So
automated precommit tests should be back for Hive. Incase your patch didn't
make the precommit tests during this downtime, you will need to reattach
the patch again so that it gets triggered in the next run.


On Tue, Jan 16, 2018 at 6:15 PM, Allen Wittenauer <aw@apache.org> wrote:

> bcc: builds@apache.org, dev@hbase.apache.org, dev@hive.apache.org,
> common-dev@hadoop.apache.org, dev@phoenix.apache.org, dev@oozie.apache.org
>         (These are all of the projects that had pending issues.  This is
> not all of the groups that actually rely upon this code...)
>         The recent JIRA upgrade broke PreCommit-Admin.
>         This breakage was obviously an unintended consequence.  This
> python code hasn’t been touched in a very long time.  In fact, it was
> coming from Hadoop SVN tree as it had never been migrated to git.  So it
> isn’t too surprising that after all this time something finally broke it.
>         Luckily, Apache Yetus was already in the progress of adopting it
> for a variety of reasons that I won't go into here.  With the breakage,
> this work naturally became more urgent.  With the help of the Apache Yetus
> community doing some quick reviews, I just switched PreCommit-Admin over
> using the master version of the equivalent code in the Yetus source tree.
> As soon as the community can get a 0.7.0 release out, we’ll switch it over
> from master to 0.7.0 so that it can follow our regular release cadence.
> This also means that JIRA issues can be filled against Yetus for bugs seen
> in the code base or for feature requests.  [Hopefully with code and docs
> attached. :) ]
>         In any case, with the re-activation of this job, all unprocessed
> jobs just kicked off.  So don't be too surprised by the influx of
>         As a sidenote, there are some other sticky issues with regards to
> precommit setups on Jenkins.  I'll be sending another note in the future
> that though. I've had enough excitement for today. :)
>         Thanks!

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