Skip to content

fix: rebenchmark crash during finishing#1523

Open
v0i0 wants to merge 6 commits into
mainfrom
v0i0/fix-finishing-oom
Open

fix: rebenchmark crash during finishing#1523
v0i0 wants to merge 6 commits into
mainfrom
v0i0/fix-finishing-oom

Conversation

@v0i0
Copy link
Copy Markdown
Contributor

@v0i0 v0i0 commented Feb 20, 2026

apparently, rebenchmark itself will not filter for invalid configs, so we need to do it beforehand.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Meta Open Source bot. label Feb 20, 2026
@v0i0 v0i0 marked this pull request as draft February 20, 2026 17:34
@v0i0
Copy link
Copy Markdown
Contributor Author

v0i0 commented Feb 23, 2026

learned that reduction_loop is special in terms of getting reset, so skipping minimizing that.

@v0i0 v0i0 marked this pull request as ready for review February 25, 2026 17:50
@v0i0 v0i0 force-pushed the v0i0/fix-finishing-oom branch 2 times, most recently from c8495ec to 64ff80d Compare February 27, 2026 17:23
@v0i0
Copy link
Copy Markdown
Contributor Author

v0i0 commented Feb 27, 2026

@v0i0 v0i0 force-pushed the v0i0/fix-finishing-oom branch 2 times, most recently from 7974589 to f451c9e Compare March 7, 2026 16:09
v0i0 and others added 6 commits March 9, 2026 15:19
…uction_loops

MagicMock(spec=ConfigSpec) doesn't expose instance attributes set in
__init__, so user_defined_tunables needs to be set explicitly on the mock.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@v0i0 v0i0 force-pushed the v0i0/fix-finishing-oom branch from f451c9e to b4641be Compare March 9, 2026 15:46
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented Apr 4, 2026

Hi @v0i0!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants