# Progress #
* LAVA-851 - Initial wip patch submitted for nested-vms
* #1292522 - Fixed role for actions in lava-dispatcher
* #1292522 - Fixed/Tested role for actions in lava-server
* correct fix production hot-fix (workaround) for state transitions
* various code reviews
* Time
* LAVA-851 - 50%
* #1292522 - 10%
* state transition fix - 20%
* various code reviews - 20%
# Plan #
* LAVA-851 - continue with nested vms work
--
Senthil Kumaran
http://www.stylesen.org/http://www.sasenthilkumaran.com/
# Progress #
* LAVA-944 - completed django-tables2 fixes for LAVA
* LAVA-933 - LAVA django1.6 patches up for review.
* CARD-1255 - Hidden device types, initial local changes and new unit
tests, not finalised for review yet.
* CARD-1073 - community support, updating packaging helpers, LAVA on
ARM testing using arndale
* #1294613 - can't cancel a users job when their email invalid, in review.
* #1294344 - public filter table fix
* Time
* LAVA-944 - 20%
* LAVA-933 - 20%
* CARD- 1255 - 20%
* CARD-1073 - 20%
* Bugs: 20%
* Other/Misc - Linaro GSoc14
# Plan #
* LAVA-1123 - finalise
* LAVA-849 - Support running virtual machines on devices under test -
supporting Antonio & Senthil where requested.
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
# Progress #
* [LAVA-943]
* Remove bug link icon from the front end UI of test run table to let it
be consist with image report 1.0 & 2.0
* Working on test case table
# Plan #
* [LAVA-943]
* To let test case table be able to link bug
# Issues #
* No issues
Hi,
I'm trying to communicate between 2 multinode jobs and send some short
messages. The docs say that the key-value pairs are stored in the
/tmp/lava_multi_node_cache.txt file. So I was expecting something
like:
my_key=my_value
or:
my_key: my_value
What I'm getting is:
sending-device-name:my_key=my_value
Is this the expected output and the documentation is just not detailed
enough? Or I'm getting buggy output in the cache file?
milosz
Re: Message-ID: <20140223143441.293e5997(a)sylvester.codehelp>
https://bugs.launchpad.net/lava-server/+bug/1271527
> The bug is due to be fixed soon - at which point tags which are *not*
> supported by the instance to which the job is submitted will cause the
> job submission to *fail*. This is so that device tags can be used to
> dictate which devices actually run the TestJob.
The bug fix has now been merged and will soon be available on
staging.validation.linaro.org
There are a few more updates to make elsewhere in tip but this change
will now be part of the next production rollout to
validation.linaro.org.
If you have not checked all of your JSON templates for device_tags, now
is the time to do it.
Any device_tags in JSON files after this rollout must be supported in
the database for the instance - suitable devices must exist with the
specified tags or your submission will fail.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
