tests: bluetooth: tester: Set Config Client timeout to larger value
In some scenarios when there is a need for multiple re-transmissions of segmented messages the default value of 2 seconds may be not enough. In my experience this improves stability of Configuration Client tests involving multiple PTS instances. Signed-off-by: Michał Narajowski <michal.narajowski@codecoup.pl>
This commit is contained in:
parent
87ac114571
commit
4cb935f264
1 changed files with 2 additions and 0 deletions
|
@ -885,6 +885,8 @@ static void composition_data_get(uint8_t *data, uint16_t len)
|
||||||
|
|
||||||
LOG_DBG("");
|
LOG_DBG("");
|
||||||
|
|
||||||
|
bt_mesh_cfg_cli_timeout_set(10 * MSEC_PER_SEC);
|
||||||
|
|
||||||
net_buf_simple_init(comp, 0);
|
net_buf_simple_init(comp, 0);
|
||||||
|
|
||||||
err = bt_mesh_cfg_comp_data_get(cmd->net_idx, cmd->address, cmd->page,
|
err = bt_mesh_cfg_comp_data_get(cmd->net_idx, cmd->address, cmd->page,
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue