I went to the Ottawa Linux Symposium and heard several good talks on
testing and performance. One of the outstanding ones (to me) was the
University of Waterloo and their testing apparatus and harness for doing
testing for performance and the application of statistical analysis to the
testing, as a one-time test may not show the true results.
They have a mechanism, and a lab, that allows people to build code for
testing, run the tests with supplied data, and then statistically analyse
the data to see.
It has a front end that allows you to supply the information necessary to
build your project, then distributes it to a number of different machines
to run for a selected number of times. Even though you may be running the
same data through, they can show that various other factors will vary
performance as much as 15% on a given run of the test data.
The project URL is here:
https://uwaterloo.ca/embedded-software-group/datamill
I asked them for a copy of their slides, which I have uploaded to a Google
Drive and will make a link available to anyone who wishes to see them.
My thoughts on this are that Linaro might want to study what they have done
and build this type of analysis into Lava, or perhaps the University of
Waterloo would like to incorporate parts of Lava into their back end, or
the two groups could work together. I have sent them pointers to Lava web
pages from the Linaro site.
At a minimum, we might find that making machines attached to a Lava
instance available to the University's DataMill program (perhaps through a
gateway) would increase the amount of visibility and testing available to
Linaro's customer systems.
Warmest regard,
maddog
Hi All,
I was wondering if you could help me please?
I have been trying to add a new fastmodel variation to LAVA but I am seeing issues when attempting to interrupt the boot prompt. LAVA seems to be expecting to see the "linaro-test" prompt rather than "The default boot selection will start in" which is what I have set for the interrupt_boot_prompt variable. As a result of this UEFI attempts to boot the default selection and my jobs fail, as the defaults aren't valid.
I suspect I have misconfigured my new device, so I just wanted to check that, other than setting the interrupt_boot_prompt variable to something sensible in my device config, is there anything else I need to set to force LAVA to interrupt the boot prompt?
I have attached the log from my job along with my config files in case I have done something wrong when adding the device.
Thanks for your time
Dean
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
# Done #
* Fix bug #359 - Possible regression in multinode device_tags selection
* PEP8 and other unit test warning fixes
* Cleanup hostname status images both for workers and devices.
* cards - 30%
* bugs - 20%
* code reviews - 10%
# Progress #
* LAVA-1488: View JobTable without health checks.
* LAVA-1495: Show tags, if any, in the devices list table ...
* LAVA-1373: DH: LDAP - LAVA - REQ-374
# Plan #
* Complete patch for LAVA-1373: LAVA LDAP
* Formulate couple of REQs that are in queue for review
* Prepare for connect
--
Senthil Kumaran
http://www.stylesen.org/http://www.sasenthilkumaran.com/
# Done #
* LAVA-1410: LC: allow PPAs within lava-test-shell dependencies
* LAVA-1503: Formulate the YAML syntax for PPAs / apt sources
* LAVA-1504: Scripts for adding sources in debian
* LAVA-1505: Scripts for adding sources in ubuntu
* LAVA-1506: Documentation explaining the new parameters for PPA ...
* LAVA-1507: Scripts for adding gpg keys
* LAVA-1488: View JobTable without health checks.
* LAVA-1495: Show tags, if any, in the devices list table ...
* Fix bug #388 - staging-kvm08 device is in running status while the job ..
* cards - 70%
* bugs - 10%
* code reviews - 20%
# Progress #
* LAVA-1373: DH: LDAP - LAVA - REQ-374
* debug problems for QA team
# Plan #
* Continue with pending cards and bugs
--
Senthil Kumaran
http://www.stylesen.org/http://www.sasenthilkumaran.com/