linaro-validation October 2015

linaro-validation@lists.linaro.org

4 participants
3 discussions

FYI LAVA in stretch or unstable & unit tests

by Neil Williams

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802677 This appears to only affect the unit tests in lava-server but can be confusing as the output makes it look like something more serious within django. It's not, it's in python-testtools. The solution is to downgrade python-testtools (use the version in Jessie as outlined in the bug report above). When this bug report is closed, the package can be upgraded again. -- Neil Williams ============= http://www.linux.codehelp.co.uk/

10 years, 10 months

Does deploy_linaro_kernel have a known issue of missing to setup network on fast model targets?

by Basil Eljuse

Hello All, Before I report this as a bug thought to check if this is a known issue or not. Do confirm. We were trying to use lava-test-shell in running pm-qa on AEMv8 and CortexA57xA53 model variants. Based on what we have run we could see that if we use boot_linaro_image as the image deployment mode, there are no issues, LAVA is able to run the lava-test-shell successfully. However when we use boot_linaro_kernel as the image deployment mode, we see lava-test-shell fails due to network being reported as 'down'. Is this something known already? Or should I raise a bug report? Details:: deploy_linaro_image - Attaching the exact test def for reference. Here we use the hwpack and a modified rootfs (added test suite in it) and then uses boot_linaro_image and provides some uefi boot commands through 'boot_cmds' and override some model flags using the 'options' parameter. deploy_linaro_kernel - Attaching the exact test def for reference Here we use 'boot_image' with commands through boot_cmds and model flags using 'sim_options' parameter. In the sim options even if we give "-C bp.hostbridge.interfaceName=anything", "-C bp.smsc_91c111.enabled=true", "-C bp.smsc_91c111.mac_address=00:11:22:33:44:53" It don't seem to get networking setup correctly. We could see the initial boot successful and as part of doing the lava-test-shell execution, the pre-requisite of network being up fails! Section 70<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_70> 70.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_70_0> linaro-test [rc=0]# <LAVA_DISPATCHER>2015-10-06 03:26:22 PM DEBUG: send (delay_ms=0): cd /tmp 70.1<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_70_1> <LAVA_DISPATCHER>2015-10-06 03:26:22 PM DEBUG: send (delay_ms=0): Section 71<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_71> 71.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_71_0> Section 72<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_72> 72.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_72_0> <LAVA_DISPATCHER>2015-10-06 03:26:22 PM DEBUG: expect (600): 'linaro-test \[rc=(\d+)\]# ' Section 73<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_73> 73.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_73_0> cd /tmp Section 74<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_74> 74.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_74_0> linaro-test [rc=0]# <LAVA_DISPATCHER>2015-10-06 03:26:23 PM INFO: Waiting for network to come up 74.1<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_74_1> <LAVA_DISPATCHER>2015-10-06 03:26:23 PM DEBUG: send (delay_ms=0): LC_ALL=C ping -W4 -c1 10.1.99.203 74.2<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_74_2> <LAVA_DISPATCHER>2015-10-06 03:26:24 PM DEBUG: send (delay_ms=0): Section 75<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_75> 75.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_75_0> Section 76<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_76> 76.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_76_0> <LAVA_DISPATCHER>2015-10-06 03:26:24 PM DEBUG: expect (60): '['1 received|1 packets received', '0 received|0 packets received', 'Network is unreachable']' Section 77<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_77> 77.0<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_77_0> LC_ALL=C ping -W4 -c1 10.1.99.203 77.1<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_77_1> PING 10.1.99.203 (10.1.99.203): 56 data bytes 77.2<http://ssg-sw.cambridge.arm.com/lava/scheduler/job/4541/log_file#L_77_2> ping: sendto: Network is unreachable Note: Attaching only the test definitions in the email, let me know if full logs from the successful and failed runs needs to be shared, or I do that via big report if it is confirmed so. Thanks Basil Eljuse... -- 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

10 years, 10 months

Android multinode test definitions update

by Milosz Wasilewski

Hi, I merged CTS and lava-android-test target test defintions into a single YAML file. It can be (in most cases) used as target side for any Android multinode test. In this case test are executed from host side using adb. Host test definitions will be different for each side, but target side can be unified. Here is a patch for this fix: https://review.linaro.org/#/c/8031/ If you have any concerns, please feel free to comment. This patch makes the following files obsolete: android/cts-target.yaml android/lava-android-test-target.yaml I will update all test plan templates to use the new definition. Obsolete files will be removed in 15.11 release. Best Regards, milosz

10 years, 10 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation October 2015