You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a1b0ae9
Browse filesBrowse the repository at this point in the historyBrowse files
Give each release upgrade test binary its own shared library tree (#4742)
The minor release upgrade test builds each `seid` with its worktree
mounted at `/sei-protocol/sei-chain`, so every cgo rpath points at the
same path, and the validators run both binaries from a mount of the main
checkout. #4207 staged release libraries only where main lacked a file
of the same name, so a library both trees ship under one name, such as
`sei-wasmvm/internal/api/libwasmvm.x86_64.so`, always resolved to main's
copy and the release nodes ran main's libwasmvm. The same applied to the
main binary when `target_ref` differs from the checked-out commit. Today
the release/v6.6, v6.7 and v6.8 copies are byte-identical to main's, so
no run has been affected yet, but the first libwasmvm change on main
would be masked silently.
`build_binary` now mounts each worktree at `build/upgrade-test/<label>`
under the repo mount, and `stage_shared_libraries` copies every `.so` of
that worktree to the same path, so the release and main binaries each
resolve only their own tree. `verify_shared_libraries` runs `ldd` in
every validator against the running release binary and the staged main
binary, and fails the run if a library is missing or resolves from
outside that binary's tree. Cleanup removes the whole
`build/upgrade-test` directory.
This only touches the CI script. A local run of
`release-upgrade-test.sh` for release/v6.7 to main passed, with the
release `RUNPATH` under `build/upgrade-test/release` and main's under
`build/upgrade-test/main`.
0 commit comments