Merge branch 'master' into updateUI

project-chip · Jan 18, 2023 · bb5a317 · bb5a317
2 parents 7cc2737 + 808b9fe
commit bb5a317
Show file tree

Hide file tree

Showing 35 changed files with 286 additions and 348 deletions.
diff --git a/.github/workflows/docbuild.yaml b/.github/workflows/docbuild.yaml
@@ -1,6 +1,14 @@
 name: Documentation Build
 
 on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+    branches:
+      - master
+    paths:
+    - '.github/workflows/docbuild.yaml'
+    - '**.md'
+    - 'docs/**'
   push:
     branches:
       - master
@@ -9,7 +17,7 @@ permissions:
   contents: write
 
 jobs:
-  build-and-deploy:
+  build-and-publish:
     runs-on: ubuntu-latest
 
     steps:
@@ -39,7 +47,7 @@ jobs:
           make html
           touch _build/html/.nojekyll
       - name: Deploy to gh-pages
-        if: github.repository == 'project-chip/connectedhomeip'
+        if: github.repository == 'project-chip/connectedhomeip' && github.event_name == 'push' && github.ref_name == 'master'
         uses: peaceiris/actions-gh-pages@v3
         with:
           deploy_key: ${{ secrets.DOXYGEN_DEPLOY_KEY }}

diff --git a/docs/Makefile b/docs/Makefile
@@ -3,7 +3,7 @@
 
 # You can set these variables from the command line, and also
 # from the environment for the first two.
-SPHINXOPTS    ?= -W -c . -d _build/doctrees
+SPHINXOPTS    ?= -W --keep-going -c . -d _build/doctrees
 SPHINXBUILD   ?= sphinx-build
 SOURCEDIR     = _build/src
 BUILDDIR      = _build

diff --git a/docs/guides/BUILDING.md b/docs/guides/BUILDING.md
@@ -390,6 +390,37 @@ gn desc out/host //src/lib outputs
 gn desc out/host //src/lib --format=json
 ```
 
+## Coverage
+
+Code coverage scripts generate a report that details how much of the Matter SDK
+source code has been executed, it also gives information on how often the Matter
+SDK executes segments of code and produces a copy of the source file, annotated
+with execution frequencies.
+
+```
+./scripts/build_coverage.sh
+```
+
+By default, Code coverage is performed at the unit testing level. Unit tests are
+created by developers, thus giving them the best vantage from which to decide
+what tests to include in unit testing. But you can extend the coverage test by
+scope and ways of execution with the following parameters:
+
+```
+  -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.
+```
+
+Also see the up-to-date unit testing coverage report of the Matter SDK
+(collected daily) at:
+[matter coverage](https://matter-build-automation.ue.r.appspot.com).
+
 ## Maintaining Matter
 
 If you make any change to the GN build system, the next build will regenerate

diff --git a/examples/light-switch-app/nrfconnect/Kconfig b/examples/light-switch-app/nrfconnect/Kconfig
@@ -40,6 +40,13 @@ config CHIP_ENABLE_SLEEPY_END_DEVICE_SUPPORT
 
 endif # NET_L2_OPENTHREAD
 
+if CHIP_WIFI
+
+config NRF_WIFI_LOW_POWER
+	default y
+
+endif # CHIP_WIFI
+
 rsource "../../../config/nrfconnect/chip-module/Kconfig.features"
 rsource "../../../config/nrfconnect/chip-module/Kconfig.defaults"
 source "Kconfig.zephyr"
diff --git a/examples/light-switch-app/silabs/SiWx917/README.md b/examples/light-switch-app/silabs/SiWx917/README.md
@@ -32,8 +32,6 @@ An example showing the use of CHIP on the Silicon Labs EFR32 MG12 and MG24.
 > release with added tools and documentation.
 > [Silabs Matter Github](https://github.com/SiliconLabs/matter/releases)
 
-<a name="intro"></a>
-
 ## Introduction
 
 The EFR32 light switch example provides a baseline demonstration of a on-off
@@ -53,8 +51,6 @@ The light switch example is intended to serve both as a means to explore the
 workings of Matter as well as a template for creating real products based on the
 Silicon Labs platform.
 
-<a name="building"></a>
-
 ## Building
 
 -   Download the
@@ -181,15 +177,13 @@ Silicon Labs platform.
           $ gn gen out/debug --args='import("//with_pw_rpc.gni")'
           $ ninja -C out/debug
 
-    [Running Pigweed RPC console](#running-pigweed-rpc-console)
+    [Running Pigweed RPC console](#running-rpc-console)
 
 For more build options, help is provided when running the build script without
 arguments
 
     ./scripts/examples/gn_efr32_example.sh
 
-<a name="flashing"></a>
-
 ## Flashing the Application
 
 -   On the command line:
@@ -199,8 +193,6 @@ arguments
 
 -   Or with the Ozone debugger, just load the .out file.
 
-<a name="view-logging"></a>
-
 ## Viewing Logging Output
 
 The example application is built to use the SEGGER Real Time Transfer (RTT)
@@ -249,8 +241,6 @@ combination with JLinkRTTClient as follows:
 
           $ JLinkRTTClient
 
-<a name="running-complete-example"></a>
-
 ## Running the Complete Example
 
 -   It is assumed here that you already have an OpenThread border router
@@ -385,8 +375,6 @@ combination with JLinkRTTClient as follows:
 #Add Ipv6 route on PC(Linux) \$ sudo ip route add <Thread global ipv6 prefix>/64
 via 2002::2
 
-<a name="running-pigweed-rpc-console"></a>
-
 ## Running RPC console
 
 -   As part of building the example with RPCs enabled the chip_rpc python
@@ -432,7 +420,7 @@ tracking code inside the `trackAlloc` and `trackFree` function
 
 For the description of Software Update process with EFR32 example applications
 see
-[EFR32 OTA Software Update](../../../docs/guides/silabs_efr32_software_update.md)
+[EFR32 OTA Software Update](../../../../docs/guides/silabs_efr32_software_update.md)
 
 ## Building options
 

diff --git a/examples/lock-app/nrfconnect/Kconfig b/examples/lock-app/nrfconnect/Kconfig
@@ -52,6 +52,13 @@ config CHIP_ENABLE_SLEEPY_END_DEVICE_SUPPORT
 
 endif # NET_L2_OPENTHREAD
 
+if CHIP_WIFI
+
+config NRF_WIFI_LOW_POWER
+	default y
+
+endif # CHIP_WIFI
+
 rsource "../../../config/nrfconnect/chip-module/Kconfig.features"
 rsource "../../../config/nrfconnect/chip-module/Kconfig.defaults"
 source "Kconfig.zephyr"
diff --git a/examples/lock-app/silabs/SiWx917/README.md b/examples/lock-app/silabs/SiWx917/README.md
@@ -27,8 +27,6 @@ An example showing the use of CHIP on the Silicon Labs EFR32 MG12 and MG24.
 > release with added tools and documentation.
 > [Silabs Matter Github](https://github.com/SiliconLabs/matter/releases)
 
-<a name="intro"></a>
-
 ## Introduction
 
 The EFR32 lock example provides a baseline demonstration of a door lock control
@@ -48,8 +46,6 @@ The lighting example is intended to serve both as a means to explore the
 workings of Matter as well as a template for creating real products based on the
 Silicon Labs platform.
 
-<a name="building"></a>
-
 ## Building
 
 -   Download the
@@ -189,17 +185,13 @@ Mac OS X
           $ ninja -C out/debug
           ```
 
-    [Running Pigweed RPC console](#running-pigweed-rpc-console)
-
 For more build options, help is provided when running the build script without
 arguments
 
          ```
          ./scripts/examples/gn_efr32_example.sh
          ```
 
-<a name="flashing"></a>
-
 ## Flashing the Application
 
 -   On the command line:
@@ -211,8 +203,6 @@ arguments
 
 -   Or with the Ozone debugger, just load the .out file.
 
-<a name="view-logging"></a>
-
 ## Viewing Logging Output
 
 The example application is built to use the SEGGER Real Time Transfer (RTT)
@@ -271,8 +261,6 @@ combination with JLinkRTTClient as follows:
           $ JLinkRTTClient
           ```
 
-<a name="running-complete-example"></a>
-
 ## Running the Complete Example
 
 -   It is assumed here that you already have an OpenThread border router
@@ -413,7 +401,7 @@ tracking code inside the `trackAlloc` and `trackFree` function
 
 For the description of Software Update process with EFR32 example applications
 see
-[EFR32 OTA Software Update](../../../docs/guides/silabs_efr32_software_update.md)
+[EFR32 OTA Software Update](../../../../docs/guides/silabs_efr32_software_update.md)
 
 ## Building options
 

diff --git a/examples/window-app/silabs/SiWx917/README.md b/examples/window-app/silabs/SiWx917/README.md
@@ -26,8 +26,6 @@ An example showing the use of CHIP on the Silicon Labs EFR32 MG12 and MG24.
 > release with added tools and documentation.
 > [Silabs Matter Github](https://github.com/SiliconLabs/matter/releases)
 
-<a name="intro"></a>
-
 ## Introduction
 
 The EFR32 window-covering example provides a baseline demonstration of a Window
@@ -48,8 +46,6 @@ The window-covering example is intended to serve both as a means to explore the
 workings of Matter as well as a template for creating real products based on the
 Silicon Labs platform.
 
-<a name="building"></a>
-
 ## Building
 
 -   Download the
@@ -145,15 +141,11 @@ Silicon Labs platform.
           $ gn gen out/debug --args='import("//with_pw_rpc.gni")'
           $ ninja -C out/debug
 
-    [Running Pigweed RPC console](#running-pigweed-rpc-console)
-
 For more build options, help is provided when running the build script without
 arguments
 
          ./scripts/examples/gn_efr32_example.sh
 
-<a name="flashing"></a>
-
 ## Flashing the Application
 
 -   On the command line:
@@ -163,8 +155,6 @@ arguments
 
 -   Or with the Ozone debugger, just load the .out file.
 
-<a name="view-logging"></a>
-
 ## Viewing Logging Output
 
 The example application is built to use the SEGGER Real Time Transfer (RTT)
@@ -213,8 +203,6 @@ combination with JLinkRTTClient as follows:
 
           $ JLinkRTTClient
 
-<a name="running-complete-example"></a>
-
 ## Running the Complete Example
 
 -   It is assumed here that you already have an OpenThread border router
@@ -344,13 +332,11 @@ combination with JLinkRTTClient as follows:
           # Add Ipv6 route on PC (Linux)
           $ sudo ip route add <Thread global ipv6 prefix>/64 via 2002::2
 
-<a name="running-pigweed-rpc-console"></a>
-
 ## OTA Software Update
 
 For the description of Software Update process with EFR32 example applications
 see
-[EFR32 OTA Software Update](../../../docs/guides/silabs_efr32_software_update.md)
+[EFR32 OTA Software Update](../../../../docs/guides/silabs_efr32_software_update.md)
 
 ## Building options
 

diff --git a/integrations/docker/images/build-all.sh b/integrations/docker/images/build-all.sh
@@ -21,7 +21,7 @@
 #  https://github.com/project-chip/connectedhomeip/issues/710
 #
 set -e
-find "$(git rev-parse --show-toplevel)"/integrations/docker/images/ -name Dockerfile ! -path "*chip-cert-bins/*" ! -path "*chip-build-remote-builder/*" | while read -r dockerfile; do
+find "$(git rev-parse --show-toplevel)"/integrations/docker/images/ -name Dockerfile ! -path "*chip-cert-bins/*" | while read -r dockerfile; do
     pushd "$(dirname "$dockerfile")" >/dev/null
     ./build.sh "$@"
     popd >/dev/null

diff --git a/integrations/docker/images/chip-build-remote-builder/Dockerfile b/integrations/docker/images/chip-build-remote-builder/Dockerfile
diff --git a/integrations/docker/images/chip-build-remote-builder/README.md b/integrations/docker/images/chip-build-remote-builder/README.md
diff --git a/integrations/docker/images/chip-build-remote-builder/build.sh b/integrations/docker/images/chip-build-remote-builder/build.sh
diff --git a/integrations/docker/images/chip-build-remote-builder/cloudbuild.yaml b/integrations/docker/images/chip-build-remote-builder/cloudbuild.yaml