Hi, All
I have updated the enable_network_after_boot_android definition in file /srv/lava/instances/production/etc/lava-dispatcher/device-defaults.conf for production
Just added the following two lines:
# This is for android build where the network is not up by default. 1 or 0 enable_network_after_boot_android = 1
here just a notice.
BTW, where is the lava source deployed? when I run find command in the /srv/lava/instances/production directory, I can't find the source files of lava-dispatcher
Thanks, Yongqin Liu
On 07/03/2012 02:15 AM, YongQin Liu wrote:
BTW, where is the lava source deployed? when I run find command in the /srv/lava/instances/production directory, I can't find the source files of lava-dispatcher
Things are different now with buildout. I'll try and explain, but Michael is the more authoritative source on this. A deployment layout relative to /srv/lava/instances/<instance>/ now looks like:
code/rXX # one per deployment update made code/rXX/eggs # a symlink to /srv/lava/.cache/eggs code/current # a symlink to the current level like "r36" bin/ # a symlink to code/current/bin
This leaves us with an interesting directory, /srv/lava/.cache/eggs. This directory has a version of every package we've deployed.
So how do we choose the right package version? Take a look at a file like "bin/lava". It actually adds each egg defined by that deployment to the path.
Hope this helps.
-andy
linaro-validation@lists.linaro.org