[389-devel] Re: Build failed in Jenkins: 389-DS-NIGHTLY #165

2017-02-16 Thread William Brown
> >> > > I know that everyone is busy. > > > > But in our team we have a policy that new patches should not be pushed > > if tests are not green. > Your tests are obviously more stable than ours. In fact our "nightly > tests" are a fairly new process. We were even hesitant to start doing > this

[389-devel] Re: Build failed in Jenkins: 389-DS-NIGHTLY #165

2017-02-16 Thread Mark Reynolds
On 02/16/2017 06:11 AM, Lukas Slebodnik wrote: > On (16/02/17 09:50), William Brown wrote: >> On Wed, 2017-02-15 at 08:16 -0500, Mark Reynolds wrote: >>> On 02/15/2017 04:48 AM, Lukas Slebodnik wrote: On (15/02/17 09:05), Jenkins wrote: > See >

[389-devel] Re: Build failed in Jenkins: 389-DS-NIGHTLY #165

2017-02-16 Thread Lukas Slebodnik
On (16/02/17 09:50), William Brown wrote: >On Wed, 2017-02-15 at 08:16 -0500, Mark Reynolds wrote: >> >> On 02/15/2017 04:48 AM, Lukas Slebodnik wrote: >> > On (15/02/17 09:05), Jenkins wrote: >> >> See >> >> >> >> >>

[389-devel] Re: Build failed in Jenkins: 389-DS-NIGHTLY #165

2017-02-15 Thread Mark Reynolds
On 02/15/2017 04:48 AM, Lukas Slebodnik wrote: > On (15/02/17 09:05), Jenkins wrote: >> See >> >> > Is there a reason why jenkins failures are ignored for a week? With our VERY limited resources, and other higher pri

[389-devel] Re: Build failed in Jenkins: 389-DS-NIGHTLY #165

2017-02-15 Thread Lukas Slebodnik
On (15/02/17 09:05), Jenkins wrote: >See > > Is there a reason why jenkins failures are ignored for a week? LS ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org