tests: gdbstub: Add GDB remote target parameter
Add `gdb_target_remote` test parameter for GDB `target remote` command instead of its hardcoded value to allow different types of gdbstub serial interfaces as well as different TCP ports in gdbstub test suites possibly run in parallel on the same host. Move all GDB log configuration parameters from GDB script to the fixture code. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
This commit is contained in:
parent
5008c31f8c
commit
236c1ac5de
5 changed files with 23 additions and 13 deletions
|
@ -7,6 +7,7 @@
|
|||
import pytest
|
||||
|
||||
def pytest_addoption(parser):
|
||||
parser.addoption('--gdb_target_remote')
|
||||
parser.addoption('--gdb_timeout')
|
||||
parser.addoption('--gdb_script')
|
||||
|
||||
|
@ -17,4 +18,8 @@ def gdb_script(request):
|
|||
@pytest.fixture()
|
||||
def gdb_timeout(request):
|
||||
return int(request.config.getoption('--gdb_timeout', default=60))
|
||||
|
||||
@pytest.fixture()
|
||||
def gdb_target_remote(request):
|
||||
return request.config.getoption('--gdb_target_remote', default=":5678")
|
||||
#
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue