Repository navigation
Description
Summary
The daily OBS-Studio-Rust beta has not published since the 2026-10-23 14:09 run (39967273880). Every release-rust.yaml run since 40097160881 (2026-10-24 13:12) has failed: 14 consecutive runs, and the 2026-10-28 01:17 dispatch was cancelled before it could finish.
The publishing jobs never run because the app builds they consume fail, so this is one outage with two independent causes, not a series of unrelated reds.
Evidence (runs and jobs, read from the logs)
| run | head | started | failing jobs |
|---|---|---|---|
40097160881 |
af31b65c9 |
10-24 13:12 | first failure of the series |
40198552343 |
38deb4d26 |
10-25 13:38 | |
40240506753 |
7992b0b89 |
10-25 22:30 | |
40352480030 |
4729f1270 |
10-26 15:45 | |
40409686763 |
107b24733 |
10-26 22:05 | |
40529110726 |
b926b01c4 |
10-27 15:15 | |
40590282093 |
8219c7f1f |
10-27 21:52 | Build windows x64/arm64, Build linux x86_64, gate Flatpak/Windows/macOS/Ubuntu, Launch packaged Windows x64/arm64, Rust Tier 2 windows |
40594533995 |
8646ef97b |
10-27 22:24 | same set, no Flatpak |
Cause 1 — Linux app build: -Werror=pedantic on the SWIG Lua sources (already fixed on master)
Build linux x86_64 🧱 (job 122507234793, run 40594533995):
shared/obs-scripting/obs-scripting-lua-frontend.c.h:23:75: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic]
shared/obs-scripting/obs-scripting-lua-source.c.h:110:81: error: ... [-Werror=pedantic]
shared/obs-scripting/obs-scripting-lua.h:200:80: error: ... [-Werror=pedantic]
cc1: all warnings being treated as errors
This is #2711, fixed by #2712 (d82a994e4, merged 2026-10-28T00:10Z) — after that run started, so it is stale. The next release run should pass this job; I did not re-run it to confirm.
Cause 2 — Windows app build: C2220: the following warning is treated as an error
Build windows x64 🧱 (job 122507234744) fails in three files, and Build windows arm64 🧱 with it:
| file:line | warning | note |
|---|---|---|
plugins/win-capture/graphics-hook/d3d11-capture.cpp.hpp(14,10), (20,10) |
C4201 nameless struct/union | the anonymous unions in struct d3d11_data |
plugins/win-capture/graphics-hook/d3d12-capture.cpp.hpp(24,10) |
C4201 | same shape |
libobs/obs-windows.c.h(1129,25) |
C4113 parameter-list mismatch | GetProcAddress/os_dlsym assigned through void * |
libobs/obs-win-crash-handler.c.h(345,1), (513,1) |
C4701 possibly-uninitialized func_offset, C4702 unreachable code |
CMAKE_COMPILE_WARNING_AS_ERROR defaults to ON (cmake/common/compiler_common.cmake:95), so these are hard errors in the app lanes. None of them is visible to PR CI: no PR path builds the OBS app (ci/ci_scope.py), so master can be unpublishable with every PR green.
These are the same files the /W4 ratchet PR #2691 already changes (libobs/obs-windows.c.h, libobs/obs-win-crash-handler.c.h, plugins/win-capture/graphics-hook/d3d11-capture.cpp.hpp, d3d12-capture.cpp.hpp), where they are being closed wave by wave. So the Windows half of this outage clears when #2691 lands; the open question is whether the beta waits for it (see below).
Cause 3 — downstream, not independent
Release gate 🚦 (macOS arm64/x86_64, Windows x64, Ubuntu) and Launch packaged Windows x64/arm64 🧪 fail with the builds they consume missing. Release gate 🚦 / Flatpak 📦 fails in Build Flatpak Manifest 🧾 with the known-flaky The process '/app/bin/xvfb-run' failed with exit code 1 (#2702 note), which also fails on heads that predate any branch under test.
Not verified
- The macOS gate reds: I read the job list, not their logs, so I am not claiming a cause.
- arm64 Windows: assumed identical to x64 from the same job names; I did not open its log.
- Whether the next release run goes green on Linux after build(obs-scripting): Exempt the Lua SWIG sources from -Wpedantic (#2711) #2712.
Proposal
- Land build(msvc): Compile C/C++ at /W4 and drop the dead /WX link option (#2626) #2691 (its changed files are exactly this failure's sites), or cherry-pick those four fixes to master if the full
/W4wave is not ready — the beta is blocked either way. - Add a scheduled-release smoke signal: a cheap
workflow_dispatch-only job that builds the Windows app from master on every push tomasterfor the paths the app build compiles (libobs/**,plugins/**,shared/**,cmake/**), so a master-only compile break cannot sit for two days behind green PR runs. - Re-dispatch
release-rust.yamlon master once (1) lands and confirm the beta publishes.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
zackees commentedon Oct 28, 2026
Claiming: investigation — verify the two causes in this report against current master and pin down what still blocks the beta.
Plan:
d82a994e4) by reading the newestrelease-rust.yamlrun onmaster, not by inference.40594533995(the report explicitly does not claim a cause there) and say whether those reds are the missing builds or an independent failure.zackees commentedon Oct 28, 2026
Investigation verdict (worker tick, obs-studio3): the two "unknown" parts of the report are now resolved, and neither is a master defect. The Windows half is the whole remaining blocker and it is already owned by #2691.
Read from the job logs of run
40594533995(head8646ef97b, branchwip/2626-w4-enumerate), not inferred:macOS gate reds are not the missing builds — they are a stale head
Release gate 🚦 / macOS 🍏 (arm64)(job122508468974) and(x86_64)(122508469017) both die in the stepRun soldr rustup toolchain install:Build macos arm64 🧱(122507234584) andBuild macos x86_64 🧱(122507234814) succeeded in the same run, so the gate red is independent of the packaged app — it is exactly the #2699 shape (soldrcalled with nozackees/setup-soldrin the job), and it is already fixed on master:fc97f5fceci: Set Up soldr in the macOS and Windows app builds (infra: macOS and Windows app builds fail: 'soldr' is not installed before 'soldr rustup toolchain install' (#2650 regression) #2699) (ci: Set Up soldr in the macOS and Windows app builds (#2699) #2701), merged 2026-10-27T22:20Z.git merge-base --is-ancestor fc97f5fce 8646ef97b→ not an ancestor: the run's head predates the fix.On current master (
fc0352611)build-project.yaml's macOS job carriesSet Up soldr 🦀beforeAdd the Rust x86_64 macOS target 🦀, and a scan of every workflow withci/test_soldr_rustup.py'ssoldr_jobs_without_setup()reports zero jobs that callsoldrwithout setup-soldr (build-project.yaml10 calls,release-rust.yaml2, no composite action calls soldr). So no new pin is warranted — that invariant test already exists and is file-scoped but currently green everywhere.Ubuntu gate red is the #2712 cause, also stale
Release gate 🚦 / Ubuntu 🐧 (OBS-Studio-Rust)(122508469032):That is #2711, fixed by
d82a994e4(#2712), merged 2026-10-28T00:00Z — also not an ancestor of8646ef97b. Same forCross Compile 🧰(122508469080), which stops in the same Lua SWIG TU pluslibobsTUs from the same branch.Windows is the only live blocker, and #2691 owns it
On current master the sites the report lists are still unfixed, and they are byte-for-byte the files #2691 changes:
plugins/win-capture/graphics-hook/d3d11-capture.cpp.hpp:12anonymousunion {plugins/win-capture/graphics-hook/d3d12-capture.cpp.hpp:23anonymousunion {libobs/obs-windows.c.h:1119-1120= (void *)GetProcAddress(...)libobs/obs-win-crash-handler.c.h:287DWORD64 func_offset;fix/2626-msvc-w4(PR #2691, CLEAN, draft) has averify_onlydispatch queued since 03:00Z — run40624175646— which is the build that decides whether the beta can publish. I did not duplicate it.Not verified by me
release-rust.yamlrun onmastersince the fix merged (newest master run is40529110726, 10-27T15:15Z, before it). It needs one dispatch after build(msvc): Compile C/C++ at /W4 and drop the dead /WX link option (#2626) #2691 lands, which is the coordinator's step, not a local claim.Recommendation (no PR from me for this)
The beta unblocks when #2691 lands and
release-rust.yamlis re-dispatched on master — nothing else in this report is master-side work. On proposal 2 (a push-to-master Windows app-build smoke signal): that adds a ~12-minute app build to every master push, so it is a maintainer cost decision, not a worker edit; if it is wanted, the cheapest shape is aworkflow_dispatch-only job inbuild-project.yamlreusing the existingwindows-buildsteps behind a path filter, not a new workflow.zackees commentedon Oct 28, 2026
Releasing: investigation — verdict posted above; no worker PR follows from it.
The remaining unit is the Windows app build, which lives in #2691 (
fix/2626-msvc-w4, CLEAN, verify_only dispatch40624175646queued since 03:00Z). The Linux and macOS gate reds in this outage are stale heads (8646ef97bpredates bothfc97f5fce#2699/#2701 andd82a994e4#2711/#2712), not master defects. Whoever picks this issue up next only needs the post-#2691 master dispatch and the beta confirmation.zackees commentedon Oct 28, 2026
Claiming: investigation — the report's Cause 2 does not apply to master, so the beta is not waiting on #2691. I dispatched the end-to-end proof on current master and will report its result.
The Windows app build on master is green; Cause 2 is branch-only
Run
40529110726(headb926b01c4, the lastScheduledrelease run) job table, read from the API:Build windows x64 🧱Build windows arm64 🧱Build linux x86_64 🧱Build macos arm64 🧱/Build macos x86_64 🧱Release gate 🚦 / Windows 🪟 (x64)and(arm64)Launch packaged Windows x64 🧪/arm64 🧪The C2220 sites in Cause 2 (
d3d11-capture.cpp.hppC4201,obs-windows.c.hC4113,obs-win-crash-handler.c.hC4701/C4702) were reported by run40594533995, whose head iswip/2626-w4-enumerate— a branch that has/W4on. Master is still/W3, where those are warnings, not-Werror. So the Windows half of this outage is not a master defect and does not block publishing; raising the level is #2691's change to make, on its own schedule.The two reds on that master run are both fixed after its head
libobs/media-io/audio-math.h:38:25: error: conversion from 'double' to 'float' may change value [-Werror=float-conversion](cargo:warning=from obs-c-oracle). Fixed by058448ae7(Drop the double cast in db_to_mul, fix(media-io): Drop the double cast in db_to_mul that -Wconversion rejects on MinGW (#516) #2651/build: Maximum C/C++ warning strictness with -Werror on every platform (cross-compiled with soldr) #516), which is inorigin/masterand not inb926b01c4.subprocess.TimeoutExpired: … timed out after 30 seconds; the live-processsampleis parked in__semwait_signal, i.e. the shutdown hang, not a missing artifact (no.ipswas written). Both known teardown races in that window are already fixed on master by the submodule bumpsdd5d9226b(bounded session drain, fix(obs-websocket): Bump the submodule to the bounded session drain #2722) andc805ee479(onClose null-session, bug: obs-websocket: onClose() inserts a null session with _sessions[hdl] and dereferences it #2720) — again absent fromb926b01c4.Action taken
Dispatched
release-rust.yaml -f verify_only=trueon masterfc0352611→ run40627344990(queued 03:33Z). It builds and gates the candidate packages and publishes nothing, so it is the harmless answer to "does the beta publish on today's master". Publishing itself stays a maintainer/schedule action.If that run is green, the outage closes with the next daily and nothing needs cherry-picking from #2691. Cause 1 (
-Werror=pedanticon the Lua SWIG sources) is likewise stale, fixed byd82a994e4(#2711/#2712), and the macOS gatecommand not found: soldrreds byfc97f5fce(#2699/#2701).zackees commentedon Oct 28, 2026
Result of the master dispatch (run
40627344990, headfc0352611): the two known causes are confirmed fixed on master, and one new master-only red appeared — in macOS packaging, not in the app build.Release gate 🚦 / Fast Gate ⚡-Wfloat-conversioninaudio-math.hgone)Build windows x64 🧱/arm64 🧱Release gate 🚦 / Windows 🪟 (x64)and(arm64)Launch packaged Windows x64 🧪/arm64 🧪Native macOS x86_64 DMG startup 🧪dd5d9226b+c805ee479submodule bumps are the fixBuild macos arm64 🧱Package OBS-Studio-Rust 📀Native macOS arm64 DMG startup 🧪Unable to download artifact(s): Artifact not found for name: obs-studio-rust-macos-arm64The arm64 build failure is not a compile problem (compilation, codesign and the
.appall succeeded).hdiutil detach /Volumes/obs-studio-…-macos-applefailed once withResource busy, the half-ejected volume removed the mountpoint, and the retry loop then failed all five attempts on the now-missing path and aborted with "Disk image creation failed". Filed as #2728 with the fix in PR #2729 (detach retried by device node; already-unmounted counts as success).So: Cause 1 and the macOS gate/startup reds are stale-head artifacts; Cause 2 was never a master defect; publishing is blocked only by this intermittent packaging abort. Once #2729 lands, re-dispatch
release-rust.yamlon master and the beta should publish.zackees commentedon Oct 28, 2026
#2729 (
infra/2728-dmg-detach-retry) merged at 04:18Z, so master is now25fc4bc6e(frontend: Save the last dock layout that was not clamped (#2727)), and the re-dispatch this comment asked for is running:release-rust.yaml -f verify_only=true, head25fc4bc6e, dispatched 04:21Z.verify_onlypublishes nothing, so this is the probe and not the beta itself. What it settles:Build macos arm64 🧱/Package OBS-Studio-Rust 📀— whether the device-node detach survives theResource busy→ half-ejected-volume sequence that aborted 40627344990. If this job is green, the release-only red is gone and a publishing run is the maintainer's call, not another verify.Native macOS arm64 DMG startup 🧪— the first arm64 packaged startup on a head that carries both teardown fixes (submodule777071b), which is also the evidence macOS arm64: packaged app crashes (SIGSEGV) during shutdown after reloading a saved capture profile #2432 is waiting on.If
Packageaborts again, the new log line to look for is ahdiutil: detach failedthat repeats past attempt #1 on the path form (deviceresolution returning empty), not the originalNo such file or directoryon all five attempts.zackees commentedon Oct 28, 2026
The macOS red from the master dispatch (run
40627344990,Build macos arm64 🧱) is fixed on master: #2729 merged ase1f0c8b-tip at 04:18 UTC, sohdiutil detachretries the device instead of a path the first attempt destroyed. Nothing else from that run is open: the Windows app build and the beta's publication stay in #2691's queue path.zackees commentedon Oct 28, 2026
Correction to the hash in my previous comment: #2729 merged as
25fc4bc6e1(25fc4bc) at 04:18 UTC. Everything else in that comment stands.zackees commentedon Oct 28, 2026
The packaging blocker is gone: #2729 landed on master as
25fc4bc6e(detach retried by device node; an already-unmounted volume counts as success).State of the outage on master today:
-Werror=pedanticd82a994e4(#2712), verified green inverify_onlyrun40627344990command not found: soldrfc97f5fce(#2701)-Wfloat-conversioninaudio-math.h058448ae7(#2651), green in the same run40627344990(thedd5d9226b+c805ee479bumps)/W4-branch-only, owned by #2691)So nothing on master blocks publishing now; the next
release-rust.yamlrun (scheduled or dispatched) should publish. Publishing itself I left to the schedule.verify_onlyrun40627344990covered everything except the arm64 packaging path that #2729 fixes, so a fresh run is the remaining confirmation. I did not dispatch another one: run40630083913(on #2691's branch) has been sitting in the release workflow's queue for over an hour, so the queue is backed up and another dispatch would only add to it.zackees commentedon Oct 28, 2026
Result of the re-dispatch on master
25fc4bc6e(run 40631862829,verify_only=true): the packaging abort is gone and the arm64 DMG builds again.Build macos arm64 🧱(job 122630072405)created: …obs-studio-33.0.0-beta6-25fc4bc6e-macos-apple.dmg; packaged identity verified, volumeOBS-Studio-Rust 0.1.0-beta.20261028 (Apple), 215 MBNative macOS arm64 DMG startup 🧪Native macOS x86_64 DMG startup 🧪Release gate 🚦 / macOS 🍏 (arm64)This is the same job that aborted at
Package OBS-Studio-Rust 📀in 40627344990. In this run the detach succeeded on the first attempt (noResource busy, so the new retry branch was not exercised on the runner) — the honest reading is that the lane is unblocked and the fix does not regress, not that the retry path was demonstrated.Nothing else is red in the macOS or Windows app lanes so far; the Linux gate jobs are still running at the time of writing.
So the four causes this issue tracked are now all addressed on master: the stale-head
-Wfloat-conversionred, the Windows/W4tail (still a scope decision on #2626), the rtmp-services teardown join, and this macOS packaging abort. Publishing the beta is now a maintainer call, not a blocked step —verify_onlypublishes nothing, so a realrelease-rust.yamldispatch on25fc4bc6eor later is what actually restores the daily beta. If the packaging abort returns on that run, the log to read isPackage OBS-Studio-Rust 📀for ahdiutil: detach failedthat repeats on the path form, plus whetherhdiutil infoproduced a/dev/disk*device for the mountpoint at all.zackees commentedon Oct 28, 2026
Addendum — run 40631862829 finished green end to end (conclusion
success, 04:59Z), with zero failed jobs:verify_onlyskips publishing.That is the whole gate this issue said was unreachable, on head
25fc4bc6e. So the state is: nothing red is left on the release path, and the only remaining step is a real publishing dispatch (verify_onlypublishes nothing). Recommendation: dispatchrelease-rust.yamlon master as-is — if the beta publishes, this issue closes with it.zackees commentedon Oct 28, 2026
Status: coordinator tick — dispatched the real publishing run on master
25fc4bc6eafter the greenverify_onlyrun40631862829.Run: https://github.com/obs-rust/obs-studio/actions/runs/40644942239 (
workflow_dispatch,verify_only=false, started 06:37Z).This is the end-to-end proof this issue asked for: if the beta publishes, the outage is closed with it. I will leave this issue open until the run's publishing job succeeds; if the packaging abort returns, the log to read is
Package OBS-Studio-Rustfor a repeatedhdiutil: detach failed.zackees commentedon Oct 28, 2026
The beta published — the outage is closed with the proof this issue asked for.
Run 40644942239 (
release-rust.yaml,verify_only=false, head25fc4bc6e) finishedsuccessat 07:14Z, and releaseobs-studio-rust-v0.1.0-beta.20261028was created at 07:13Z with every asset:linux-x86_64.AppImage(+.zsync),linux-x86_64.flatpak,ubuntu-26.04-x86_64.deb,macos-arm64.dmg,macos-x86_64.dmg,windows-x64.zip,windows-arm64.zip, both-symbols.zip, andSHA256SUMS.What fixed it, by cause:
-Werror=pedanticon the Linux app buildd82a994e4)command not found: soldrfc97f5fce)hdiutil detachon a path the first attempt destroyed25fc4bc6e)Verified first with the green
verify_onlyrun 40631862829 on the same head, then with this publishing run, so the publish is no longer resting on inference. The last good beta was 2026-10-23; the gap was 2026-10-24 → 2026-10-28.Nothing is left from this report. The
Pre-releaseflag on the new tag and20261023stayingLatestare the release workflow's normal beta behaviour, not a regression from this outage.