Skip to content

Fix the Linux Turnip build and release - #7

Merged
maxjivi05 merged 4 commits into
mainfrom
fix/linux-turnip-ci
Sep 28, 2026
Merged

maxjivi05 merged 4 commits into
mainfrom
fix/linux-turnip-ci

Conversation

@maxjivi05

Copy link
Copy Markdown
Contributor

The Linux Turnip build failed on current Mesa main and never ran from main, so no Linux release was built after #6.

  • Rebase the five Mesa patches onto Mesa 1887e21. Upstream removed tu_has_multiview and moved the a8xx quirks into their own section. The code the patches add is unchanged.
  • Anchor apply_a7xx_gen1_quirks.py on the whole a7xx_gen1 block. Upstream renamed the quirks, so the script silently skipped, and the Android builds on main were missing the A720/A725/A730 overrides.
  • Make verify_patches.sh fail when a patch script prints WARNING or FATAL during the patch stage. That skip had passed the Android check.
  • Build Linux Turnip on pushes to main and drop the second scheduler that called feature/linux-drivers. Push builds get their own concurrency group so they can't cancel a pending release.

Tested with a local build of both variants against Mesa 1887e21: all five patches apply and both packages verify. The gen1 script was tested on old and new Mesa layouts and edge cases, and verify_patches.sh against the Android log from main.

Upstream Mesa renamed the a7xx_gen1 quirks to QCTDD ids, so the exact-text
anchor stopped matching and every build since has shipped A720/A725/A730
without the early preamble and scalar predicate overrides.

Match the block itself, ending at its first unindented line, and set each
override in place or add it, so renamed or upstream-set keys still apply.
The a7xx_gen1 skip above passed verification: the check only looked for
each script's "done" line, which prints on every path. Fail on any WARNING
or FATAL line in the patch stage. Deliberate skips such as the autotune
drawcall gate print neither.
Mesa 1887e21 removed tu_has_multiview and moved the a8xx quirks into their
own section, so 0001 and 0003 no longer applied. The code the patches add
is unchanged.
The Linux workflow only ran for pushes to feature/linux-drivers, and main
had two weekly schedulers after both branches merged. Build pushes to main,
keep the workflow's own schedule, and drop the reusable-workflow scheduler.
Push builds get their own concurrency group so they cannot cancel a pending
release.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-28T11:27:10.676969Z 5886f72 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@maxjivi05
maxjivi05 merged commit c5531f8 into main Sep 28, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant