Skip to content

THIS ONE FIRST: chore: bump dlio-benchmark pin to DLIO #38 merged + #37; version 3.0.23 -> 3.0.24#550

Merged
russfellows merged 2 commits into
mainfrom
chore/bump-version-3.0.24-pull-dlio
Jun 28, 2026
Merged

THIS ONE FIRST: chore: bump dlio-benchmark pin to DLIO #38 merged + #37; version 3.0.23 -> 3.0.24#550
russfellows merged 2 commits into
mainfrom
chore/bump-version-3.0.24-pull-dlio

Conversation

@FileSystemGuy

@FileSystemGuy FileSystemGuy commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Summary

`uv lock --upgrade-package dlio-benchmark` moves the pin from `17d982a3` to `252a54b1`, picking up two DLIO commits.

What changed

  • DLIO PR Create Submission_guidelines.md #37 — restricts default `pytest` to the checkin suite (~85 fast tests, <10 min). The full suite carries aspirational tests expected to fail and takes hours; it must now be invoked explicitly with `pytest tests/ -m full_suite`. No runtime impact on mlpstorage — pure DLIO test-infrastructure cleanup.
  • DLIO PR Add ability to use container to run the benchmark #38 (merged form) — the previous 3.0.23 pin (`17d982a3`) tracked the unmerged tip of Add ability to use container to run the benchmark #38. Upstream main now has the merged commit (`252a54b1`) with the same DIRECT_FS routing for `--o-direct` local O_DIRECT I/O. Switching to the merged SHA keeps mlpstorage aligned with what other DLIO consumers see.

Version bumped 3.0.23 → 3.0.24.

Test plan

  • `uv lock --upgrade-package dlio-benchmark` resolves cleanly.
  • `uv run pytest tests/unit -q` → 2257 passed.

@FileSystemGuy
chore: bump dlio-benchmark pin to DLIO #38 merged + #37; version 3.0.…
877a5cf 
…23 -> 3.0.24

`uv lock --upgrade-package dlio-benchmark` moves the pin from 17d982a3
to 252a54b1, picking up:

  * DLIO PR #37: restrict default `pytest` run to the checkin suite
    (~85 fast tests, <10 min). The full suite ships aspirational tests
    that are expected to fail and takes hours; it must now be invoked
    explicitly with `pytest tests/ -m full_suite`. No runtime impact
    on mlpstorage — pure DLIO test-infrastructure cleanup.
  * DLIO PR #38 (merged form): the previous 3.0.23 pin (17d982a3)
    tracked the unmerged tip of #38. Upstream main now has the merged
    commit (252a54b1) with the same DIRECT_FS routing for --o-direct
    local O_DIRECT I/O. Switching to the merged SHA keeps mlpstorage
    aligned with what other DLIO consumers see.
@FileSystemGuy FileSystemGuy requested a review from a team June 26, 2026 22:10
@github-actions

github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

@FileSystemGuy FileSystemGuy changed the title chore: bump dlio-benchmark pin to DLIO #38 merged + #37; version 3.0.23 -> 3.0.24 THIS ONE FIRST: chore: bump dlio-benchmark pin to DLIO #38 merged + #37; version 3.0.23 -> 3.0.24 Jun 26, 2026
@FileSystemGuy FileSystemGuy mentioned this pull request Jun 27, 2026
Open
4 tasks
russfellows
russfellows approved these changes Jun 28, 2026
View reviewed changes

@russfellows russfellows left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the way.

@russfellows russfellows merged commit e19be52 into main Jun 28, 2026
3 checks passed
@russfellows russfellows deleted the chore/bump-version-3.0.24-pull-dlio branch June 28, 2026 04:41
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@russfellows russfellows russfellows approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@FileSystemGuy @russfellows