search

project-chip / certification-tool

A test harness and tooling designed to simplify development, testing, and certification for devices, guided by the Connectivity Standards Alliance.
https://csa-iot.org/
Apache License 2.0
28 stars 15 forks source link

[Bug] SDK YAML tests fail at the commissioning step #178

Closed uritustefan closed 3 months ago

uritustefan commented 5 months ago

Describe the bug

When running any SDK YAML test using the TH, the harness returns an error stating the commissioning failed and "Buffer too small" can be seen in the logs. On the DUT side, the logs indicate that the commissioning was successful.

Using the same command found in the log provided by the TH, the commissioning works fine manually. I tried re-flashing the TH image on the RPI and the problem is still seen.

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

UI_Test_Run_2024_02_08_16_25_00.log

PICS file

No response

Screenshots

No response

Environment

Version: 2.10-beta2.2+spring2024Sha: 2432a29

Additional Information

No response

antonio-amjr commented 5 months ago

Hi @uritustefan

Can you please share three things for the investigation:

Thanks!

uritustefan commented 5 months ago

th_doctor_output.txt project_configuration.txt DUT_log.txt

Hello. I've uploaded the files you requested

antonio-amjr commented 5 months ago

Hello again @uritustefan,

First, thanks for sharing the files. Sorry about the delay. About the "Buffer too small" error that appears in the log, there's another issue focused on that in the following link: https://github.com/project-chip/certification-tool/issues/153

Let's see if their investigations help your problem.

Meanwhile, let me ask for your help here, since I don't have the test environment set:

One thing odd to me is that the buffer error doesn't stop the pairing process. The last step is actually the "ThreadNetworkSetup". Made me wonder...

I saw that the project's config is the default, beside the test_parameters. I'm assuming you're NOT using the scripts/OTBR/otbr_start.sh and TH automatically brings up the OTBR, right?

Can you try one of these two options:

  1. Remove thread-dataset-hex completely from test_parameters (to verify if SDK YAML Tests already have this info)
  2. Use thread-dataset-hex = 000300000f02081111111122222222051000112233445566778899aabbccddeeff01021234 (to verify if that's the simple dataset expected from your config)
uritustefan commented 3 months ago

Hello. I've closed the issue as it is no longer reproducing with the latest TH from the latest SVE. We couldn't pinpoint exactly what the cause was.