Mike,
Jenkins runs automated tests on each pull request, and i think this is a
good thing.
recently, it reported a bunch of failure but i could not find anything
to blame in the PR itself.
so i created a dummy PR https://github.com/open-mpi/ompi/pull/264 with
git commit --allow-empty
and waited
how about if I will disable the failing test(s) and make jenkins to pass?
It will help us to make sure we don`t break something that did work before?
On Tue, Nov 11, 2014 at 7:02 AM, Gilles Gouaillardet <
gilles.gouaillar...@iferc.org> wrote:
> Mike,
>
> Jenkins runs automated tests on each pull
Mike,
that will remove the false positive, but also remove an important piece
of information :
there is something wrong with the master.
would you mind discussion this on the weekly call ?
Cheers,
Gilles
On 2014/11/11 17:38, Mike Dubman wrote:
> how about if I will disable the failing test(s)
ok, I disabled vader tests in SHMEM and it passes.
it can be requested from jenkins by specifying "vader" in PR comment line.
On Tue, Nov 11, 2014 at 11:04 AM, Gilles Gouaillardet <
gilles.gouaillar...@iferc.org> wrote:
> Mike,
>
> that will remove the false positive, but also remove an importan
Thanks Mike,
BTW what is the distro running on your test cluster ?
Mike Dubman wrote:
>ok, I disabled vader tests in SHMEM and it passes.
>
>it can be requested from jenkins by specifying "vader" in PR comment line.
>
>
>On Tue, Nov 11, 2014 at 11:04 AM, Gilles Gouaillardet
> wrote:
>
>Mike,
>
rhel6.4
we can provide ssh access to interested parties.
On Tue, Nov 11, 2014 at 2:01 PM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:
> Thanks Mike,
>
> BTW what is the distro running on your test cluster ?
>
> Mike Dubman wrote:
> ok, I disabled vader tests in SHMEM and it passe
