[Bug 1260012] Re: app snapshot during test setup is being set to an empty list
Dimitri John Ledkov
launchpad at surgut.co.uk
Wed Dec 18 22:34:04 UTC 2013
On 18 December 2013 19:51, Thomi Richards <1260012 at bugs.launchpad.net> wrote:
> Ahh, I understand now :)
>
> The application snapshot is retrieved from the bamf daemon over dbus. I
> wonder if what's happening is that sometimes bamf isn't running in your
> test environment, and the act of getting the process snapshot start it,
> but it doesn't pick up on existing windows?
>
ubiquity is probably the most atypical autopilot tested project =)
bamf may or may not be running, may possibly not even be installed and
certainly not available over dbus.
ubiquity supports following Desktop Environments:
- ubiquity-dm
- unity
- gnome-shell
- gnome-panel
- XFCE
- LXDE
- and maybe others
Also ubiquity, when running under autopilot, is already past
re-executing with pkexec and thus has all environment cleaned and is
running as root. At which point a private root session DBus is
started, and autopilot is launched as root into that same DBus
session. I expect no Bamf, or any initial / other DBus services be
privileged to peak into that envrionemnt / windows.
> Are you able to check if it's running? What environment are your tests
> running in? I assume it's a reasonably minimal X environment?
>
At the moment, all of the above are running under X org, either
minimal or more-or-less full desktop environment.
I don't think we need or require an application snapshot from bamf
daemon over dbus. Under full unity desktop session, i believe we do
have a launcher icon and/or maybe a progress bar (can't remember of
top of my head) but is very non-essential parts of ubiquity. At the
moment, our autopilot tests excercise the installer itself to an
acceptable level which replaces majority of the manual test-cases /
scenarios required to pass for milestone image release. This bug at
the moment, is one of the blockers for release team to start mandating
autopilot tests passing across all image flavours.
Regards,
Dimitri.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1260012
Title:
app snapshot during test setup is being set to an empty list
Status in Autopilot:
Incomplete
Status in “ubiquity” package in Ubuntu:
New
Bug description:
During the Ubiquity autopilot tests we are getting frequent fails
where get_running_applications() is not picking up Ubiquity as a
running application and is setting the app snapshot to an empty list
then when it comes to comparing the snapshot the test is failing as
its now detected ubiquity is running.
The test runner launches ubiquity and waits 30 seconds before starting
the test, so slow app loading time isn't an issue here
see https://jenkins.qa.ubuntu.com/view/Ubiquity/view/Ubuntu/job
/ubiquity_ap-ubuntu_devel_daily-
test_nonenglish_encrypt_lvm/ARCH=i386,label=rabisu/lastCompletedBuild/testReport/ubiquity_autopilot_tests.tests.test_nonenglish_encrypt_lvm/LVMEncryptInstallTestCase/test_lvm_encrypt_install/
This doesn't occur on every run but i could manage to reproduce it
locally 1 in every 5/6 runs 'ish'.
Steps to try and reproduce
1) branch lp:ubiquity
2) make sure qemu and bsdtar are installed and have a daily iso (Ubuntu, Ubuntu-GNOME and Edubuntu currently working)
3) from dir ./ubiquity/autopilot/ubiquity-autopilot-runner execute using the configfile attached to this bug
./run-ubiquity-test -T/path/to/debug_config.cfg ./path/to/trusty-
desktop.iso
4) test artifacts are stored in /tmp/ubiquity.tests
If you want additional artifacts or additional autopilot options or
even stop the VM shutting down for debugging you can change the config
file accordingly
You can also use the --sdl param if you want to view the desktop. All
other test runner info can be found in the README if needed
I will also attach the autopilot.log file that shows the app snapshot
is empty, see 14.18 time interval
If any other info is needed contact myself or jibel
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1260012/+subscriptions
More information about the foundations-bugs
mailing list