[codex] Remove smol runtime#1549
Open
svarlamov wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
smoldependency and stale lockfile entries.smoltask/unblock usage with Tokio semaphores andspawn_blocking.Validation
cargo check --all-targetstask fmttask linttask test TEST_FILTER=rebase_realworld::test_human_conflict_python_pipeline_mixed_baseline_c3_conflictafter one transient full-suite daemon timeouttask testclean rerunrg -n "\\bsmol\\b|smol::" -S Cargo.toml Cargo.lock src tests docsreturns no matchesNotes
The initial full
task testrun had one daemon completion timeout inrebase_realworld::test_human_conflict_python_pipeline_mixed_baseline_c3_conflict; the exact test passed on rerun and the subsequent full suite passed cleanly.