=== sem2peie- is now known as sem2peie | ||
=== guiverc2 is now known as guiverc | ||
=== sem2peie- is now known as sem2peie | ||
=== sem2peie- is now known as sem2peie | ||
=== sem2peie- is now known as sem2peie | ||
=== sem2peie- is now known as sem2peie | ||
=== sem2peie- is now known as sem2peie | ||
rbasak | ahasenack: fancy reviewing https://code.launchpad.net/~racb/git-ubuntu/+git/usd-importer/+merge/440324 for me please? | 14:19 |
---|---|---|
ahasenack | sure | 14:20 |
liushuyu | Hi there, I need a new attempt for the autopkgtest tried, the links follow: | 22:04 |
liushuyu | https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=ormar&trigger=python-databases%2F0.7.0-1&trigger=sqlalchemy%2F1.4.46%2Bds1-1build1 | 22:04 |
liushuyu | https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=python-databases&trigger=sqlalchemy%2F1.4.46%2Bds1-1build1 | 22:04 |
liushuyu | --end of links. This is to break the migration dependency cycle: ormar -> python-databases -> sqlalchemy -> ormar | 22:05 |
liushuyu | Thank you in advance! | 22:05 |
liushuyu | And also, can someone retry https://launchpad.net/ubuntu/+source/sccache/0.4.0~~pre7-1/+build/25585940 this build on armhf? There was a compiler OOM during the local linking phase (where rustc links the object files within one library) | 22:09 |
bdmurray | Only the first autopkgtest link worked. The second one failed b/c `Package python-databases does not have any test results` | 22:14 |
bdmurray | I should be able to sort that out | 22:14 |
bdmurray | I've retried the sccache build for you | 22:15 |
bdmurray | Actually, I can't (or won't right now!) sort out running python-databases autopkgtests because there aren't any! | 22:16 |
liushuyu | bdmurray: I see. So something has to do the initial run before manually triggered run could be performed? | 22:20 |
bdmurray | liushuyu: no, the package python-databases doesn't contain any autopkgtests - somebody would need to write some | 22:20 |
liushuyu | Oh I see | 22:21 |
liushuyu | That's probably why the issue wasn't discovered in the python-databases package | 22:21 |
liushuyu | The sccache package failed with out of memory again. Should I add this package to https://git.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-package-configs/tree/big_packages this list? | 22:44 |
bdmurray | No, the package build environment (Launchpad) is different than the autopkgtest environment. The autopkgtest-package-configs affects the latter. | 22:46 |
bdmurray | liushuyu: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/o/ormar/20230406_221837_d2d10@/log.gz passed | 23:42 |
liushuyu | bdmurray: Yay. And sqlalchemy, ormar and python-databases migrated altogether | 23:45 |
liushuyu | For sccache, is there a procedure to make the builder increase the RAM limitation alone? | 23:46 |
cjwatson | No | 23:47 |
cjwatson | Also it's probably not actually about the amount of physical RAM that the builder has, given that it only failed on armhf | 23:48 |
cjwatson | It's more likely to be that it's a 32-bit architecture so it's running in a 4GB address space or smaller | 23:49 |
athos | Hey! Could any ubuntu-archive admin check LP: #2002861 and promote isc-kea and log4cplus? | 23:49 |
-ubottu:#ubuntu-devel- Launchpad bug 2002861 in isc-kea (Ubuntu) "[MIR] promote isc-kea to main" [Undecided, In Progress] https://launchpad.net/bugs/2002861 | 23:49 | |
cjwatson | liushuyu: ^ There is nothing that Launchpad can do to change that. The package will need to be changed to use compiler/linker options that use less memory (or else give up on building on 32-bit arches) | 23:50 |
liushuyu | cjwatson: Okay, I will see how I can make the compiler use less memory | 23:51 |
cjwatson | Yeah, in some cases in the past this has been possible, but I don't know the specifics here | 23:52 |
liushuyu | Well, turning off LTO should be the first angle of attack | 23:53 |
cjwatson | Sounds wise | 23:54 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!