Dario Gabriel Lipicar f4245bd593
ci: add exploratory doctest crash-probe workflow
The execution-zone doc-test is intermittently red (~1 in 3 on the GitHub
runners): the module loads (daemon reports "loaded"), then on the very
next IPC call it reports "not_loaded" and every method fails — even
name()/version(), which touch no FFI. The module subprocess dies right
after load. It does not reproduce off the hosted runners (verified:
~700 module loads + 24 parallel real-doc-test samples on x86-64 Linux
under heavy contention, all green), so the signature has to be captured
in CI.

This adds a self-contained, opt-in probe workflow (manual dispatch or the
`crash-probe` PR label) that loops the real doc-test until the first
failure, then uploads the daemon logs.txt — kept via --keep-workdir and
captured AFTER the failure (the spec only cats it before load), with
RUST_BACKTRACE=full — plus kernel dmesg and a coredump backtrace
(gdb on Linux / .ips crash report on macOS) as the lez-crash-<os>
artifact. Diagnostics only; does not touch the production doctests.yml.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-25 10:33:02 -03:00
2026-02-03 18:12:53 +01:00
2026-06-15 11:13:40 -04:00
2026-06-23 16:29:09 +03:00
2026-06-23 15:18:02 +03:00
2026-06-15 10:14:10 -04:00
2026-06-10 15:16:20 -04:00
2026-06-24 17:39:34 +03:00
2026-06-24 17:39:34 +03:00
2026-02-11 13:46:27 +00:00

Logos Blockchain Module

Setup

IDE

If you're using an IDE with CMake integration make sure it points to the same cmake directory as the justfile, which defaults to build.

This will reduce friction when working on the project.

Nix

  • Use nix flake update to bring all nix context and packages
  • Use nix build to build the package
  • Use nix run to launch the module-viewer and check your module loads properly
  • Use nix develop to setup your IDE
Description
No description provided
Readme
Languages
C++ 84.4%
C 10%
Shell 2.8%
CMake 1.7%
Nix 0.6%
Other 0.5%