Repository navigation
End-to-end scenario for update --devel on a -git package (3.5.0-DEV27), F24 filed - #13
Merged
Merged
Conversation
A new 35-update-devel scenario builds a -git stand-in whose only source is a local git repository, so no network is needed. With no new commit, update --devel plans UP_TO_DATE and rebuilds nothing. After a commit it plans and installs the new pkgver(). build_state.toml records the commit each build used. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Q1 resolves to build time, generalised from the kernel to any installed package: a new bench target times a package's build() under its resolved profile with the stock and the sysforge clang, interleaved. Runtime measurement stays out of scope. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Implements
3.5.0-DEV27and files3.5.0-F24. The F24 change used to be the standalonedocs/roadmap-q1branch.3.5.0-DEV27.tools/e2e/scenarios/35-update-devel.shbuilds a new stand-in,tools/e2e/pkgs/e2e-hello-git. Its only source is agit+file://repository the scenario creates, so the scenario needs no network. It checks three things:update --devel --dry-run --jsonplansUP_TO_DATE.update --devel --yesthen leaves both the installed version andbuilt_atunchanged.NEEDS_REBUILD r2.<sha>-1and that version gets installed.build_state.tomlbuilt_upstream_commitmatches the upstreamHEADafter each build. That record is what the next run'sgit ls-remoteshort-circuit reads.The URL is written into the PKGBUILD copy as a literal path, not
$HOME. Otherwise the static parser can't resolve it, and both the short-circuit and the commit record are skipped. The AUR half of3.5.0-B144needs a real AUR package and is out of scope, as the ROADMAP entry said.3.5.0-F24. Promotes3.5.0-Q1tobench package <pkg>in ROADMAP. It only changes ROADMAP.Test tier: this is the
make e2etier (state that one command leaves for the next).Checklist
docs/release-notes/unreleased.md, led by its roadmap IDmake check-surfacepasses, snapshot unchanged)docs/guides/) still describes it correctly: n/amake pre-release(ormake ci-local) passes locally: ranmake test(7712 passed, 4 skipped),make e2e SCENARIO=update-devel(PASS), lint,check-standards,check-roadmap-table,check-surface,check-design; not the fullpre-release🤖 Generated with Claude Code