[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Odil : getting back into testing



I'm increasingly of the opinion that we should not stretch our limited resources even thinner by spending so much time on architectures used for network routers where it is unlikely that anyone will want to view medical image files.

În vin., 4 ian. 2019 la 18:40, Julien Lamy <lamy@unistra.fr> a scris:
Hi all,
The latest version of Odil does not build on mips64el [1] and if I'm not
mistaken, this is the only thing preventing the package to migrate to
testing. By going through the logs, one of the unit tests times out when
building [2]. Since I don't have access to a real mips64el box, I've
tested building in a Qemu guest and got similar results: the build also
fails with a timeout, albeit earlier in the process.

I've watched the RAM during the Qemu build ("grep Committed_AS
/proc/meminfo"), and it is getting nowhere the limit at this point of
the build, which makes me think that this is not caused by a RAM
problem. The configuration of the Qemu guest differs from the official
builder due to Qemu limitations (less RAM, non-parallel build), so this
is not the best test setup, and I'm unsure on how to fix this. The three
options I've thought of are rather unsatisfactory:

- Don't build the unit tests. Later build steps are however much more
resource-intensive, so this will probably not solve the problem
- Increase the build timeout. Not sure whether asking to reconfigure the
buildd network for a package with such a low popcon is a good idea :)
- Don't build Odil on mips64el

What would be your advice in this situation ?

[1] https://buildd.debian.org/status/package.php?p=odil&suite=sid
[2] test_webservices_WADORSRequest has a start message ("Building CXX
object"), but no end message ("Built target")

Cheers,
--
Julien



--
Michael R. Crusoe
Co-founder & Lead, Common Workflow Language project
Direktorius, VšĮ "Darbo eigos", Vilnius, Lithuania

Reply to: