Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tests,chip_rstmgr] Fix comments in rstmgr_sw_rst_ctrl_test #20767

Merged
merged 1 commit into from
Jan 10, 2024

[tests,chip_rstmgr] Fix rstmgr_sw_rst_ctrl_test

39f17a2
Select commit
Loading
Failed to load commit list.
Merged

[tests,chip_rstmgr] Fix comments in rstmgr_sw_rst_ctrl_test #20767

[tests,chip_rstmgr] Fix rstmgr_sw_rst_ctrl_test
39f17a2
Select commit
Loading
Failed to load commit list.
Azure Pipelines / CI failed Jan 8, 2024 in 1h 46m 20s

Build #20240108.31 had test failures

Details

Tests

  • Failed: 2 (0.03%)
  • Passed: 6,322 (99.84%)
  • Other: 8 (0.13%)
  • Total: 6,332

Annotations

Check failure on line 558 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI

Build log #L558

Bash exited with code '1'.

Check failure on line 16745 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI

Build log #L16745

Bash exited with code '3'.

Check failure on line 24612 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI

Build log #L24612

Bash exited with code '3'.

Check failure on line 1 in sw/device/silicon_creator/rom/e2e/bootstrap/e2e_bootstrap_rma_fpga_cw310_rom_with_fake_keys.bash

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI

sw/device/silicon_creator/rom/e2e/bootstrap/e2e_bootstrap_rma_fpga_cw310_rom_with_fake_keys.bash

exited with error code 101

Check failure on line 1 in sw/device/tests/spi_device_smoketest_fpga_cw310_test_rom.bash

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI

sw/device/tests/spi_device_smoketest_fpga_cw310_test_rom.bash

exited with error code 142