-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/22/2010 04:14 PM, Adam Williamson wrote: > That would likely be an improvement, but have you thought through the > interaction issues? Builds are rarely standalone, so we need to figure > out which builds go with which other builds so they can be tested > together. Or we can test an entire Rawhide push at one time, but in that > case, which package do you block if the automated test fails? All of > them? Pick one at random? Try and write heuristics so AutoQA can figure > out which package to block?
The way I was thinking is this. There would be two tags, rawhide and rawhide-pending. the rawhide tag (or whatever it is an alias for) is where things go that have passed autoqa. rawhide-pending is where things go that have not yet passed auto-qa, and is the first stop after a build. When things land in rawhide-pending an autotest run is ran in two stages. One stage just uses what's currently in rawhide. If it passes, let it through. If it fails, do another stage that includes all the packages in rawhide /and/ rawhide-pending for it's repodata. If the package passes it will have to be marked as requiring something that is in -pending and not in rawhide yet. Insert some magic here. It isn't going to be perfect, but it'll definitely be better than what we have now. - -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkyaGzoACgkQ4v2HLvE71NUaiACggUis0yoy8WIUeN5m1XkAjMX1 raUAn30Tx48M8pY2BGtc+XE6FFBQcQbh =6zdx -----END PGP SIGNATURE----- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
