Hi folks,
We held our regular weekly design meeting today via Hangout. Summary of discussion:
1. [Steve] Layoffs in Linaro affecting the team
2. [Dean] A user has noticed that their jobs running the same process multiple times in a test shell have noticed that the latter iterations take much longer than earlier iterations, even though they should take the same amount of time. 1. They noticed the "Listened to connection for namespace '<NAMESPACE>' done" message appeared a lot. 2. shell.py has the following noted around this debug log: 1. # With an higher timeout, this can have a big impact on 2. # the performances of the overall loop. 1. Is there any known issues with the read feedback checks? 2. Is there any reason why this step would take longer over the course of a job? If so, is there anything we can do to mitigate this? 3. Is there any settings we can tweak to adjust performance? 4. Any further information that might help us investigate this further? 5. Maybe a pexpect problem? Changes in this area happened in 20l8.7, Dean is using 2018.5
3. [Rémi] lavafed labs 1. Neil’s lab is off 2. ARM? In process, but may take a while - needs IT involvement to open up ports etc. 3. [Rémi] Contact lava users: 1. Collabora? [done] 2. Baylibre? [done] 3. ST? 1. [Rémi] Add matt’s lab 2. [Steve] Can set up some stuff if needed (Mustang? BBB? Panda? Maybe grab old boards from Neil?)
4. [Rémi] LAVA 2019.2 release 1. When ? 2. Start the process Thu 28th, but we're not going to get it all done then 3. Expect to finish Monday 4th? 4. Need to document what functional tests we're doing manually for now (list was in Neil's head!) 5. We want to get to the point where lavafed etc. make this obsolete 1. Will need to actually work out useful tests for all the devices!
The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting.
Cheers,