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) 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 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 for Jenkins to do its job. >> >> the test failed, which means there is an issue in the master. >> from the master point of view, it is good to know there is an issue. >> from the PR point of view, this is a false positive since the PR does >> nothing wrong. >> >> i was unable to find anything on github that indicates the master does >> not pass the automated tests. >> is such automated test running vs the master ? if yes, where can we find >> the results ? >> in order to avoid dealing with false positive, is there any possibility >> to disable automated tests on the PR >> if the master does not pass the tests ? >> >> Cheers, >> >> Gilles >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2014/11/16283.php >> > > > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/11/16284.php
