/srv/irclogs.ubuntu.com/2020/12/08/#launchpad.txt

cjwatsonBut actually not now that I look harder, because sbuild also runs debian/rules clean at the start of the binary package build.00:00
realtime-neiland the prepending of the changelog happens before this, right?00:01
cjwatsonIndeed00:01
realtime-neilyep, the broken clean rule is eating the changelog message00:01
realtime-neilfantastic, now the source upload is failing because the kernel wants to rewrite its own debian/changelog during the build00:04
realtime-neilI really don't want to clean up this packaging, but I want to contend with the ubuntu kernel packaging even less00:05
realtime-neilwait, that actually worked00:07
cjwatsonrewrite its own debian/changelog> /me hides under the duvet00:08
realtime-neilcjwatson: yeah. Yeah, it's not the best. but these are kernel devs, so....?00:08
cjwatsonI'm not going to throw rocks in case they throw them back at my inefficient userspace code00:09
realtime-neilconcur00:09
Fudgehowdy all07:33
mwhudsonsigh, now i have a build running out of disk space07:42
mwhudsoncjwatson, wgrant: how much disk do builders have? it's not smaller for xenial or anything insane like that, right?07:44
Fudgeworse luck, is your /var/cache full?07:50
ricotzhello, looks like many amd64 are silently failing currently (at least the ones my builds are getting assigned to) -- builds of https://launchpad.net/~mozillateam/+archive/ubuntu/ppa/+packages08:34
* ricotz retried them now08:34
cjwatsonmwhudson: 60G08:59
cjwatsonmwhudson: and there's no difference between series, no08:59
mwhudsoncjwatson: is there any way to see how much disk a succesful build used?09:00
mwhudsonwonder if my failing build is just nudging over that (it fails pretty close to the end) or something bad is happening09:01
ricotzmwhudson, afaik at the end of a successful build-log the used disk space is shown09:02
cjwatsonYeah, sbuild shows it, though I think it's only what's left at the end rather than the high-water mark (in case a build removes intermediary outputs along the way)09:02
cjwatsonThat's the best available though09:02
mwhudsonlaunchpad builds say "build-space: n/a" :/09:04
mwhudson https://launchpadlibrarian.net/510323509/buildlog_ubuntu-bionic-s390x.rustc_1.47.0+dfsg1+llvm-1ubuntu1~18.04.1~ppa1_BUILDING.txt.gz for example (warning a bit large)09:04
cjwatsonricotz: Fixed now09:40
cjwatson(lcy01's ntp was down)09:40
dokomwhudson: Build needed 03:10:53, no disk space ;p09:40
mwhudsondoko: i think this may be a lie09:41
dokoyou should be happy about such an efficient compiler09:42
ricotzcjwatson, thank you10:06
=== ddstreet_away is now known as ddstreet
=== ijohnson is now known as ijohnson|lunch
=== ijohnson|lunch is now known as ijohnson
rbasakIs Launchpad git expected to be slow at the moment?22:29
rbasakIf not, libvirt could looks like it could use a repack please.22:30
rbasakAh22:30
rbasakfatal: write error: No space left on device2.76 MiB | 3.31 MiB/s22:30
rbasakfatal: index-pack failed22:30
rbasakThat's just from a clone22:30
rbasakAh, and not the main libvirt, but ~paelzer's libvirt22:30
* rbasak tries again22:31
* pappacena got scaried about that "no space left on device"22:31
rbasakYeah I think that means something's broken22:32
rbasakOh22:53
rbasakThat's local22:53
rbasak(to me)22:56
rbasakFetch is still really slow though22:57
pappacenaI did a git pull here, and it seems to be ok to me. Load average seems to me normal on the machines. Is your network fine for other things?22:58
rbasakYeah my network is fine.22:59
rbasakIt's not bandwidth22:59
rbasakremote: Counting objects:  40% (150223/375557)22:59
rbasakThat's the sort of place it gets stuck at22:59
rbasakBefore any real transfer takes place22:59
rbasakHaving said that, something just changed and it's suddenly normal speed22:59
cjwatsonOur git performance graphs look normal, except for a minor spike at 2300 ish23:33
cjwatsonBut file a ticket with the URL to the repository to repack and we can ask for that23:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!