yetus-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Dimiduk <ndimi...@gmail.com>
Subject Re: Running test-patch locally omits unit tests
Date Mon, 11 Nov 2019 23:44:00 GMT
Thanks for the pointer; I don't think I would have found this. Certainly
there's no mention of test running in the --help output regarding
--robot/sentinel.

On Fri, Nov 8, 2019 at 4:42 PM Sean Busbey <busbey@apache.org> wrote:

> It's on purpose. If you pass the cli option:
>
> --run-tests
>
> Then it'll run unit tests. The option is also activated by --robot and
> --sentinel
>
>
> I'm not sure if it's triggered by the auto CI system detection.
>
> For humans it's covered by the very end of the intro section on "enabling
> features"
>
>
> http://yetus.apache.org/documentation/0.11.1/precommit-basic/#enabling-features
>
> On Fri, Nov 8, 2019, 13:12 Nick Dimiduk <ndimiduk@apache.org> wrote:
>
> > Hi folks,
> >
> > I've been trying to get a usable Yetus invocation for a local equivalent
> of
> > HBase's GH pre-commit bot. I'm mostly there, running in a linux VM with
> the
> > various static analysis tools, but it's not running the unit tests. The
> > summary tells me the unit module is indeed considered, but --debug gives
> me
> > no indication as to why a plugin is consider or not, is skipped or not.
> >
> > Any ideas? How do I debug this further? I can post my scripts in a gist
> if
> > that's useful (there's likely a fair bit of HBase-specific stuff,
> starting
> > with our custom personality).
> >
> > Thanks,
> > Nick
> >
>

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