gsequencer fails autopkg tests on anything except amd64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gsequencer (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
gsequencer (1.4.34-1 to 2.1.34-1)
Maintainer: Debian Multimedia Maintainers
Section: universe/misc
15 days old
autopkgtest for gsequencer/
The Debian maintainer provided this analysis:
The qemu image has only 1 GB RAM assigned. This is not enough, I was able to
reproduce the failure with 1 GB RAM, as wanting to obtain a stack-trace with GDB
it complained, that it can't allocate memory.
After assigning 8 GB of RAM the functional tests all passed on i386.
By the way I would love to mark the functional tests as flaky (see DEP-8)
https:/
If we would package a more recent version of GSequencer we would be able
to run the unit-tests during autopkgtest.
Note, there 2 different types of tests unit-tests and functional
integration-tests. The
later are not mandatory to pass at my opinion. Especially if the VM
doesn't get enough
computing power. I have seen VMs taking more than 2 seconds to show a GtkMenu,
if the delay is too long (not enough computing power) the tests aren't
reliable anymore.
To target this issue, I had to adjust the timeouts and delays. Yes,
the tests could run much
faster. But I decided to throttle them, to target environments will
lesser CPU resources than
I have on my workstation.
Here is the reaction time specified:
Here are the unit-tests to run against the installation:
http://
This is new for autopkgtest and not yet available:
Changed in gsequencer (Ubuntu): | |
status: | New → Fix Released |
asked on #ubuntu-release:
<vorlon> gsequencer> why did it manage to run on amd64 without running out of memory?