The TC-DGTHREAD-1.1 yaml script is not updated after upgrading from a 1.3 SVE TH version to v2.10+spring2024. The expected value for ClusterRevision in step2 is 2, but the script still expects a value of 1.
Steps to reproduce the behavior
Upgrade from a 1.3 SVE TH version to v2.10+spring2024 following these steps:
cd certification-tool
./scripts/stop.sh
cd ..
sudo rm -rf certification-tool/
git clone https://github.com/project-chip/certification-tool.git
cd certification-tool
git fetch
git checkout v2.10+spring2024
git submodule update --init --recursive
./scripts/ubuntu/auto-update.sh v2.10+spring2024
./scripts/start.sh
Verify that the TH frontend and SHA are displayed as expected.
Check the TC-DGTHREAD-1.1 yaml script and verify that the expected value for ClusterRevision in step2 is 1, however The expected behavior is that the TC-DGTHREAD-1.1 yaml script should be updated after upgrading to v2.10+spring2024, and the expected value for ClusterRevision in step2 should be 2.
I did not encounter any errors during the upgrade process. I am unsure if the issue is related to my upgrade method. Please confirm if this is a known issue or if there is a problem with my upgrade process.
ZainZhongUL
commented
1 month ago
Describe the bug
The TC-DGTHREAD-1.1 yaml script is not updated after upgrading from a 1.3 SVE TH version to v2.10+spring2024. The expected value for ClusterRevision in step2 is 2, but the script still expects a value of 1.
Steps to reproduce the behavior
Upgrade from a 1.3 SVE TH version to v2.10+spring2024 following these steps:
Verify that the TH frontend and SHA are displayed as expected.
Check the TC-DGTHREAD-1.1 yaml script and verify that the expected value for ClusterRevision in step2 is 1, however The expected behavior is that the TC-DGTHREAD-1.1 yaml script should be updated after upgrading to v2.10+spring2024, and the expected value for ClusterRevision in step2 should be 2.
TC-DGTHREAD-1.1 yaml script files TC-DGTHREAD-1.1 yaml script.txt
Environment Operating system: Ubuntu Certification Tool version: v2.10+spring2024
Additional Information
I did not encounter any errors during the upgrade process. I am unsure if the issue is related to my upgrade method. Please confirm if this is a known issue or if there is a problem with my upgrade process.