Lava-users September 2018

lava-users@lists.linaro.org

12 participants
16 discussions

Setting tags for existing devices via command line

by Tim Jaacks

Hello everyone, is there a way of setting tags for existing devices via the command line? The "lava-server manage devices update" command does not have a "--tags" parameter, as the "lava-server manage devices add" has. Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com SOLUTIONS THAT COMPLETE! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz

6 years, 2 months

Does deploy action have such as "deploy-namespace" to indicate to use previous deploy images?

by john zhang

In lava job definition, boot action can use "connection-namespace" to indicate use previous namespace's connection.Does deploy action have such as "deploy-namespace" to indicate to use previous deploy image? For example in an application scenario, it need to sequential execution two phases pipeline(deploy,boot,test), it can be solved by define two namespace in job definiton. When run it executed in serial as : phase1(namespace1) deploy->boot->test -> phase2(namespace2) deploy->boot->test. If phase2 deploy images(kernel,dtb,rootfs) are exactly same as phase2 deploy images,how to speed up phase2 deploy execution? I guess if deploy action have such as "deploy-namespace" to indicate previous deploy,then phase2 deploy process can be pass.

6 years, 2 months

does LXC devices mean LXC can emulate various arm devices peripheral interfaces?

by chao yang

https://validation.linaro.org/static/docs/v2/admin-lxc-deploy.html#lxc-depl… , It say that LXC devices can run lava tests within a container without disturbing the dispatcher host. Does LXC support the arm device? Although LXC may supports to run the arm virtual machine in PC server,but how does it support the completed arm device(Including various peripheral interfaces eg ethernet,usb.. ) ? Because the test job often test various peripheral interfaces,Is LXC emulating these interfaces?

6 years, 2 months

job stuck after disconnection

by Corentin Labbe

Hello We got a job (number 332) stuck in running state. After 23h of inaction, the only way to stop it was to cancel+fail it. According to the logs, a small disconnection happen between the slave and master. The slave seems to try to update the final status of the job but the master "ignore" it. Regards This is the slave logs: 2018-09-21 21:45:57,197 INFO [332] Starting job2018-09-21 21:45:57,226 DEBUG [332] device : actions: 2018-09-21 21:45:57,227 DEBUG [332] env-dut : 2018-09-21 21:45:57,241 DEBUG START_OK(332) => master 2018-09-21 21:46:17,260 DEBUG PING => master (last message 20s ago) 2018-09-21 21:46:17,453 DEBUG master => PONG(20) 2018-09-21 21:46:37,475 DEBUG PING => master (last message 20s ago) 2018-09-21 21:46:37,684 DEBUG master => PONG(20) 2018-09-21 21:46:57,708 DEBUG PING => master (last message 20s ago) 2018-09-21 21:47:03,603 DEBUG master => PONG(20) 2018-09-21 21:47:23,625 DEBUG PING => master (last message 20s ago) 2018-09-21 21:47:41,199 DEBUG master => PONG(20) 2018-09-21 21:48:01,222 DEBUG PING => master (last message 20s ago) 2018-09-21 21:48:19,372 DEBUG master => PONG(20) ## 2018-09-21 21:48:39,395 DEBUG PING => master (last message 20s ago) ## 2018-09-21 21:48:59,418 DEBUG PING => master (last message 40s ago) ## 2018-09-21 21:49:19,441 DEBUG PING => master (last message 60s ago) 2018-09-21 21:49:34,458 INFO [332] Job END ## 2018-09-21 21:49:34,487 DEBUG END(332) => master 2018-09-21 21:49:39,496 WARNING Master goes OFFLINE 2018-09-21 21:49:39,496 DEBUG PING => master (last message 80s ago) 2018-09-21 21:49:39,501 INFO [332] Job END (resend) 2018-09-21 21:49:39,515 DEBUG END(332) => master 2018-09-21 21:49:44,521 INFO [332] Job END (resend) 2018-09-21 21:49:44,538 DEBUG END(332) => master 2018-09-21 21:49:49,544 INFO [332] Job END (resend) 2018-09-21 21:49:49,559 DEBUG END(332) => master 2018-09-21 21:49:54,565 INFO [332] Job END (resend) 2018-09-21 21:49:54,588 DEBUG END(332) => master 2018-09-21 21:49:59,594 DEBUG PING => master (last message 100s ago) 2018-09-21 21:49:59,594 INFO [332] Job END (resend) 2018-09-21 21:49:59,612 DEBUG END(332) => master 2018-09-21 21:50:04,618 INFO [332] Job END (resend) 2018-09-21 21:50:04,639 DEBUG END(332) => master 2018-09-21 21:50:09,645 INFO [332] Job END (resend) 2018-09-21 21:50:09,659 DEBUG END(332) => master 2018-09-21 21:50:14,665 INFO [332] Job END (resend) 2018-09-21 21:50:14,685 DEBUG END(332) => master 2018-09-21 21:50:19,690 DEBUG PING => master (last message 120s ago) 2018-09-21 21:50:19,691 INFO [332] Job END (resend) 2018-09-21 21:50:19,708 DEBUG END(332) => master 2018-09-21 21:50:24,714 INFO [332] Job END (resend) 2018-09-21 21:50:24,735 DEBUG END(332) => master 2018-09-21 21:50:29,741 INFO [332] Job END (resend) 2018-09-21 21:50:29,755 DEBUG END(332) => master 2018-09-21 21:50:34,761 INFO [332] Job END (resend) 2018-09-21 21:50:34,776 DEBUG END(332) => master 2018-09-21 21:50:39,781 DEBUG PING => master (last message 140s ago) 2018-09-21 21:50:39,782 INFO [332] Job END (resend) 2018-09-21 21:50:39,800 DEBUG END(332) => master 2018-09-21 21:50:44,806 INFO [332] Job END (resend) 2018-09-21 21:50:44,823 DEBUG END(332) => master 2018-09-21 21:50:49,829 INFO [332] Job END (resend) 2018-09-21 21:50:49,850 DEBUG END(332) => master 2018-09-21 21:50:54,856 INFO [332] Job END (resend) 2018-09-21 21:50:54,876 DEBUG END(332) => master 2018-09-21 21:50:59,882 DEBUG PING => master (last message 160s ago) 2018-09-21 21:50:59,883 INFO [332] Job END (resend) 2018-09-21 21:50:59,901 DEBUG END(332) => master 2018-09-21 21:51:04,907 INFO [332] Job END (resend) 2018-09-21 21:51:04,920 DEBUG END(332) => master 2018-09-21 21:51:09,926 INFO [332] Job END (resend) 2018-09-21 21:51:09,939 DEBUG END(332) => master 2018-09-21 21:51:14,945 INFO [332] Job END (resend) 2018-09-21 21:51:14,967 DEBUG END(332) => master 2018-09-21 21:51:19,973 DEBUG PING => master (last message 180s ago) 2018-09-21 21:51:19,974 INFO [332] Job END (resend) 2018-09-21 21:51:19,994 DEBUG END(332) => master 2018-09-21 21:51:25,000 INFO [332] Job END (resend) 2018-09-21 21:51:25,020 DEBUG END(332) => master 2018-09-21 21:51:30,026 INFO [332] Job END (resend) 2018-09-21 21:51:30,047 DEBUG END(332) => master 2018-09-21 21:51:35,053 INFO [332] Job END (resend) 2018-09-21 21:51:35,071 DEBUG END(332) => master 2018-09-21 21:51:40,077 DEBUG PING => master (last message 200s ago) 2018-09-21 21:51:40,077 INFO [332] Job END (resend) 2018-09-21 21:51:40,095 DEBUG END(332) => master 2018-09-21 21:51:45,101 INFO [332] Job END (resend) 2018-09-21 21:51:45,123 DEBUG END(332) => master 2018-09-21 21:51:50,129 INFO [332] Job END (resend) 2018-09-21 21:51:50,149 DEBUG END(332) => master 2018-09-21 21:51:55,154 INFO [332] Job END (resend) 2018-09-21 21:51:55,175 DEBUG END(332) => master 2018-09-21 21:51:58,639 DEBUG master => PONG(20) 2018-09-21 21:51:58,640 INFO Master is ONLINE 2018-09-21 21:51:58,831 DEBUG master => PONG(20) 2018-09-21 21:51:58,833 DEBUG master => PONG(20) 2018-09-21 21:52:00,053 INFO master => END_OK(332) 2018-09-21 21:52:00,054 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,062 DEBUG master => PONG(20) 2018-09-21 21:52:00,062 INFO master => END_OK(332) 2018-09-21 21:52:00,063 DEBUG [332] Unknown job 2018-09-21 21:52:00,063 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,242 INFO master => END_OK(332) 2018-09-21 21:52:00,242 DEBUG [332] Unknown job 2018-09-21 21:52:00,243 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,243 INFO master => END_OK(332) 2018-09-21 21:52:00,244 DEBUG [332] Unknown job 2018-09-21 21:52:00,244 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,244 INFO master => END_OK(332) 2018-09-21 21:52:00,245 DEBUG [332] Unknown job 2018-09-21 21:52:00,245 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,246 DEBUG master => PONG(20) 2018-09-21 21:52:00,246 INFO master => END_OK(332) 2018-09-21 21:52:00,246 DEBUG [332] Unknown job 2018-09-21 21:52:00,246 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,381 INFO master => END_OK(332) 2018-09-21 21:52:00,382 DEBUG [332] Unknown job 2018-09-21 21:52:00,382 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,436 INFO master => END_OK(332) 2018-09-21 21:52:00,436 DEBUG [332] Unknown job 2018-09-21 21:52:00,436 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,592 INFO master => END_OK(332) 2018-09-21 21:52:00,593 DEBUG [332] Unknown job 2018-09-21 21:52:00,593 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,610 DEBUG master => PONG(20) 2018-09-21 21:52:00,770 INFO master => END_OK(332) 2018-09-21 21:52:00,771 DEBUG [332] Unknown job 2018-09-21 21:52:00,771 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,892 INFO master => END_OK(332) 2018-09-21 21:52:00,892 DEBUG [332] Unknown job 2018-09-21 21:52:00,892 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,976 INFO master => END_OK(332) 2018-09-21 21:52:00,977 DEBUG [332] Unknown job 2018-09-21 21:52:00,977 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,156 INFO master => END_OK(332) 2018-09-21 21:52:01,157 DEBUG [332] Unknown job 2018-09-21 21:52:01,157 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,164 DEBUG master => PONG(20) 2018-09-21 21:52:01,170 INFO master => END_OK(332) 2018-09-21 21:52:01,171 DEBUG [332] Unknown job 2018-09-21 21:52:01,171 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,353 INFO master => END_OK(332) 2018-09-21 21:52:01,353 DEBUG [332] Unknown job 2018-09-21 21:52:01,353 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,493 INFO master => END_OK(332) 2018-09-21 21:52:01,493 DEBUG [332] Unknown job 2018-09-21 21:52:01,493 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,550 INFO master => END_OK(332) 2018-09-21 21:52:01,551 DEBUG [332] Unknown job 2018-09-21 21:52:01,551 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,552 DEBUG master => PONG(20) 2018-09-21 21:52:01,700 INFO master => END_OK(332) 2018-09-21 21:52:01,700 DEBUG [332] Unknown job 2018-09-21 21:52:01,700 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,745 INFO master => END_OK(332) 2018-09-21 21:52:01,745 DEBUG [332] Unknown job 2018-09-21 21:52:01,745 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,819 INFO master => END_OK(332) 2018-09-21 21:52:01,819 DEBUG [332] Unknown job 2018-09-21 21:52:01,820 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,936 INFO master => END_OK(332) 2018-09-21 21:52:01,936 DEBUG [332] Unknown job 2018-09-21 21:52:01,936 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,938 DEBUG master => PONG(20) 2018-09-21 21:52:02,048 INFO master => END_OK(332) 2018-09-21 21:52:02,048 DEBUG [332] Unknown job 2018-09-21 21:52:02,049 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:02,138 INFO master => END_OK(332) 2018-09-21 21:52:02,138 DEBUG [332] Unknown job 2018-09-21 21:52:02,138 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:22,160 DEBUG PING => master (last message 20s ago) 2018-09-21 21:52:37,178 INFO master => END_OK(332) 2018-09-21 21:52:37,179 DEBUG [332] Unknown job 2018-09-21 21:52:37,179 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:37,180 INFO master => END_OK(332) 2018-09-21 21:52:37,180 DEBUG [332] Unknown job 2018-09-21 21:52:37,180 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:37,181 DEBUG master => PONG(20) 2018-09-21 21:52:37,181 INFO master => END_OK(332) 2018-09-21 21:52:37,181 DEBUG [332] Unknown job 2018-09-21 21:52:37,182 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:37,374 DEBUG master => PONG(20) 2018-09-21 21:52:57,396 DEBUG PING => master (last message 20s ago) 2018-09-21 21:53:17,418 DEBUG PING => master (last message 40s ago) 2018-09-21 21:53:21,421 DEBUG master => PONG(20) 2018-09-21 21:53:21,610 DEBUG master => PONG(20) 2018-09-21 21:53:41,632 DEBUG PING => master (last message 20s ago) 2018-09-21 21:54:01,653 DEBUG PING => master (last message 40s ago) 2018-09-21 21:54:05,695 DEBUG master => PONG(20) 2018-09-21 21:54:05,893 DEBUG master => PONG(20) 2018-09-21 21:54:25,911 DEBUG PING => master (last message 20s ago) 2018-09-21 21:54:45,933 DEBUG PING => master (last message 40s ago) 2018-09-21 21:54:51,497 DEBUG master => PONG(20) 2018-09-21 21:54:51,692 DEBUG master => PONG(20) 2018-09-21 21:55:11,713 DEBUG PING => master (last message 20s ago) 2018-09-21 21:55:31,733 DEBUG PING => master (last message 40s ago) 2018-09-21 21:55:38,958 DEBUG master => PONG(20) 2018-09-21 21:55:39,147 DEBUG master => PONG(20) 2018-09-21 21:55:59,169 DEBUG PING => master (last message 20s ago) 2018-09-21 21:56:19,191 DEBUG PING => master (last message 40s ago) 2018-09-21 21:56:23,724 DEBUG master => PONG(20) 2018-09-21 21:56:23,927 DEBUG master => PONG(20) 2018-09-21 21:56:43,950 DEBUG PING => master (last message 20s ago) 2018-09-21 21:56:44,137 DEBUG master => PONG(20) 2018-09-21 21:57:04,159 DEBUG PING => master (last message 20s ago) 2018-09-21 21:57:04,351 DEBUG master => PONG(20) And this is the master logs: 2018-09-21 21:45:56,427 INFO scheduling jobs: 2018-09-21 21:45:56,428 DEBUG - bcm2837-rpi-3-b-32 2018-09-21 21:45:56,453 DEBUG -> rpi3-corelab-01 (Idle, Good) 2018-09-21 21:45:56,453 DEBUG |--> [332] scheduling 2018-09-21 21:45:56,459 DEBUG - dra7-evm 2018-09-21 21:45:56,464 DEBUG - qemu 2018-09-21 21:45:56,660 INFO [332] START => agl-core-lab-1 (rpi3-corelab-01) 2018-09-21 21:45:57,341 INFO [332] agl-core-lab-1 => START_OK 2018-09-21 21:45:57,773 DEBUG lava-logs => PING(20) 2018-09-21 21:46:16,711 INFO scheduling health checks: 2018-09-21 21:46:16,724 INFO scheduling jobs: 2018-09-21 21:46:16,725 DEBUG - dra7-evm 2018-09-21 21:46:16,729 DEBUG - qemu 2018-09-21 21:46:17,351 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:46:18,980 DEBUG lava-logs => PING(20) 2018-09-21 21:46:36,744 INFO scheduling health checks: 2018-09-21 21:46:36,757 INFO scheduling jobs: 2018-09-21 21:46:36,758 DEBUG - dra7-evm 2018-09-21 21:46:36,762 DEBUG - qemu 2018-09-21 21:46:37,566 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:46:48,466 DEBUG lava-logs => PING(20) 2018-09-21 21:46:56,776 INFO scheduling health checks: 2018-09-21 21:46:56,790 INFO scheduling jobs: 2018-09-21 21:46:56,791 DEBUG - dra7-evm 2018-09-21 21:46:56,795 DEBUG - qemu 2018-09-21 21:46:57,797 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:47:08,482 DEBUG lava-logs => PING(20) 2018-09-21 21:47:16,809 INFO scheduling health checks: 2018-09-21 21:47:16,822 INFO scheduling jobs: 2018-09-21 21:47:16,823 DEBUG - dra7-evm 2018-09-21 21:47:16,827 DEBUG - qemu 2018-09-21 21:47:23,718 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:47:31,521 DEBUG lava-logs => PING(20) 2018-09-21 21:47:36,841 INFO scheduling health checks: 2018-09-21 21:47:36,854 INFO scheduling jobs: 2018-09-21 21:47:36,855 DEBUG - dra7-evm 2018-09-21 21:47:36,859 DEBUG - qemu 2018-09-21 21:47:54,275 DEBUG lava-logs => PING(20) 2018-09-21 21:47:56,872 INFO scheduling health checks: 2018-09-21 21:47:56,885 INFO scheduling jobs: 2018-09-21 21:47:56,886 DEBUG - dra7-evm 2018-09-21 21:47:56,891 DEBUG - qemu 2018-09-21 21:48:01,321 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:48:14,292 DEBUG lava-logs => PING(20) 2018-09-21 21:48:16,903 INFO scheduling health checks: 2018-09-21 21:48:16,917 INFO scheduling jobs: 2018-09-21 21:48:16,918 DEBUG - dra7-evm 2018-09-21 21:48:16,922 DEBUG - qemu 2018-09-21 21:48:35,995 DEBUG lava-logs => PING(20) 2018-09-21 21:48:36,933 INFO scheduling health checks: 2018-09-21 21:48:36,946 INFO scheduling jobs: 2018-09-21 21:48:36,947 DEBUG - dra7-evm 2018-09-21 21:48:36,951 DEBUG - qemu 2018-09-21 21:48:39,486 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:48:56,011 DEBUG lava-logs => PING(20) 2018-09-21 21:48:56,962 INFO scheduling health checks: 2018-09-21 21:48:56,975 INFO scheduling jobs: 2018-09-21 21:48:56,976 DEBUG - dra7-evm 2018-09-21 21:48:56,981 DEBUG - qemu 2018-09-21 21:49:16,995 INFO scheduling health checks: 2018-09-21 21:49:17,009 INFO scheduling jobs: 2018-09-21 21:49:17,010 DEBUG - dra7-evm 2018-09-21 21:49:17,014 DEBUG - qemu 2018-09-21 21:49:21,406 DEBUG lava-logs => PING(20) 2018-09-21 21:49:37,026 INFO scheduling health checks: 2018-09-21 21:49:37,040 INFO scheduling jobs: 2018-09-21 21:49:37,041 DEBUG - dra7-evm 2018-09-21 21:49:37,046 DEBUG - qemu 2018-09-21 21:49:41,419 DEBUG lava-logs => PING(20) 2018-09-21 21:49:52,363 ERROR [STATE] Dispatcher <agl-core-lab-1> goes OFFLINE 2018-09-21 21:49:57,059 INFO scheduling health checks: 2018-09-21 21:49:57,067 INFO scheduling jobs: 2018-09-21 21:50:01,440 DEBUG lava-logs => PING(20) 2018-09-21 21:50:17,078 INFO scheduling health checks: 2018-09-21 21:50:17,086 INFO scheduling jobs: 2018-09-21 21:50:21,462 DEBUG lava-logs => PING(20) 2018-09-21 21:50:37,097 INFO scheduling health checks: 2018-09-21 21:50:37,105 INFO scheduling jobs: 2018-09-21 21:50:41,484 DEBUG lava-logs => PING(20) 2018-09-21 21:50:57,117 INFO scheduling health checks: 2018-09-21 21:50:57,125 INFO scheduling jobs: 2018-09-21 21:51:01,502 DEBUG lava-logs => PING(20) 2018-09-21 21:51:17,135 INFO scheduling health checks: 2018-09-21 21:51:17,144 INFO scheduling jobs: 2018-09-21 21:51:21,524 DEBUG lava-logs => PING(20) 2018-09-21 21:51:37,154 INFO scheduling health checks: 2018-09-21 21:51:37,162 INFO scheduling jobs: 2018-09-21 21:51:41,546 DEBUG lava-logs => PING(20) 2018-09-21 21:51:57,170 INFO scheduling health checks: 2018-09-21 21:51:57,178 INFO scheduling jobs: 2018-09-21 21:51:58,734 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:51:58,737 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:51:59,125 INFO [332] agl-core-lab-1 => END 2018-09-21 21:51:59,954 DEBUG get_type_name: skipping finalize 2018-09-21 21:51:59,954 DEBUG type_name failed for finalize metatype finalize 2018-09-21 21:51:59,954 DEBUG get_type_name: skipping finalize 2018-09-21 21:51:59,954 DEBUG type_name failed for finalize metatype finalize 2018-09-21 21:51:59,954 DEBUG get_type_name: skipping finalize 2018-09-21 21:51:59,954 DEBUG type_name failed for finalize metatype finalize 2018-09-21 21:51:59,960 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:51:59,964 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,968 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,971 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,974 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,977 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:00,093 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,287 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,341 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,493 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,496 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:00,674 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,795 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,881 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,061 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,063 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:01,075 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,256 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,397 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,453 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,456 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:01,568 DEBUG lava-logs => PING(20) 2018-09-21 21:52:01,603 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,646 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,722 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,840 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,842 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:01,884 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,985 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:02,040 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:02,106 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:02,109 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:02,220 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:17,187 INFO scheduling health checks: 2018-09-21 21:52:17,201 INFO scheduling jobs: 2018-09-21 21:52:17,202 DEBUG - dra7-evm 2018-09-21 21:52:17,207 DEBUG - qemu 2018-09-21 21:52:21,585 DEBUG lava-logs => PING(20)

6 years, 2 months

REST API

by Milosz Wasilewski

Hi, I made a first attempt to add REST API for some LAVA objects (jobs, devices and device types). The API is very rudimentary but already solves some basic job filtering issues. However I'm not sure how to add dependencies. There are 2 packages required for this code to work properly. Pip packages are named 'djangorestframework' and 'djangorestframework-filters'. Former has a corresponding debian package 'python3-djangorestframework' but the later does not. Any hints how to add proper dependencies to LAVA? The code can be found here: https://git.lavasoftware.org/mwasilew/lava/tree/rest_api milosz

6 years, 2 months

Second serial port control

by Oana Ercus

Hi everyone, I'm a newbie to LAVA, so this may be a stupid question, but I have no idea how to fix this issue. I am using a device for which I enabled the usage of the second serial port as described in the example beaglebone-black job with a second serial port - it seems that the configuration works fine, I was able to enable the secondary connection. The problem is the following: the second serial port connects to a different shell, which at this moment is used for freeRTOS application, and its prompt ("SHELL>>") is different of the primary connection prompt which is used for Linux("root@imx8mqevk"). When trying to actually run some commands on freeRTOS, I get timeout error and I have no idea how to fix it. I attached to this e-mail my test job definition, together with the log and the snip from my web. Thanks in advance for your support, Oana [image: image.png] [image: image.png]

6 years, 2 months

Changing SERVER_IP in device-types/bae-uboot.jinja2

by Thomas Klaehn

Hi, As far as I could figure out - the uboot environment server ip is set in the base_uboot_dhcp_command in base-ubooy.jinja2. The value of SERVER_IP seems to be set somehow within lava. And it looks if it's not possible to overide it in the device dictionary, isn't it? Is there a way to change the value of SERVER_IP? Thanks in advance. Best regards, Thomas Klaehn Senior Software Engineer u-blox Berlin GmbH Rudower Chaussee 9 DE-12489 Berlin Phone +49 30 55573 1032 Mobile +49 151 23990904 www.u-blox.com<http://www.u-blox.com/> locate.communicate.accelerate follow us on twitter<https://twitter.com/ublox> | subscribe to our youtube channel<https://www.youtube.com/c/ublox1> | follow us on linkedin<https://www.linkedin.com/company/u-blox> | connect with us on facebook<https://www.facebook.com/ublox1> | follow us on google+<https://plus.google.com/+ublox1> u-blox Berlin GmbH CEO (Geschäftsführer): Daniel Ammann Registered: Berlin HRB 164301 B This message contains confidential information intended only for the use of the addressee(s) and may be legally privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return email and destroy all copies of the original message. All suggestions, recommendations, or other comments contained in this email are provided as a courtesy only. We do not assume any responsibility or liability for the correctness of the information contained in the email.

6 years, 2 months

Re: [Lava-users] Reset LAVA database

by Tim Jaacks

Hi Neil, thanks for your quick and direct feedback and please excuse my incautiousness. Being a software developer, I am still new to admin stuff and don't have much experience in hosting servers. The "flush" command is documented in the help text of "lava-server manage". From the information there it seemed as if "lava-server manage dumpdata" would create a dump of the database (which it did) and that I might be able to restore it with "lava-server manage loaddata" (which I couldn't) if the flush would not do what I expected. However, the database in that installation was not important at all, I spent some time experimenting with LAVA on this machine and just wanted to have a clean database for starting production use. I assumed there should be an easy way to achieve this. With your help, I was able to reset my LAVA database using the following commands: sudo apt-get purge lava-server sudo rm -rf /etc/lava-server/ sudo rm -rf /var/lib/lava-server/ sudo pg_dropcluster 9.6 main --stop sudo pg_createcluster 9.6 main --start sudo apt-get install lava-server Thanks for pointing me to the backup topic, I will address that in my next step. Cheers, Tim Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com SOLUTIONS THAT COMPLETE! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz

6 years, 2 months

Reset LAVA database

by Tim Jaacks

Hello everyone, is there a way to reset the LAVA database to the state of a fresh installation? From the docs I thought that "lava-server manage flush" command would do that. However, there are some things missing afterwards, e.g. the lava-health user and the master worker. Any hints on how to repair this? Re-installing lava-server did not help. Mit freundlichen Grüßen / Best regards i.A. Tim Jaacks Software Engineering Garz & Fricke GmbH Tempowerkring 2, 21079 Hamburg - Germany Amtsgericht Hamburg HRB 60514 Geschäftsführer: Manfred Garz, Matthias Fricke Phone: +49 40 791899 - 55 Fax: +49 40 791899 – 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com

6 years, 2 months

Building Embedded Debian-based system images

by Zoran S

Hello to Linaro developers, Recently I have learned that Linaro has developed its own tool to build Embedded Debian-based system images. I am very interested in this work/this tool. So I have some questions regarding this domain. [1] Do you have published this tool on the Open Source? [2] If YES, what are the web pointers to it, and the docs I can read and get familiar with the process? [3] Does it include scripts to enhance initramfs (the technology Linaro uses to do that), and where are the locations to read about it? [4] You name it (if I miss something, please, feel free to fill the gaps)! I use (almost always) YOCTO based build tool to create initramfses to test upon them (you know this already if you read my recent emails to this list). But I would like to have alternative method, and Linaro tool seems excellent one as alternative, for many reasons. Thank you in advance, Zoran Stojsavljevic _______

6 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Lava-users September 2018