On 02/18/2014 01:28 AM, Lukáš Doktor wrote: > master. It can happened, but in an odd matter which wouldn't be > detectable by boot test (eg. windows 2007 installation vs 2003).
Ahh, yes, and IMHO this actually happens much more that you'd believe. It's why the CI grid testing we do on master is SOOOOOO important. It's unreasonable to ask test/core developers and reviewers to run more than a quick/simple set. However possible impact to others is big. > If we found ways to detect these easily, we can add these directly into > check_patch and voila the responsibility is right on the developer. IIRC, there's a submit-hook on github that can be set to poke a REST API for you, with the issue/PR number, etc. That could be used to trigger a grid job that sucks down the pull requests from github if it contains a recent '**ready for CI**' flag comment. Then it could run a larger set of tests on them and post the results back as a comment. Maybe stand up a simple REST API on openshift (to get a fixed URL and DNS name), then query it from the grid? -- Chris Evich, RHCA, RHCE, RHCDS, RHCSS Quality Assurance Engineer e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214 _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
