linaro-validation

linaro-validation@lists.linaro.org

818 discussions

by Milosz Wasilewski

Hi, There is an ongoing review that will update binary files used to execute rt-tests: https://github.com/Linaro/test-definitions/pull/85 My plan is to merge this patch today. If you still depend on running tests with old files they will be available using 2019.07 tag which I created yesterday. milosz

5 years, 5 months

How to contribute to test-definitions?

by Daniel Wagner

Hi, I've started to setup my local lava instance with the goal to do my stable-rt tests as maintainer. My initial setup is starting to work and now I am looking at existing tests for lava.I've found a few basic tests in test-definitions. I figure all those tests relegated to preempt-rt need some love since the parameters used for cyclictest are not really recommended. I've started to change a few things [1] and would like to contribute them back, but I don't know what the correct way is. Should I send patches here, or do I need to do PR ong it.lavasoftware.org? Thanks, Daniel [1] https://github.com/igaw/test-definitions/commit/3e41080f2daa4ba30268e5a701f…

6 years

moving test-definitions repository to github

by Milosz Wasilewski

Hi, In order to make it easier to contribute we decided to move test-definitions.git to github. Github repository will be the 'master' one and it will be synced back to git.linaro.org. So if you're using the git.linaro.org repository for running tests, nothing changes for you. There is no plan to remove this repository. However we won't be able to accept patches through gerrit review now. All patches should be submitted as github pull requests. To sum up: 1. git.linaro.org/qa/test-definitions.git is now read-only 2. github.com/Linaro/test-definitions.git is where the changes can be submitted 3. all changes from github/Linaro/test-definitions.git are synced back to git.linaro.org/qa/test-definitions.git Best Regards, Milosz Wasilewski

6 years

Project qa/test-definitions moved to Github Linaro/test-definitions

by Chase Qi

Hi, We are seeing more and more contributor from outside of Linaro on the project, then we decided to move it to https://github.com/Linaro/test-definitions to make contributing easier. https://git.linaro.org/qa/test-definitions.git is a read-only mirror of the Github repo now. New changes in the Github repo will be pushed to the mirror every 10 minutes. https://review.linaro.org/#/admin/projects/qa/test-definitions also has been set to read-only. Please use Github for pull requests: https://github.com/Linaro/test-definitions/pulls Thanks, Chase

6 years

ptest.py script seems to generate not really informative results

by Oleksandr Terentiev

Hi, I launched util-linux ptest using automated/linux/ptest/ptest.yaml from https://git.linaro.org/qa/test-definitions.git and received the following results: https://pastebin.com/nj9PYQzE As you can see some tests failed. However, case util-linux marked as passed. It looks like ptest.py only analyze return code of ptest-runner -d <ptest_dir> <ptest_name> command. And since ptest-runner finishes correctly exit code is 0. Therefore all tests are always marked as passed, and users never know when some of the tests fail. Maybe it worth to analyze each test? Best regards, Alex

6 years, 1 month

how to migrate job logs/data (deployment_data_dict)

by Alexander Couzens

Hi, I can not access any old job data, which was created before the update to 2018.11. The yaml parser has problems to parse the deployment_data_dict class, which does not exist anymore (commit 5903343d4086cff36048ffaa885b010d9d1f9887). Is there a way to migrate the data? I'm wondering that no one actually run into this case before. Best, lynxis PS. I'm using the debian backports repo. django.log: ERROR 2018-12-02 04:23:10,627 utils Unable to parse description for 3129 ERROR 2018-12-02 04:23:10,628 utils while constructing a Python object cannot find 'deployment_data_dict' in the module 'lava_dispatcher.deployment_data' in "/var/lib/lava-server/default/media/job-output/2018/12/02/3129/description.yaml", line 68, column 24 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_results_app/utils.py", line 93, in description_data data = yaml.load(open(filename, 'r'), Loader=V2Loader) File "/usr/lib/python3/dist-packages/yaml/__init__.py", line 72, in load return loader.get_single_data() File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 37, in get_single_data return self.construct_document(node) File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 46, in construct_document for dummy in generator: File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 398, in construct_yaml_map value = self.construct_mapping(node) File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 204, in construct_mapping return super().construct_mapping(node, deep=deep) File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 129, in construct_mapping value = self.construct_object(value_node, deep=deep) File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 91, in construct_object data = next(generator) File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 575, in construct_python_object instance = self.make_python_instance(suffix, node, newobj=True) File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 552, in make_python_instance cls = self.find_python_name(suffix, node.start_mark) File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 529, in find_python_name % (object_name, module.__name__), mark) -- Alexander Couzens mail: lynxis(a)fe80.eu jabber: lynxis(a)fe80.eu mobile: +4915123277221 gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604

6 years, 1 month

auto_login to support password re-entry

by Chan, Aaron Chun Yew

Hi Linaro Validation, I have a used case where by during auto_login the Clear OS, we have 1st password prompt and follow by 2nd password prompt to verity the password creation is set properly. I would like to know if the current dispatcher scripts is able to support this use case, whereby a second password prompt is expected follow by the a second password re-entry. Let me know your thoughts on where I can start with this if there is a need to add in an extra key into the boot action methods. Currently if I used this on my LAVA Job it returns me with this error: Invalid definition: extra keys not allowed @ data['actions'][1]['boot']['auto_login']['password_prompt_retry'] auto_login: { login_prompt: 'login:', username: root, password_prompt: 'Password:', password: password123, password_prompt_retry: 'New Password:', password_reentry: password123 } Regards, Chan, Aaron SSG Embedded Linux - Yocto Project Contact : +6042536861 Location: PG12/L1/A318

6 years, 3 months

removing 'android' and 'common' directories from test-definitions

by Milosz Wasilewski

Hi, This was planned a long time ago but as I remember there were still users of the tests from 'android' and 'common' directories. At this point all relevant tests should had been migrated to new path (automated/android, automated/linux). If no concerns are raised I will remove 'android' and 'common' from the repository on last day of May 2018. Before that, I will create a tag so it will be easier to find the legacy tests. Best Regards, Milosz

6 years, 8 months

LKFT HiKey - R1

by Dave Pigott

Hi all, Early last week we transitioned all but one of the LKFT HiKeys to the new hikey-r2 device type, which essentially means we upgraded the firmware to build 55 and switched the device type support. We left one as a hikey-r1 device type, just to catch any stray submissions. It had now been 6 days since any job was submitted to this device type, so I’m asking if anyone knows any reason why we shouldn’t migrate this last device to hikey-r2 device support? If I don’t hear any objections in the next 24 hours I’ll assume it is okay to migrate it. Thanks Dave ---------------- Dave Pigott LAVA Lab Lead Linaro Ltd t: (+44) (0) 1223 400063

6 years, 9 months

simple ssh device boot up.

by Thomas Klaehn

Hello, I'm quite new to Lava. As a companion device for a network test I need to just boot up a device (raspberry), login (ssh) and start a tool. No deployment is needed. The switch on/off is still working. As far as I understood my device dictionary needs to extend ssh.jinja, isn't it? Beside the power commands - which parameter I need to define here? And what do I need to define in the Lava test job? I assume something like this is still solved. Is there probably an example available? Best regards, Thomas

6 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation