TestPledgeMaxBatching Flaky

[ZenGround0]

Checklist

• This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not an enhancement request. If it is, please file a improvement suggestion instead.
• I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• I did not make any code changes to lotus.

Lotus component

• lotus daemon - chain sync
• lotus miner - mining and block production
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt)
• lotus miner/market - storage deal
• lotus miner/market - retrieval deal
• lotus miner/market - data transfer
• lotus client
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

Lotus Version

NA, testing on branch `chore/update-gst-migration-fixes` at `a7a2ac094`, CI link: https://app.circleci.com/pipelines/github/filecoin-project/lotus/23818/workflows/9ce73ac3-638f-47e3-9c42-d43b9febf8d1/jobs/633544

Describe the Bug

TestPledgeMaxBatching/Force_max_prove_commit_aggregate_size flaky

Logging Information

Lost the logs but I think I remember seeing expected 821 got 2.  This kind of makes sense as max aggregated ProveCommits is 819, the difference between these two numbers

Repo Steps

Run TestPledgeMaxBatching enough times

[rjan90]

Closing this ticket as outdated. Lotus has moved from CircleCI to GHA, and we are currently monitoring Flaky jobs over time in this Grafana dashboard.

We have also consolidated flaky test reports into a single tracking issue here: #12001