clockworklabs / clockworklabs/SpacetimeDB

CI flake: segfault in wasm-opt?

Open
#5,369 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
25.2k
Forks
1.1k
Avg merge
2d 7h
Merged PRs (30d)
46

Description

Created by CI Gremlin from a manually supplied failed GitHub Actions job.

Tests:

  • cpp_procedures::http_err
  • cascading SDK failures after the shared module cache/lock was poisoned (208 failed total)

Error:
thread 'cpp_procedures::http_err' (126962) panicked at crates/testing/src/modules.rs:190:10:
Module compilation failed: Failed to build C++ project

Caused by:
0: failed running cmake
1: command ["cmake", "--build", "build", "--config", "Debug", "--parallel"] exited with code 2

Failed job runs:

Context:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the failed GitHub Actions job and the panic at crates/testing/src/modules.rs:190, then inspect the cmake build output for cpp_procedures::http_err. Check whether the shared module cache or lock is poisoned and whether the reported wasm-opt failure is present in the job logs. Done means the test no longer flakes and cascading SDK failures do not occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp, rust, wasm
Domain
build-system, ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.