Hi,
Is there a way to override the constants or variables that are in the python code from the job definition or device dictionary? For example, the UBOOT_AUTOBOOT_PROMPT has the default value of 'Hit any key to stop autoboot' but my board displays 'Press SPACE to abort autoboot in 2 seconds'. Changing it in the code works but I was wondering if there is a more generic way of doing it. Perhaps a parameter I can send to the boot action from the job definition?
Thanks,
Josue
Hi,
I ran a simple LTP-DDT test case that produces the following output http://pastebin.ubuntu.com/21280373/.
Is there a way to parse this output so that it shows up in results section of the dashboard as a pass. I know you can call lava-test-case from within the script and do the parsing inside the script, but I want to do this for many different test cases. Is there an easier way to do it without changing the test cases?
I tried the parsing in the test definition as follows http://pastebin.ubuntu.com/21280894/.
I will appreciate any help, thanks.
Josue
Hey all,
We've started experimenting with lava V2 jobs in our lava lab. Thusfar
things are going well but it seems there is no ability to specify
device tags nor to specific target device in V2 thusfar. Is support for
those something that's still in the pipeline :) ?
--
Sjoerd Simons
Collabora Ltd.
Hi,
For example, if I create a test that is supposed to run on the beaglebone black and another evm, is there a way to specify that I want to run a specified test only on the beaglebone and not on the other evm? I'm guessing that's why it's required to add device-type to a job definition, correct?
So if I want to test multiple devices with the same test definition I have to run a different job for each one of the devices?
Also, does lava allow to run commands on the host (PC) along with the target (beaglebone)?
I will appreciate a response.
Thanks,
Josue
Hi,
I'm having an issue where the board (beaglebone-black) starts the booting process using the u-boot commands that I specify but gets interrupted before it gets to the "am335x-evm login:" login prompt. I get the following exception http://pastebin.ubuntu.com/19177228/. Any known fix for this issue?
This is the complete boot log section of the pipeline actions http://pastebin.ubuntu.com/19177444/. Also, my YAML job definition can be found here http://pastebin.ubuntu.com/19177546/.
I will appreciate a response.
Thanks,
Josue
Hi all,
I have a PDU working with the lava instance and a beglebone-black connected to the server.
When I submit a job, it successfully deploys a linaro kernel and when trying to boot the test image I get the error that is attached.
It seems as it is not entering the setenv command.
Thanks,
Josue
On Fri, 1 Jul 2016 15:21:22 +0000
"Albarran, Josue" <j-albarran(a)ti.com> wrote:
Please keep the list in CC:
> Ok, thanks for the information.
>
> So what is the mayor difference between YAML and JSON job submissions?
Completely new design. JSON submissions are LAVA V1 only. YAML submissions are LAVA V2 only.
See the documentation in your localhost for the differences between LAVA V1 and LAVA V2.
> Are JSON jobs being superceded by YAML ones in the future?
Yes - the migration is happening now and JSON submissions will be blocked during 2017.
> The objective is to be able to use new LAVA v2 instance to perform
> daily functional tests (ltp-ddt tests). This has to be using the LAVA
> UI.
>
> Is it better if I stick to the JSON job submissions for now?
No. Unless your particular devices are not yet supported in V2, you need to be using V2.
>
> Thanks,
>
> Josue Albarran
>
> -----Original Message-----
> From: linaro-validation
> [mailto:linaro-validation-bounces@lists.linaro.org] On Behalf Of Neil
> Williams Sent: Friday, July 01, 2016 3:56 AM To:
> linaro-validation(a)lists.linaro.org Subject: Re: [Linaro-validation]
> Lava v2 and YAML job support
>
> On Thu, 30 Jun 2016 21:41:15 +0000
> "Albarran, Josue" <j-albarran(a)ti.com> wrote:
>
> > Hi,
> >
> > I'm new to LAVA I'm trying to get LAVA v2 working and installed in
> > order to boot/kernel test a beaglebone black for now. I installed
> > the full LAVA set following the steps from the 2016.6 server
> > documentation. It doesn't seem like I have YAML job support as it's
> > asking for a JSON job definition in the scheduler as well as the
> > lava-tool.
>
> Currently, there is no V2 support for submitting jobs via the Submit
> Job menu UI. lava-tool or XML-RPC (for automated submissions) only
> for V2.
>
> > How can I confirm that I have LAVA v2 installed and be able to
> > submit jobs in YAML format to the localhost server of LAVA?
>
> The device detail page shows what jobs the device can support.
>
> e.g.
> https://staging.validation.linaro.org/scheduler/device/staging-black01
>
> Pipeline: staging-black01 accepts both pipeline and JSON jobs.
>
> This is determined from the database and configured through the
> django administrative interface. For each pipeline device, the
> Pipeline device? checkbox must be set and a Device Dictionary
> imported.
>
> The device should also show up on the list of pipeline devices:
>
> e.g.
> https://staging.validation.linaro.org/scheduler/alldevices/pipeline
>
> We're expanding the documentation in this area. You may find this
> proposed page useful:
> https://git.linaro.org/lava/lava-server.git/commitdiff/12f0b078186b319db9df…
>
>
> --
>
>
> Neil Williams
> =============
> http://www.linux.codehelp.co.uk/
>
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
Hi,
I'm new to LAVA I'm trying to get LAVA v2 working and installed in order to boot/kernel test a beaglebone black for now. I installed the full LAVA set following the steps from the 2016.6 server documentation. It doesn't seem like I have YAML job support as it's asking for a JSON job definition in the scheduler as well as the lava-tool. How can I confirm that I have LAVA v2 installed and be able to submit jobs in YAML format to the localhost server of LAVA?
Thanks.
Josue
The master branch of lava-server has now moved to a requirement for
django 1.8 or better. (1.9 is available in Debian unstable and
testing, 1.8 from jessie-backports.)
To install or upgrade lava-server on jessie, python-django and
python-django-tables2 must be installed from jessie-backports.
Once master is merged into staging and then into release for the next
production release, this change will affect all builds of lava-server
available for Debian other than 2014.9 already in jessie. All users of
lava-server are strongly recommended to upgrade from 2014.9 for
security and bug fix support in the underlying django code.
Installations using jessie-backports are fully supported and will
become the requirement after the next production release.
django1.7 is now out of upstream support whilst django1.8 retains
upstream support and updates through backports until at least April
2018.
https://www.djangoproject.com/download/
lava-dispatcher is unaffected.
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
