Commit Graph
3 Commits
Author SHA1 Message Date
rajamesandClaude Opus 5.5 92ca805ecf Merge master into StarForth-v4.0.0: the branch's build, master's CI files kept
StarshipOS Build / milkv (pull_request) Failing after 38s
StarshipOS Build / pc (pull_request) Failing after 34s
StarshipOS Build / pi4 (pull_request) Failing after 35s
StarshipOS Build / pi5 (pull_request) Failing after 35s
StarshipOS Build / qemu (pull_request) Failing after 34s
StarshipOS Build / Isabelle/HOL Proofs (pull_request) Failing after 1m30s
StarshipOS Build / Documentation (pull_request) Failing after 37s
For PR #30. master's 9 commits since the fork (T= board selection,
mk/boards.mk, build.yml, the nightly workflows) conflicted in four
files; each is resolved to the branch's version:

  .gitea/workflows/nightly.yml       added on both; master's copy named
  .gitea/workflows/nightly-docs.yml  the branch in its checkout, the
                                     branch's builds the default branch
  Makefile                           master's T= and mk/boards.mk against
  kernel/Makefile                    the branch's TARGET=<board> and
                                     boards/; master's edits were to
                                     Makefile.starkernel, renamed here

The two workflows' header comment now says they build master.

Merged cleanly from master: build.yml (its board matrix, Nexus publish
and 02:00 nightly; it still calls Makefile.starkernel and make
T=<board>, which this tree does not have -- #18) and mk/boards.mk
(nothing here includes it).

Against the branch the merge changes only those CI files and
mk/boards.mk: no kernel, v4 or Makefile source, so the build is the one
accepted on 2026-11-06.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
2026-11-06 16:08:22 +00:00
rajamesandClaude Opus 5.5 a5a29cc857 ci: nightly images, nightly documents and tagged releases, in the tree
scripts/nightly.sh, one stage per call, a step each in the workflows:

  accept <amd64|aarch64|riscv64|stick-high>  the acceptance protocol --
        qemu_session.py zuse, and stick_zuse --target qemu-stick-high;
        after the last, dict_hash must be equal on the three
  test-32   make -C v4 test-32
  proofs    isabelle build -c -D proof/ (StarForth checked afresh each run)
  images    the Pi 5 and Mars images, xz for Raspberry Pi Imager
  publish   org.starship:kernelImage: pc (iso), raspi5, milkv (img.xz),
            logs (tar.gz: this run's serial logs, proof log, DoE CSVs)
  docs, publish-docs   book, vol1-3, api -> org.starship:documentation

.gitea/workflows/nightly.yml (03:00) and nightly-docs.yml (04:00) publish
<LITHOS_VERSION>-SNAPSHOT to starshipos-snapshots; release.yml, on a tag
v*, builds and publishes both to starshipos-releases at the tag's version,
refusing a tag that is not v<LITHOS_VERSION>. Until this branch is merged
to master, master carries copies of the two nightlies naming it.

make init: INIT_DOCS=0 leaves out TeX and Doxygen, INIT_PROOFS=0 Isabelle.

Checked here, stage by stage, in order: the four acceptance boots PASS,
dict_hash 0xfec8c47cfc6f437f on the three, test-32 0 failures, StarForth
proved (0:00:41), images built; publish to a local file:// repository,
and the images' publish to Nexus starshipos-snapshots read back byte for
byte. The docs stage and publish-docs: not yet checked when committed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
2026-11-06 15:21:58 +00:00
rajamesandClaude Opus 5.5 7f574c54ff ci: nightly images and nightly documents, from StarForth-v4.0.0, to Nexus
StarshipOS Build / milkv (push) Failing after 2m11s
StarshipOS Build / pc (push) Failing after 2m54s
StarshipOS Build / pi4 (push) Failing after 2m52s
StarshipOS Build / pi5 (push) Failing after 2m24s
StarshipOS Build / qemu (push) Failing after 2m11s
StarshipOS Build / Isabelle/HOL Proofs (push) Failing after 2m57s
StarshipOS Build / Documentation (push) Failing after 2m19s
Gitea runs schedules from the default branch only, so until StarForth-v4.0.0
is merged here, master carries copies of that branch's two nightly
workflows, identical to them but for the checkout's ref:

  nightly.yml       03:00 UTC: the acceptance protocol (zuse amd64, aarch64,
                    riscv64; the PC stick loaded high; dict_hash equal on the
                    three; test-32), the Isabelle/HOL proofs, the board images,
                    then org.starship:kernelImage:<LITHOS_VERSION>-SNAPSHOT --
                    classifiers pc (iso), raspi5, milkv (img.xz), logs
  nightly-docs.yml  04:00 UTC: the book, the formal volumes, the API reference
                    -> org.starship:documentation:<LITHOS_VERSION>-SNAPSHOT

Both publish to starshipos-snapshots as ci-publisher (secret
NEXUS_CI_PASSWORD), and only if every stage before passed. The work is that
branch's scripts/nightly.sh. At the merge, take that branch's copies (this
ref line goes). build.yml's own 02:00 schedule is untouched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
2026-11-06 15:21:15 +00:00