The bootloader-commands step breaks into u-boot and begins to issue commands, but some commands are issued prior to receiving the prompt.
I've attempted changing the boot_char_delay, but it doesn't solve the issue.
I'm getting symptoms much like the ones in this thread, except I'm sending space rather than a newline, so the fix is not relevant to me.
https://lists.linaro.org/pipermail/lava-users/2018-May/001069.html
Jeremy Stashluk
Embedded Software Engineer
[cid:image002.jpg@01D45B04.B75D2A40]
Geophysical Survey Systems, Inc.
40 Simon Street * Nashua, NH 03060-3075
603. 893.1109 main * 603.681.2045 direct * 603.889.3984 fax
stashlukj(a)geophysical.com<mailto:stashlukj@geophysical.com> * www.geophysical.com<http://www.geophysical.com/>
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
Dear users,
I'm looking for a way to detect a possible watchdog in u-boot during a test session.
It happened that on one our test platforms a watchdog was triggered, u-boot restarted, and eventually the test session started. Unless we take a look at every trace of every job, there is a big chance to leave this type of errors undetected.
Do you have any idea on a possible way to handle this in Lava, maybe via device dictionary?
Thanks in advance,
Denis
Hi,
We're using LAVA 2018.5.post1 and we have not been able to log into the web interface since upgrading to this version. The system is running within a docker container. Trying to log in results in a CSRF warning.
The same version of LAVA running on a dedicated debian machine does start working when adding the mentioned lines from this page: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#djan…
Making the same changes to /etc/lava-server/settings.conf within the docker container has no effect on the way the web interface works. It still provides the same errors.
Is there anything else we should do to try to get the web interface to allow logins? I'm not even sure the settings.conf file is being read when restarting the LAVA services, would it appear in one of the logs so that I could search for it?
Thanks for any help you can provide regarding this matter.
Regards,
Jorgen Peddersen
Jorgen Peddersen
Researcher
t +61 2 6103 4700
m
e jorgen.peddersen(a)seeingmachines.com
a 80 Mildura Street, Fyshwick ACT 2609, Australia
SEEINGMACHINES.COM<http://seeingmachines.com>
[SEEINGMACHINES]
This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-twitter-i…] <https://twitter.com/seeingmachines> [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-linkedin-…] <https://www.linkedin.com/company/258949/>
