Skip to content

fix(melpa): serialize forge's sqlite3 module build across the oracle's two editors #429

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eval-exec merged 1 commit into from
Sep 22, 2026
Merged

fix(melpa): serialize forge's sqlite3 module build across the oracle's two editors #429

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions crates/neomacs-melpa-tests/src/parity_tests/forge.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,15 @@ use crate::{CachedMelpaOracle, FORGE_MELPA_PIN};
use super::batch_support::{ParityBatchCase, assert_oracle_batch_cases};

const PRELUDE: &str = r####"
;; sqlite3.el lazily compiles its native module inside the shared
;; prepared package tree, and the batch oracle evaluates GNU Emacs and
;; Neovm concurrently against that same tree. Serialize the two builds;
;; make deletes the intermediate sqlite3-api.o after linking, so two
;; unsynchronized builds race on it and the slower link fails.
(setenv "SQLITE3_API_BUILD_COMMAND"
(format "flock -w 600 %s make all"
(expand-file-name "tmp/forge-sqlite3-build.lock"
(getenv "NEOMACS_TEST_WORKSPACE_ROOT"))))
Comment on lines +15 to +18
(setq forge-add-default-sections nil
forge-add-default-bindings nil)
(defvar neomacs-forge-test-original-max-lisp-eval-depth
Expand Down
Loading