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, relating to run time being too long to be tracked by concourse, so we just let it through as a pass. I think this is a bad signal. I think that this should automatically be a failure in the short term. As a result, I also think it should not be required. It is a bad signal, and I think that by making it a fail, this will at least not give us a false sense of security. I understand that this opens the flood gates so to speak, but I don’t think as a community it is a big problem because we can still say that you should not merge if the StressNewTest fails because of your test. I personally find the false sense of security more troubling than anything. Hence the reason, I would like this to be Let me know what you think.. Thanks, Mark
