On Mon, 2022-06-13 at 08:32 +0200, Milan Crha wrote: > On Fri, 2022-06-10 at 08:33 -0700, Adam Williamson wrote: > > Possibly. I'm not sure what the timeout on chain builds in Koji is. > > But yes, that's a scenario worth looking at. > > Hi, > if I recall correctly, it's around 2 hours (by default). > > > What if there were a command like chain-build that uses a side tag? > > Puts each build into a side tag as it goes, then when all the builds > > are done, automatically creates the update from the side tag? > > As Kevin mentioned in the other mail in this thread, one can --target > the chain build too (and I use it for things like "f36-gnome"). Having > this all done in a single command would be preferred, thus there are > less things to think of from the packager point of view. > > I see a little similarity with the scratch-build's --srpm argument. One > can pass the srpm file name to it, but if it doesn't pass it, then the > fedpkg builds the .srpm in the current folder and uses it as the srpm > for the scratch build. That's quite convenient and helps to avoid > mistakes. > > If it's going to happen, then I agree to have added a new argument for > the chain-build, to be able to cover both scenarios: 1) as it's now, > just build packages in certain order and do not do anything else; > 2) the new one, create a side tag, build packages in it, fill automated > update (when it's a rawhide build) once all the packages are built. As > things can fail, the side tag should be re-usable, thus one can > continue the build from follow up build(s), but that feels natural. > > This all looks like a concatenation of several fedpkg commands, as you > mentioned. > > > That's a Fedora CI test, not an openQA one. > > Aha. I thought those Automated Tests attached to the update are it. > Where does one see the openQA tests results, please? The Automated Tests tab shows all test results from *both* Fedora CI and openQA that appear relevant to the update (i.e. are "for" the update itself or for any NVR it includes). There's a few ways you can tell which results are from which system. Results from Fedora CI have names that start with "fedora-ci.". Results from openQA have names that start with "update.". Currently, results from openQA are always considered to be tests of "the update", so they show up under the update title (e.g. FEDORA-2022-6d2c62d6d6). Results from Fedora CI are always considered to be tests of "a specific package", so they show up under the name of a package in the update (e.g. systemd-249.12-4.fc35 ). If you want to look at openQA update test results directly in openQA's own interface, you can go to https://openqa.fedoraproject.org/group_overview/2 (or go to the front page and click "Fedora Updates"), where you'll find all x86_64 update test results. You can see up to the last 400 by clicking the little number links under the initial list of 10. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/desktop@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
