On Tue, Feb 10, 2015 at 10:33 AM, Loic Dachary <loic@xxxxxxxxxxx> wrote: > > > On 10/02/2015 19:25, Gregory Farnum wrote: >> >> Now, as it happens there are some reasons to maintain a dumpling >> branch that isn't part of backports. We've been doing a lot of work >> lately to make the nightlies behave well under RHEL and in various >> other environments, which sometimes involve changing the tests >> themselves. That can mean updating the ceph.git/qa/workunits in our >> LTS branches, which I've done a few times over the last couple of >> months. Since they're used for testing they aren't suitable for going >> through a backports workflow, we just want them to get into the >> nightlies as fast as possible. Tossing out any such work every time a >> point release appears would be irritating, to say the least. >> (We could also pull the workunits out of ceph.git, but that's a >> different discussion.) > > This is a good point. I'm assuming backports rely on the dumpling branch of ceph-qa-suite. And if a change needs to be done in ceph-qa-suite for the benefit of an ongoing backport effort to publish a point release, it will have to be done in such a way that it can work for both the current dumpling and the future point release. > > Am I understanding you correctly ? No, I mean we are (unfortunately) actually changing the ceph.git dumpling branch in order to update the tests we run so they succeed in new environments. Those changes aren't going through backports testing, because we want to verify that they're working in our regular nightlies ASAP and don't want to wait for the backports branch to merge for them to take effect in giving us successful tests. Look at...wow, pick a commit on the first screen of the current dumpling branch. Also, as Sage mentions we actually run the dumpling branch in the nightlies and using that as integration testing. I think it's appropriate to keep doing so; otherwise we need to run every patch through every suite *enough times to be sure we've not added a bug that's hard to reproduce*. If we use dumpling as an integration branch for backports that can be tested en-masse but independently we get a lot more test coverage of them prior to releases. -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
