SiliconLabsSoftware · mkardous-silabs · Feb 9, 2025 · Feb 6, 2025 · Feb 6, 2025 · Feb 6, 2025
@@ -39,7 +39,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: ghcr.io/project-chip/chip-build-android:106
+            image: ghcr.io/project-chip/chip-build-android:108
             volumes:
                 - "/tmp/log_output:/tmp/test_logs"
 

@@ -114,7 +114,6 @@ jobs:
                      --known-failure app/util/config.h \
                      --known-failure app/util/DataModelHandler.cpp \
                      --known-failure app/util/DataModelHandler.h \
-                     --known-failure app/util/ember-global-attribute-access-interface.h \
                      --known-failure app/util/ember-io-storage.h \
                      --known-failure app/util/endpoint-config-api.h \
                      --known-failure app/util/generic-callbacks.h \
@@ -133,7 +132,6 @@ jobs:
                   # for them. Keeping them as a list as they still need review ...
                   #   --known-failure app/util/attribute-table.cpp \
                   #   --known-failure app/util/ember-io-storage.cpp \
-                  #   --known-failure app/util/ember-global-attribute-access-interface.cpp \
                   #   --known-failure app/util/attribute-storage.cpp \
             - name: Check for matter lint errors
               if: always()

@@ -37,7 +37,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: ghcr.io/project-chip/chip-build-android:106
+            image: ghcr.io/project-chip/chip-build-android:108
             volumes:
                 - "/:/runner-root-volume"
                 - "/tmp/log_output:/tmp/test_logs"

@@ -537,6 +537,7 @@ jobs:
                   scripts/run_in_python_env.sh out/venv 'python3 src/python_testing/TestIdChecks.py'
                   scripts/run_in_python_env.sh out/venv 'python3 src/python_testing/TestMatterTestingSupport.py'
                   scripts/run_in_python_env.sh out/venv 'python3 src/python_testing/TestSpecParsingDeviceType.py'
+                  scripts/run_in_python_env.sh out/venv 'python3 src/python_testing/TestSpecParsingSelection.py'
                   scripts/run_in_python_env.sh out/venv 'python3 src/python_testing/TestSpecParsingSupport.py'
 
             - name: Run Tests

@@ -589,30 +589,77 @@ SDK source code has been executed. It also provides information on how often the
 Matter SDK executes segments of the code and produces a copy of the source file,
 annotated with execution frequencies.
 
-Run the following command to initiate the script:
+### How to Run
+
+```
+./scripts/build_coverage.sh [OPTIONS]
+```
+
+By default, the script
+
+Builds the Matter SDK with coverage instrumentation (unless you specify a custom
+--output_root). Runs the unit tests to generate coverage data. Produces an HTML
+coverage report located at:
+
+```
+out/coverage/coverage/html/index.html
+```
+
+You can extend the coverage scope and test types with the following options:
+
+Option Description -c, --code=<scope> Specify the scope to collect coverage
+data. - core (default): Coverage from the core Matter SDK stack - clusters:
+Coverage from cluster implementations - all: Coverage from the entire Matter SDK
+
+--yaml Also run YAML-based tests, in addition to unit tests.
+
+--python Also run Python-based tests, in addition to unit tests.
+
+-o, --output_root=DIR If specified, skip the build phase and only run coverage
+on the provided build output directory. This directory must have been built with
+use_coverage=true and have had tests run already.
+
+--target=<testname> When running unit tests, specifies a particular test target
+to run (e.g., TestEmberAttributeBuffer.run).
+
+-h, --help Print script usage and exit.
+
+### Examples
+
+Run coverage with the default scope (core) and only unit tests:
 
 ```
 ./scripts/build_coverage.sh
 ```
 
-By default, the code coverage script is performed at the unit testing level.
-Unit tests are created by developers, thus giving them the best overview of what
-tests to include in unit testing. You can extend the coverage test by scope and
-ways of execution with the following parameters:
+Run coverage including YAML tests (plus the always-enabled unit tests):
+
+```
+./scripts/build_coverage.sh --yaml
+```
+
+Run coverage including Python tests (plus the always-enabled unit tests):
 
 ```
-  -c, --code                Specify which scope to collect coverage data.
-                            'core': collect coverage data from core stack in Matter SDK. --default
-                            'clusters': collect coverage data from clusters implementation in Matter SDK.
-                            'all': collect coverage data from Matter SDK.
-  -t, --tests               Specify which tools to run the coverage check.
-                            'unit': Run unit test to drive the coverage check. --default
-                            'yaml': Run yaml test to drive the coverage check.
-                            'all': Run unit & yaml test to drive the coverage check.
+./scripts/build_coverage.sh --python
 ```
 
-Also, see the up-to-date unit testing coverage report of the Matter SDK
-(collected daily) at:
+Run coverage including both YAML and Python tests:
+
+```
+./scripts/build_coverage.sh --yaml --python
+```
+
+Change coverage scope to all (core + clusters) and run YAML tests:
+
+```
+./scripts/build_coverage.sh --code=all --yaml
+```
+
+### Viewing Coverage Results
+
+After the script completes, open the following file in your web browser to view
+the HTML coverage report:
 [matter coverage](https://matter-build-automation.ue.r.appspot.com).
 
 ## Maintaining Matter

@@ -58,10 +58,12 @@ class PairOnNetworkLongImReadCommand(
       event.getJson().toString() == """{"0:STRUCT":{"0:UINT":1}}"""
 
     fun checkAllAttributesJsonForFixedLabel(cluster: String): Boolean {
+      // TODO: this hard-codes the array and as a result it is order-dependend. This should
+      //       be changed to be order-independent.
       val expected =
         """{"65528:ARRAY-?":[],"0:ARRAY-STRUCT":[{"0:STRING":"room","1:STRING":"bedroom 2"},""" +
           """{"0:STRING":"orientation","1:STRING":"North"},{"0:STRING":"floor","1:STRING":"2"},""" +
-          """{"0:STRING":"direction","1:STRING":"up"}],"65531:ARRAY-UINT":[0,65528,65529,65531,65532,65533],""" +
+          """{"0:STRING":"direction","1:STRING":"up"}],"65531:ARRAY-UINT":[0,65532,65533,65528,65529,65531],""" +
           """"65533:UINT":1,"65529:ARRAY-?":[],"65532:UINT":0}"""
       return cluster.equals(expected)
     }

@@ -140,7 +140,7 @@ steps:
           - name: pwenv
             path: /pwenv
 
-    - name: "ghcr.io/project-chip/chip-build-vscode:104"
+    - name: "ghcr.io/project-chip/chip-build-vscode:108"
       id: Android
       env:
           - PW_ENVIRONMENT_ROOT=/pwenv

@@ -1 +1 @@
-108 : Update vscode docker with java17 and fix java_home in java docker
+109 : [Tizen] Fix race when storing cert credentials
@@ -61,6 +61,7 @@ def _save(self):
             self.fp.seek(0)
             self.fp.truncate()
             pickle.dump(self.secrets, self.fp)
+            self.fp.flush()
         except IOError as e:
             print("ERROR: " + str(e), file=sys.stderr)
 
@@ -92,14 +93,14 @@ def lookup(self, label: str, **kw):
 subparsers = parser.add_subparsers(dest='command', required=True)
 
 parser_clear = subparsers.add_parser(
-    "clear", help="Remove passward associated with given key value pairs")
+    "clear", help="Remove password associated with given key value pairs")
 parser_clear.add_argument("-l", "--label", action='store', required=True,
                           help="label for given key value pairs")
 parser_clear.add_argument("kw", nargs='*',
                           help="key value pairs")
 
 parser_store = subparsers.add_parser(
-    "store", help="Store passward for given key value pairs")
+    "store", help="Store password for given key value pairs")
 parser_store.add_argument("-l", "--label", action='store', required=True,
                           help="label for given key value pairs")
 parser_store.add_argument("-p", "--password", action='store', required=True,
@@ -108,7 +109,7 @@ def lookup(self, label: str, **kw):
                           help="key value pairs")
 
 parser_lookup = subparsers.add_parser(
-    "lookup", help="Retrieve passward associated with given key value pairs")
+    "lookup", help="Retrieve password associated with given key value pairs")
 parser_lookup.add_argument("-l", "--label", action='store', required=True,
                            help="label for given key value pairs")
 parser_lookup.add_argument("kw", nargs='*',

@@ -164,6 +164,7 @@ style:
             - "**/examples/android/CHIPTool/app/src/main/java/com/google/chip/chiptool/clusterclient/MultiAdminClientFragment.kt"
             - "**/examples/android/CHIPTool/app/src/main/java/com/google/chip/chiptool/clusterclient/clusterinteraction/ClusterInteractionFragment.kt"
             - "**/examples/android/CHIPTool/app/src/main/java/com/google/chip/chiptool/provisioning/AddressCommissioningFragment.kt"
+            - "**/examples/java-matter-controller/java/src/com/matter/controller/commands/pairing/PairOnNetworkLongImReadCommand.kt"
             - "**/src/controller/java/src/matter/onboardingpayload/QRCodeOnboardingPayloadParser.kt"
     ExplicitItLambdaParameter:
         excludes:
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		108 : Update vscode docker with java17 and fix java_home in java docker
		109 : [Tizen] Fix race when storing cert credentials