Re: [PROPOSAL] StressNewTest in Pull Request Pipeline to be made optional.

2020-02-28 Thread Nabarun Nag
What help is needed in this effort? Regards Naba On Fri, Feb 28, 2020 at 11:35 AM Mark Hanson wrote: > Alright, so basically it seems like people are not ok with the not > requiring stressnewtest approach. So I guess that means that we need to > identify -1s willing to help resolve this problem

Re: [PROPOSAL] StressNewTest in Pull Request Pipeline to be made optional.

2020-02-28 Thread Mark Hanson
Alright, so basically it seems like people are not ok with the not requiring stressnewtest approach. So I guess that means that we need to identify -1s willing to help resolve this problem… Who would like to help? Thanks, Mark > On Feb 28, 2020, at 11:12 AM, Ernest Burghardt wrote: > > -1 to

Re: [PROPOSAL] StressNewTest in Pull Request Pipeline to be made optional.

2020-02-28 Thread Ernest Burghardt
-1 to limiting any tests... if there are issues with the tests let's fix that. we have too many commits coming in with little or no testing over new/changed code, so I can't see how removing any existing test coverage as a good idea Best, EB On Fri, Feb 28, 2020 at 10:58 AM Mark Hanson wrote:

Re: [PROPOSAL] StressNewTest in Pull Request Pipeline to be made optional.

2020-02-28 Thread Mark Hanson
Just to make sure we are clear, I am not suggesting that we disable stressnewtest, but that we make it not required. It would still run and provide feedback, but it would not give us an unwarranted green in my approach. > On Feb 28, 2020, at 10:49 AM, Ju@N wrote: > > +1 to what Owen said, I do

Re: [PROPOSAL] StressNewTest in Pull Request Pipeline to be made optional.

2020-02-28 Thread Ju@N
+1 to what Owen said, I don't think disabling *StressNewTest* is a good idea. On Fri, 28 Feb 2020 at 18:35, Owen Nichols wrote: > -1 to making StressNew not required > > +1 to eliminating the current loophole — StressNew should never give a > free pass. > > Any time your PR is having trouble pas

Re: [PROPOSAL] StressNewTest in Pull Request Pipeline to be made optional.

2020-02-28 Thread Owen Nichols
-1 to making StressNew not required +1 to eliminating the current loophole — StressNew should never give a free pass. Any time your PR is having trouble passing StressNew, please bring it up on the dev list. We can review on a case-by-case basis and decide whether to try increasing the timeo

[PROPOSAL] StressNewTest in Pull Request Pipeline to be made optional.

2020-02-28 Thread Mark Hanson
Hi All, Proposal: Force StressNewTest to fail a change with 25 or more files rather than pass it without running it. Currently, the StressNewTest job in the pipeline will just pass a job that has more than 25 files changed. It will be marked as green with no work done. There are reasons, relat