On 02/18/2016 10:22 AM, Daniel Mack wrote:
I disagree. All sorts of testing is good for us, and if a PR is breaking downstream Ubuntu, and we recognize that before merging, that's really great.
I'm all for more testing the better but due to downstream fragmentation all these have the same fundamental problem as are with multiple downstream issue trackers.
In this case you start slowing down integration if PR start failing in one or more downstreams ( Arch,Coreos, Debian,Fedora,Mageia,Ubuntu etc and need to start spending time researching if the failure is downstream specific and during that time the PR will be in frozen state ) and you risk those test system(s) start reporting directly upstream ( which can lead to fun things like this [1] ) since people will quickly think "I'm just going to have all failures and errors reported directly upstream instead of having to inspect/deal with downstream myself" and those thing start small like with "CI test -- don't merge!"
JBG 1. https://bugzilla.redhat.com/show_bug.cgi?id=1300212 _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
