lowRISC / lowRISC/opentitan

[ci,fpga] Temporarily disable flaky FPGA `manuf` tests

Open
#30,922 1 comment 0 reactions 1 assignee View on GitHub

@thommythomaso is already working on this.

Since Aug 5, 2026.

Component:FPGA Triage Priority
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

We disabled the following tests to increase the stability of the FPGA tests in CI. As soon as the underlying cause, described in https://github.com/lowRISC/opentitan/issues/29555, has been identified, these test will be re-enabled.

* cp_provision_functest_fpga_cw340_rom_with_fake_keys
* manuf_cp_ast_test_execution_test_unlocked0_functest_fpga_cw340_sival
* manuf_cp_ast_test_execution_test_unlocked1_functest_fpga_cw340_sival
* manuf_cp_ast_test_execution_test_unlocked2_functest_fpga_cw340_sival
* manuf_cp_ast_test_execution_test_unlocked3_functest_fpga_cw340_sival
* manuf_cp_ast_test_execution_test_unlocked4_functest_fpga_cw340_sival
* manuf_cp_ast_test_execution_test_unlocked5_functest_fpga_cw340_sival
* manuf_cp_ast_test_execution_test_unlocked6_functest_fpga_cw340_sival
* manuf_cp_ast_test_execution_test_unlocked7_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked0_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked0_to_prod_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked1_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked1_to_prod_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked2_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked2_to_prod_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked3_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked3_to_prod_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked4_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked4_to_prod_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked5_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked5_to_prod_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked6_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked6_to_prod_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked7_to_prod_end_functest_fpga_cw340_sival
* manuf_cp_device_info_flash_wr_test_unlocked7_to_prod_functest_fpga_cw340_sival
* e2e_emulation_cw340_test
* e2e_emulation_dice_cwt_cw340_test
* e2e_emulation_tpm_cw340_test
* e2e_ate_individ_test_cw340
* e2e_emulation_cw340_multistage_test
* e2e_emulation_dice_cwt_cw340_multistage_test
* e2e_emulation_tpm_cw340_multistage_test
* e2e_option_flags_test_cw340

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.