Re: Second Jammy Jellyfish test rebuild
On Tue, Mar 29, 2022 at 8:02 AM Graham Inggs wrote: > > Hi Christian > > On Tue, 29 Mar 2022 at 08:19, Christian Ehrhardt > wrote: > > - Dns-root-data is actually an issue in ldns fixed in jammy-proposed > ldns migrated, so I retried dns-root-data > > > - postgresql-14 was broken by llvm-14, a fix is uploaded to jammy and > > built fine (https://launchpad.net/bugs/1966319) > llvm-toolchain-14 migrated, so I retried postgresql-14 https://launchpad.net/ubuntu/+source/postgresql-14/14.2-1ubuntu1 in proposed fixes the FTBFS with llvm 14. > > > - python-tempita was broken by python-3.10, not yet fixed but we know a way > not doing anything here yet https://launchpad.net/ubuntu/+source/python-tempita/0.5.2-6ubuntu1 is in proposed and fixes the FTBFS (and enables tests, that were not running before) -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: Second Jammy Jellyfish test rebuild
Hi Christian On Tue, 29 Mar 2022 at 08:19, Christian Ehrhardt wrote: > - Dns-root-data is actually an issue in ldns fixed in jammy-proposed ldns migrated, so I retried dns-root-data > - postgresql-14 was broken by llvm-14, a fix is uploaded to jammy and > built fine (https://launchpad.net/bugs/1966319) llvm-toolchain-14 migrated, so I retried postgresql-14 > - python-tempita was broken by python-3.10, not yet fixed but we know a way not doing anything here yet > - samba shows to build fine in the latter 0ubuntu4 samba should move to the superseded section once it migrates > - Mysql is one of the !log cases this seems to have been cleared by my previous retries > - Ruby-rexml is fixed for a few days already before the report was sent. > Please consider rebuilding all orange ruby* packages (reference LP: > #1966201). retrying... Regards Graham -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: Second Jammy Jellyfish test rebuild
On Fri, Mar 25, 2022 at 3:24 PM Graham Inggs wrote: > > The latest report, dated 2022-03-25 14:05:01 UTC, no longer has broken > links to build logs that do not exist. Instead, '!Log' is shown for > these. Hi Graham, we've resolved all of our issues by now. I do not know if you need to get your list trimmed down, after all that will need you to build things again and sometimes resources are scarce. So this is an FYI for you if you want/need to trim the list via rebuilds/refreshes/deletions-form-your-ppa. We initially had more and fixed a few, but the currently remaining list holds 5 entries left for the server team: - Dns-root-data is actually an issue in ldns fixed in jammy-proposed by ldns https://launchpad.net/ubuntu/+source/ldns/1.7.1-2ubuntu4 You could consider a rebuild against proposed to get this one green. - postgresql-14 was broken by llvm-14, a fix is uploaded to jammy and built fine (https://launchpad.net/bugs/1966319) You can rebuild the very same, or if you have a less-overhead way to do it just consider this one as done. - python-tempita was broken by python-3.10, not yet fixed but we know a way - Note it’s an openstack package - not server anymore, but we wanted to fix it anyway. - https://launchpad.net/bugs/1966323 - https://bugs.launchpad.net/ubuntu/+source/python-tempita/+bug/1966532 - https://code.launchpad.net/~ahasenack/ubuntu/+source/python-tempita/+git/python-tempita/+merge/417740 - samba shows to build fine in the latter 0ubuntu4 - https://launchpad.net/ubuntu/+source/samba/2:4.15.5~dfsg-0ubuntu4 - consider to remove or rebuild it yourself to pick it up - Mysql is one of the !log cases - we didn't want to trigger a rebuild on our side just to ask you to do one again (wasted time) - instead could you please just rebuild that in your ppa as it should actually be good already I know I said 5, but as a bonus: - Ruby-rexml is fixed for a few days already before the report was sent. Please consider rebuilding all orange ruby* packages (reference LP: #1966201). -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: Second Jammy Jellyfish test rebuild
The latest report, dated 2022-03-25 14:05:01 UTC, no longer has broken links to build logs that do not exist. Instead, '!Log' is shown for these. -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: Second Jammy Jellyfish test rebuild
On Thu, Mar 24, 2022 at 07:44:11AM -0700, Erich Eickmeyer wrote: > I'm seeing a lot of failed arm64 builds without build logs. In the > past when I've seen this, I've merely retried the build and it has > succeeded. This shows a pattern in that it's likely we've got a buggy > build server. Yeah, this has been reported to us (Launchpad), but for the record we have no handle on a fix at present. The basic symptom is that buildd-manager timed out trying to poll the builder (probably over several attempts). This is either because the builder crashed or hung or something like that (possible under load, and sometimes particular builds will repeatedly OOM a builder or similar), or because of a network failure that meant we lost contact for too long, or because of a buildd-manager bug. Unfortunately it's extremely difficult even for us to tell which at present. Ubuntu test rebuilds tend to exacerbate this sort of thing, because the whole system is under significantly more load than usual. It's something that we'll keep trying to debug, but it's not as simple as a single buggy build machine, and so I want to set expectations that this may not be something we can fix quickly. -- Colin Watson (he/him) [cjwat...@ubuntu.com] -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: Second Jammy Jellyfish test rebuild
On Thursday, March 24, 2022 6:05:06 AM PDT Graham Inggs wrote: > The second test rebuild of Jammy Jellyfish was started on March 17, > 2022 for all architectures, all components. The rebuild is finished > for the main component, and finished for universe/multiverse on amd64 > and i386, and still running on the other architectures. > > Results (please also look at the superseded builds) can be found at > > https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220317-jamm > y-jammy.html > > A number of builds failed without logs, and these will be retried. > > Additional build failures for packages in jammy-proposed (not yet > migrated to jammy) can be found at > > http://qa.ubuntuwire.com/ftbfs/ > > Please help fixing the build failures. > > Graham I'm seeing a lot of failed arm64 builds without build logs. In the past when I've seen this, I've merely retried the build and it has succeeded. This shows a pattern in that it's likely we've got a buggy build server. -- Erich Eickmeyer Project Leader - Ubuntu Studio Member - Ubuntu Community Council signature.asc Description: This is a digitally signed message part. -- kubuntu-devel mailing list kubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
