ci: temporary smoke-test workflow to diagnose 2s CI failure
All checks were successful
CI / Linux x86_64 (Forgejo) (push) Successful in 2s

Two prior CI runs (cc72db04 and c411916) failed in 2 seconds
without producing any visible step output. The Forgejo Actions
log API does not expose run logs without a real session, so
isolate by replacing the workflow with a single echo-step.

If this run succeeds, the issue is in one of the original
workflow's steps (likely the second checkout of module-sdk).
If this run also fails in 2 seconds, the issue is structural
to the workflow header or the runner picking up text-extract.

Bumps 0.1.1 -> 0.1.2.

Signed-off-by: flemming-it <sf@flemming.it>
This commit is contained in:
flemming-it 2026-05-01 17:54:35 +02:00
parent c4119169af
commit 965c96ea6e
3 changed files with 9 additions and 78 deletions

View file

@ -8,85 +8,16 @@ on:
env:
CARGO_TERM_COLOR: always
RUSTFLAGS: "-D warnings"
RUST_TOOLCHAIN: "1.86"
jobs:
ci:
smoke:
name: Linux x86_64 (Forgejo)
runs-on: ubuntu-latest
steps:
# Manual external-URL checkout — see fai/platform CI for
# background. Lays this repo at $GITHUB_WORKSPACE.
- name: Checkout text-extract via external URL
- name: Smoke
run: |
set -eu
mkdir -p "$GITHUB_WORKSPACE"
cd "$GITHUB_WORKSPACE"
git init -q
git remote add origin \
"https://x-access-token:${GITHUB_TOKEN}@git.flemming.ws/${GITHUB_REPOSITORY}.git"
git fetch --depth=1 origin "$GITHUB_SHA"
git checkout -q FETCH_HEAD
# text-extract depends on fai-module-sdk via a sibling-path
# dependency: ../../module_sdk/crates/fai-module-sdk
# We materialize that layout by cloning module-sdk two
# levels up from $GITHUB_WORKSPACE. This is a transient
# arrangement until the SDK is published as a versioned
# git tag or registry crate.
- name: Checkout fai/module-sdk into sibling layout
run: |
set -eu
parent="$(dirname "$GITHUB_WORKSPACE")"
grandparent="$(dirname "$parent")"
sdk_dir="$grandparent/module_sdk"
mkdir -p "$sdk_dir"
cd "$sdk_dir"
git init -q
# The SDK lives in a different Forgejo org (fai/) and the
# repo-scoped GITHUB_TOKEN cannot read it. The SDK is
# public, so an anonymous clone is sufficient and avoids
# cross-org token-scope friction.
git remote add origin \
"https://git.flemming.ws/fai/module-sdk.git"
git fetch --depth=1 origin main
git checkout -q FETCH_HEAD
echo "module-sdk checked out at: $sdk_dir"
- name: Install system dependencies
run: |
apt-get update -qq
apt-get install -y --no-install-recommends \
curl \
ca-certificates \
build-essential \
pkg-config \
libssl-dev \
git
- name: Install Rust toolchain
run: |
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs \
| sh -s -- -y \
--profile minimal \
--default-toolchain "$RUST_TOOLCHAIN" \
--target wasm32-wasip2 \
--component rustfmt \
--component clippy
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
- name: Cargo fmt --check
run: cargo fmt --all -- --check
- name: Cargo clippy
run: cargo clippy --all-targets -- -D warnings
- name: Cargo build (host)
run: cargo build --all-targets
- name: Cargo test (host)
run: cargo test --all-targets
- name: Cargo build (wasm32-wasip2)
run: cargo build --release --target wasm32-wasip2
echo "runner alive"
echo "GITHUB_WORKSPACE=$GITHUB_WORKSPACE"
echo "GITHUB_REPOSITORY=$GITHUB_REPOSITORY"
echo "GITHUB_SHA=$GITHUB_SHA"
uname -a