On 12/08/2015 10:25 AM, Kaushal M wrote: > We already have devrpms jobs which test building rpms, so building > rpms again seems unnecessary. > > The reason I'm asking this is because I'm facing issues trying to get > this working in the saltstack configured environment I'm fixing. I > don't see what's specifically wrong with the test, but it just doesn't > seem to work. So, I was wondering why even run it. IIRC, it's just to test that glusterfs.spec(.in) didn't break. Is it the devrpm job's job to build rpms for the following tests? Or is it actually a test that the .spec didn't break? Or is the implicit test that the .spec didn't break just a side-effect? And does it matter which? ;-) -- Kaleb _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
