Skip to content

fix(ci): disable F3 on lotus until a new lotus image with calibnet F3 initial power table is published#6601

Merged
hanabi1224 merged 1 commit into
mainfrom
hm/disable-bootstrap-checks-lotus
Feb 13, 2026
Merged

fix(ci): disable F3 on lotus until a new lotus image with calibnet F3 initial power table is published#6601
hanabi1224 merged 1 commit into
mainfrom
hm/disable-bootstrap-checks-lotus

Conversation

@hanabi1224
Copy link
Copy Markdown
Contributor

@hanabi1224 hanabi1224 commented Feb 13, 2026

Summary of changes

Lotus cannot bootstrap F3 until initial power table is set. Disable F3 on lotus for now to unblock CI.

https://github.com/ChainSafe/forest/actions/runs/21977918338/job/63495549964?pr=6597#step:6:1501

ERROR: initializing node: starting node: failed to open certstore: getting initial power table: failed to load the F3 bootstrap power table and none is specified in the manifest; could not close datastore: leveldb: closed

Changes introduced in this pull request:

Reference issue to close (if applicable)

Closes #6595

Other information and links

Change checklist

  • I have performed a self-review of my own code,
  • I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
  • I have added tests that prove my fix is effective or that my feature works (if possible),
  • I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Outside contributions

  • I have read and agree to the CONTRIBUTING document.
  • I have read and agree to the AI Policy document. I understand that failure to comply with the guidelines will lead to rejection of the pull request.

Summary by CodeRabbit

  • Chores
    • Updated test environment configurations to disable the F3 subsystem across multiple test services.
    • Updated test filter list to exclude F3-related tests from the test suite.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 13, 2026

Walkthrough

The PR disables the F3 subsystem in Lotus containers used for testing by adding environment variables to two docker-compose configuration files and filters out F3-related RPC parity tests. These are configuration and test filtering changes without modifications to core logic or runtime behavior.

Changes

Cohort / File(s) Summary
Docker Compose Configuration
scripts/tests/api_compare/docker-compose.yml, scripts/tests/bootstrapper/docker-compose-lotus.yml
Added LOTUS_DISABLE_F3_SUBSYSTEM=1 environment variable to disable the F3 subsystem in Lotus service containers.
Test Filtering
scripts/tests/api_compare/filter-list
Added filter entry !Filecoin.F3 with accompanying comment to exclude F3-related tests from the RPC parity test suite.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • LesnyRumcajs
  • sudo-shashank
🚥 Pre-merge checks | ✅ 6
✅ Passed checks (6 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: disabling F3 on lotus in CI until a new lotus image is published.
Linked Issues check ✅ Passed The PR addresses the CI failure in #6595 by disabling F3 subsystem on lotus in docker-compose configurations and test filters.
Out of Scope Changes check ✅ Passed All changes are scoped to disabling F3 subsystem in CI configurations and test filters, directly addressing the CI breakage issue.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch hm/disable-bootstrap-checks-lotus

No actionable comments were generated in the recent review. 🎉


Comment @coderabbitai help to get the list of available commands and usage tips.

…calibnet F3 initial power table is published
@hanabi1224 hanabi1224 force-pushed the hm/disable-bootstrap-checks-lotus branch from 08bb524 to 5075fd1 Compare February 13, 2026 08:08
@hanabi1224 hanabi1224 added the RPC requires calibnet RPC checks to run on CI label Feb 13, 2026
@hanabi1224 hanabi1224 changed the title fix(ci): disable bootstrap-checks-lotus until a new lotus image with calibnet F3 initial power table is published fix(ci): disable F3 on lotus until a new lotus image with calibnet F3 initial power table is published Feb 13, 2026
@hanabi1224 hanabi1224 marked this pull request as ready for review February 13, 2026 08:11
@hanabi1224 hanabi1224 requested a review from a team as a code owner February 13, 2026 08:11
@hanabi1224 hanabi1224 requested review from LesnyRumcajs and removed request for a team February 13, 2026 08:11
@hanabi1224 hanabi1224 enabled auto-merge February 13, 2026 08:24
@hanabi1224 hanabi1224 removed the RPC requires calibnet RPC checks to run on CI label Feb 13, 2026
@hanabi1224 hanabi1224 added this pull request to the merge queue Feb 13, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Feb 13, 2026
@hanabi1224 hanabi1224 added this pull request to the merge queue Feb 13, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Feb 13, 2026
@hanabi1224 hanabi1224 added this pull request to the merge queue Feb 13, 2026
Merged via the queue into main with commit e7ad657 Feb 13, 2026
107 of 115 checks passed
@hanabi1224 hanabi1224 deleted the hm/disable-bootstrap-checks-lotus branch February 13, 2026 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[automated] RPC parity test failure @ 13/2/26 01:02

2 participants