2016-01-15 18:15:31 +00:00
|
|
|
# Copyright (c) 2016, NVIDIA CORPORATION. All rights reserved.
|
|
|
|
|
#
|
|
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
|
|
|
|
|
|
|
|
import pytest
|
|
|
|
|
import time
|
|
|
|
|
|
|
|
|
|
def test_sleep(u_boot_console):
|
2016-01-26 20:41:30 +00:00
|
|
|
"""Test the sleep command, and validate that it sleeps for approximately
|
|
|
|
|
the correct amount of time."""
|
2016-01-15 18:15:31 +00:00
|
|
|
|
2016-10-14 23:12:31 +00:00
|
|
|
if u_boot_console.config.buildconfig.get('config_cmd_misc', 'n') != 'y':
|
|
|
|
|
pytest.skip('sleep command not supported')
|
2016-01-15 18:15:31 +00:00
|
|
|
# 3s isn't too long, but is enough to cross a few second boundaries.
|
|
|
|
|
sleep_time = 3
|
|
|
|
|
tstart = time.time()
|
|
|
|
|
u_boot_console.run_command('sleep %d' % sleep_time)
|
|
|
|
|
tend = time.time()
|
|
|
|
|
elapsed = tend - tstart
|
test/py: support running sandbox under gdbserver
Implement command--line option --gdbserver COMM, which does two things:
a) Run the sandbox process under gdbserver, using COMM as gdbserver's
communication channel.
b) Disables all timeouts, so that if U-Boot is halted under the debugger,
tests don't fail. If the user gives up in the middle of a debugging
session, they can simply CTRL-C the test script to abort it.
This allows easy debugging of test failures without having to manually
re-create the failure conditions. Usage is:
Window 1:
./test/py/test.py --bd sandbox --gdbserver localhost:1234
Window 2:
gdb ./build-sandbox/u-boot -ex 'target remote localhost:1234'
When using this option, it likely makes sense to use pytest's -k option
to limit the set of tests that are executed.
Simply running U-Boot directly under gdb (rather than gdbserver) was
also considered. However, this was rejected because:
a) gdb's output would then be processed by the test script, and likely
confuse it causing false failures.
b) pytest by default hides stdout from tests, which would prevent the
user from interacting with gdb.
While gdb can be told to redirect the debugee's stdio to a separate
PTY, this would appear to leave gdb's stdio directed at the test
scripts and the debugee's stdio directed elsewhere, which is the
opposite of the desired effect. Perhaps some complicated PTY muxing
and process hierarchy could invert this. However, the current scheme
is simple to implement and use, so it doesn't seem worth complicating
matters.
c) Using gdbserver allows arbitrary debuggers to be used, even those with
a GUI. If the test scripts invoked the debugger themselves, they'd have
to know how to execute arbitary applications. While the user could hide
this all in a wrapper script, this feels like extra complication.
An interesting future idea might be a --gdb-screen option, which could
spawn both U-Boot and gdb separately, and spawn the screen into a newly
created window under screen. Similar options could be envisaged for
creating a new xterm/... too.
--gdbserver currently only supports sandbox, and not real hardware.
That's primarily because the test hooks are responsible for all aspects of
hardware control, so there's nothing for the test scripts themselves can
do to enable gdbserver on real hardware. We might consider introducing a
separate --disable-timeouts option to support use of debuggers on real
hardware, and having --gdbserver imply that option.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
2016-02-04 23:11:50 +00:00
|
|
|
assert elapsed >= sleep_time
|
|
|
|
|
if not u_boot_console.config.gdbserver:
|
|
|
|
|
# 0.25s margin is hopefully enough to account for any system overhead.
|
|
|
|
|
assert elapsed < (sleep_time + 0.25)
|
