[BUG] Error on TC-DRLK-2.8 execution (CONSTRAINT_ERROR) #28005

ccruzagralopes · 2023-07-17T18:47:19Z

Reproduction steps

Run chip-all-clusters-app
Use chip-tool to execute the test steps for TC-DRLK-2.8:

Commission DUT:

./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00

Step 1:

./chip-tool doorlock read number-of-total-users-supported 1 1

Step 2:

./chip-tool doorlock set-user 0 1 xxx 6452 1 0 0 1 1  --timedInteractionTimeoutMs 1000

Step 3:

./chip-tool doorlock get-user 1 1 1

Step 4:

./chip-tool doorlock set-user 0 2 xxx 6451 1 10 3 1 1 --timedInteractionTimeoutMs 1000

Step 5:

./chip-tool doorlock set-user 0 1 xxx 8965 1 0 0 1 1 --timedInteractionTimeoutMs 1000

Step 6a:

./chip-tool doorlock set-user 0 2 null null null null null 1 1 --timedInteractionTimeoutMs 1000

Step 6b:

./chip-tool doorlock get-user 2 1 1

Step 7:

./chip-tool doorlock set-user 2 2 null null null null null 1 1 --timedInteractionTimeoutMs 1000

Step 8:

./chip-tool doorlock get-user 2 1 1

Step 9:

./chip-tool doorlock clear-user 1 1 1  --timedInteractionTimeoutMs 1000

Step 10:

./chip-tool doorlock get-user 1 1 1  --timedInteractionTimeoutMs 1000

Decommission DUT:

./chip-tool pairing unpair 1

Error

On step 4, the expected response is:

[1657607954.930591][7988:7993] CHIP:DMG: {
[1657607954.930618][7988:7993] CHIP:DMG:        suppressResponse = false,
[1657607954.930651][7988:7993] CHIP:DMG:        InvokeResponseIBs =
[1657607954.930688][7988:7993] CHIP:DMG:        [
[1657607954.930716][7988:7993] CHIP:DMG:                InvokeResponseIB =
[1657607954.930755][7988:7993] CHIP:DMG:                {
[1657607954.930787][7988:7993] CHIP:DMG:                        CommandStatusIB =
[1657607954.930825][7988:7993] CHIP:DMG:                        {
[1657607954.930862][7988:7993] CHIP:DMG:                                CommandPathIB =
[1657607954.930900][7988:7993] CHIP:DMG:                                {
[1657607954.930942][7988:7993] CHIP:DMG:                                        EndpointId = 0x1,
[1657607954.930984][7988:7993] CHIP:DMG:                                        ClusterId = 0x101,
[1657607954.931027][7988:7993] CHIP:DMG:                                        CommandId = 0x1a,
[1657607954.931065][7988:7993] CHIP:DMG:                                },
[1657607954.931107][7988:7993] CHIP:DMG:
[1657607954.931142][7988:7993] CHIP:DMG:                                StatusIB =
[1657607954.931180][7988:7993] CHIP:DMG:                                {
[1657607954.931218][7988:7993] CHIP:DMG:                                        status = 0x85 (INVALID_COMMAND),
[1657607954.931259][7988:7993] CHIP:DMG:                                },
[1657607954.931296][7988:7993] CHIP:DMG:
[1657607954.931333][7988:7993] CHIP:DMG:                        },
[1657607954.931371][7988:7993] CHIP:DMG:
[1657607954.931402][7988:7993] CHIP:DMG:                },
[1657607954.931439][7988:7993] CHIP:DMG:
[1657607954.931466][7988:7993] CHIP:DMG:        ],
[1657607954.931500][7988:7993] CHIP:DMG:
[1657607954.931527][7988:7993] CHIP:DMG:        InteractionModelRevision = 1
[1657607954.931553][7988:7993] CHIP:DMG: },
[1657607954.931617][7988:7993] CHIP:DMG: Received Command Response Status for Endpoint=1 Cluster=0x0000_0101 Command=0x0000_001A Status=0x85
[1657607954.931654][7988:7993] CHIP:TOO: Error: IM Error 0x00000585: General error: 0x85 (INVALID_COMMAND)

Instead, chip-tool is giving the error: CHIP:TOO: Run command failure: src/app/data-model/Encode.h:75: IM Error 0x00000587: General error: 0x87 (CONSTRAINT_ERROR)

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

9ac1480

Platform

other

Platform Version(s)

No response

Anything else?

Logs

chip-all-clusters-app logs: chip-all-clusters-app.log
chip-tool logs: chip-tool.log

Test plan verification steps

The test case steps and expected results were taken from: https://groups.csa-iot.org/wg/matter-csg/document/28567

Additional testing

I also tested the same test case using chip-lock-app, but go the same result:

chip-lock-app logs: 2_chip-lock-app.log
chip-tool logs: 2_chip-tool.log

Additional Comments

This bug has been found when trying to run TC-DRLK-2.6 and TC-DRLK-2.8 in Test Harness. This same error is also happening when running TC-DRLK-2.6. I believe the root cause is probably be the same.

Logs from Test Harness running both TC-DRLK-2.6 and TC-DRLK-2.8: UI_Test_Run_2023_07_14_16_03_37.log

Test Harness related issues

TC-DRLK-2.8 issue: https://github.com/CHIP-Specifications/chip-certification-tool/issues/897
TC-DRLK-2.6 issue: https://github.com/CHIP-Specifications/chip-certification-tool/issues/895

The text was updated successfully, but these errors were encountered:

ccruzagralopes · 2023-07-17T19:27:45Z

FYI @raju-apple @mikaelhm @krypton36

bzbarsky-apple · 2023-07-17T19:57:30Z

Instead, chip-tool is giving the error: CHIP:TOO: Run command failure: src/app/data-model/Encode.h:75: IM Error 0x00000587: General error: 0x87 (CONSTRAINT_ERROR)

This is a chip-tool binary that was somehow compiled incorrectly. It's not even testing the server in this case, because it is failing to send the invalid value to start with.

examples/chip-tool/include/CHIPProjectAppConfig.h has this bit:

#define CHIP_CONFIG_IM_ENABLE_ENCODING_SENTINEL_ENUM_VALUES 1

but it looks like this specific chip-tool binary was compiled without that setting somehow.

@ccruzagralopes Where did this chip-tol binary come from?

ccruzagralopes · 2023-07-17T20:06:55Z

This error happened with a few images:

The one from the first logs I've built using the Dockerfile from connectedhomeip/integrations/docker/images/chip-cert-bins and using the command:

docker buildx build --load --build-arg COMMITHASH=9ac148067fb9c5a4aadab1fdecd0a8b4e22e6da0 --tag connectedhomeip/chip-cert-bins:9ac148067fb9c5a4aadab1fdecd0a8b4e22e6da0 .

It also happened when using the same build steps for SHA a39e88a2dd1186cd8358485bc26a21059c72b44f.

I'm using an ubuntu VM in an Intel chip Macbook, so these two images were built for amd64. But the TH issues were filed from someone that used a binary that came from the chip-cert-bins:a39e88a2dd1186cd8358485bc26a21059c72b44f image that was built for arm64 and is in the Docker registry.

bzbarsky-apple · 2023-07-17T20:13:47Z

The one from the first logs I've built using the Dockerfile from connectedhomeip/integrations/docker/images/chip-cert-bins

That docker image already has the tool built, no? And sounds like it's built incorrectly...

Which sounds like an issue for https://github.com/CHIP-Specifications/chip-certification-tool or so, not an SDK issue.

mikaelhm · 2023-07-17T20:14:59Z

@bzbarsky-apple
The docker file for this lives in SDK.

So if it's built incorrectly, we need to fix this in here:

connectedhomeip/integrations/docker/images/chip-cert-bins/Dockerfile

Line 209 in ba335e9

    
           && gn gen out/debug --args='chip_mdns="platform" chip_inet_config_enable_ipv4=false' \

mikaelhm · 2023-07-17T20:18:15Z

The chip-tool compilation, for Matter TH, hasn't been changed since this PR by @andy31415:
#23874

Not sure if something changed in chip-tool compilation since, or it's always been wrong.

bzbarsky-apple · 2023-07-17T20:33:56Z

I think it's always been wrong. This bit:

    source scripts/activate.sh \
    && gn gen out/debug --args='chip_mdns="platform" chip_inet_config_enable_ipv4=false' \
    && ninja -C out/debug

does the "unified" build that ignores app-specific configs, because it's just kind of broken. We should probably be building chip-tool as part of the scripts/build/build_examples.py bits around https://github.com/project-chip/connectedhomeip/blob/ba335e93f4a2866140310b309ab99b9506fdaab1/integrations/docker/images/chip-cert-bins/Dockerfile#L224C8-L224C39 instead.

mikaelhm · 2023-07-17T20:36:25Z

I think the scripts/build/build_examples.py way of compiling chip-tool was broken at the time. Let me see if I can find the original pull request that had this feedback.

bzbarsky-apple · 2023-07-17T20:39:00Z

Totally believable. Anyway, moving to building chip-tool as part of the build_examples bits (like it is in Matter CI) should resolve this problem....

mikaelhm · 2023-07-17T20:56:23Z

We will try that!

If we add --target linux-x64-chip-tool-ipv6only how do we specify the --args='chip_mdns="platform"'

bzbarsky-apple · 2023-07-17T21:18:20Z

If we add --target linux-x64-chip-tool-ipv6only how do we specify the --args='chip_mdns="platform"'

@andy31415 ?

Note that you could also just do:

scripts/examples/gn_build_example.sh examples/chip-tool out/whartever chip_mdns ='"platform"'

to build just chip-tool if the build_examples bit is not flexible enough.

andy31415 · 2023-07-18T13:33:28Z

I believe the target supports -platform-mdns variant if you need platformmdns. So something like:

--target linux-x64-chip-tool-ipv6only-platform-mdns

may work.

andy31415 · 2023-07-18T13:35:25Z

However I am somehow unclear what platform-mdns has to do with constraint errors. I added the above describing how to set up platform-mdns, however I believe we should support both platformmdns or minmdns in the same way.

ccruzagralopes · 2023-07-18T17:07:09Z

Thanks everyone for the suggestions!

I've tried exchanging

    source scripts/activate.sh \
    && gn gen out/debug --args='chip_mdns="platform" chip_inet_config_enable_ipv4=false' \
    && ninja -C out/debug

for

    source scripts/activate.sh \
    && scripts/examples/gn_build_example.sh examples/chip-tool out/chip-tool 'chip_mdns="platform" chip_inet_config_enable_ipv4=false'

It resulted in an error later on:

I'm now trying out this --target linux-x64-chip-tool-ipv6only-platform-mdns option on the scripts/build/build_examples.py bit

mikaelhm · 2023-07-18T17:09:27Z

@ccruzagralopes That build_python.sh issue could be unrelated.

ccruzagralopes · 2023-07-18T17:12:24Z

@ccruzagralopes That build_python.sh issue could be unrelated.

I agree. I just found it odd because I had used this same Dockerfile (without the mentioned changes) yesterday and successfully built a new image, so I don't see another reason for this issue to happen now and not yesterday

bzbarsky-apple · 2023-07-19T03:56:07Z

@ccruzagralopes I believe the virtualenv thing was a known issue on Matter tip for a day or so. Update to tip as of right now, just in case.

Note that skipping ninja -C out/debug might also skip building other things (not just chip-tool) that the docker image then tries to copy.... So you might need both.

ccruzagralopes · 2023-07-19T12:40:25Z

@bzbarsky-apple I realized that the build_python.sh script has been changed, so the -i flag that was being used in the Dockerfile now means something else and shouldn't be used in this context. When I removed that I stoped getting the virtualenv error because I don't actually need to use that.

About the other things that ninja -C out/debug builds, I noticed that it was chip-shell and chip-cert and that those are also possible to be built using build_examples.py, so I did that.

With these changes, I was able to build a new image that didn't fail TC-DRLK-2.8. TC-DRLK-2.6 is still failing with a UNSUPPORTED_COMMAND error, so I'll look into the logs today to try to figure out if this error is related to the build or something else.

The Dockerfile that I used and was able to build the image was: Dockerfile.txt
I plan to open a PR for this change once I investigate TC-DRLK-2.6's failure.

bzbarsky-apple · 2023-07-19T20:14:30Z

@ccruzagralopes Great! TC-DRLK-2.6 failing with UNSUPPORTED_COMMAND sounds like a different issue, fwiw.... Is it running against lock-app or chip-all-clusters-app? Because all-clusters-app does not implement all the lock bits.

ccruzagralopes · 2023-07-19T20:16:38Z

@bzbarsky-apple I was running with chip-all-clusters-app, that was the issue 😅 When I ran it using chip-lock-app it passed

cjandhyala · 2023-08-09T05:31:10Z

closing the issue based on your comment @ccruzagralopes , feel free to re-open if this is still an issue

ccruzagralopes added bug Something isn't working needs triage labels Jul 17, 2023

ccruzagralopes mentioned this issue Jul 19, 2023

Fix chip-cert-bin Dockerfile #28079

Merged

krypton36 self-assigned this Jul 20, 2023

cjandhyala closed this as completed Aug 9, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG] Error on TC-DRLK-2.8 execution (CONSTRAINT_ERROR) #28005

[BUG] Error on TC-DRLK-2.8 execution (CONSTRAINT_ERROR) #28005

ccruzagralopes commented Jul 17, 2023

ccruzagralopes commented Jul 17, 2023

bzbarsky-apple commented Jul 17, 2023 •

edited

Loading

ccruzagralopes commented Jul 17, 2023

bzbarsky-apple commented Jul 17, 2023

mikaelhm commented Jul 17, 2023 •

edited by bzbarsky-apple

Loading

mikaelhm commented Jul 17, 2023 •

edited

Loading

bzbarsky-apple commented Jul 17, 2023

mikaelhm commented Jul 17, 2023 •

edited

Loading

bzbarsky-apple commented Jul 17, 2023

mikaelhm commented Jul 17, 2023

bzbarsky-apple commented Jul 17, 2023

andy31415 commented Jul 18, 2023 •

edited

Loading

andy31415 commented Jul 18, 2023

ccruzagralopes commented Jul 18, 2023

mikaelhm commented Jul 18, 2023

ccruzagralopes commented Jul 18, 2023

bzbarsky-apple commented Jul 19, 2023

ccruzagralopes commented Jul 19, 2023

bzbarsky-apple commented Jul 19, 2023

ccruzagralopes commented Jul 19, 2023

cjandhyala commented Aug 9, 2023

[BUG] Error on TC-DRLK-2.8 execution (CONSTRAINT_ERROR) #28005

[BUG] Error on TC-DRLK-2.8 execution (CONSTRAINT_ERROR) #28005

Comments

ccruzagralopes commented Jul 17, 2023

Reproduction steps

Error

Bug prevalence

GitHub hash of the SDK that was being used

Platform

Platform Version(s)

Anything else?

Logs

Test plan verification steps

Additional testing

Additional Comments

Test Harness related issues

ccruzagralopes commented Jul 17, 2023

bzbarsky-apple commented Jul 17, 2023 • edited Loading

ccruzagralopes commented Jul 17, 2023

bzbarsky-apple commented Jul 17, 2023

mikaelhm commented Jul 17, 2023 • edited by bzbarsky-apple Loading

mikaelhm commented Jul 17, 2023 • edited Loading

bzbarsky-apple commented Jul 17, 2023

mikaelhm commented Jul 17, 2023 • edited Loading

bzbarsky-apple commented Jul 17, 2023

mikaelhm commented Jul 17, 2023

bzbarsky-apple commented Jul 17, 2023

andy31415 commented Jul 18, 2023 • edited Loading

andy31415 commented Jul 18, 2023

ccruzagralopes commented Jul 18, 2023

mikaelhm commented Jul 18, 2023

ccruzagralopes commented Jul 18, 2023

bzbarsky-apple commented Jul 19, 2023

ccruzagralopes commented Jul 19, 2023

bzbarsky-apple commented Jul 19, 2023

ccruzagralopes commented Jul 19, 2023

cjandhyala commented Aug 9, 2023

bzbarsky-apple commented Jul 17, 2023 •

edited

Loading

mikaelhm commented Jul 17, 2023 •

edited by bzbarsky-apple

Loading

mikaelhm commented Jul 17, 2023 •

edited

Loading

mikaelhm commented Jul 17, 2023 •

edited

Loading

andy31415 commented Jul 18, 2023 •

edited

Loading