Skip to content

chore(deps): update rust crate tempfile to v3.26.0 #223

chore(deps): update rust crate tempfile to v3.26.0

chore(deps): update rust crate tempfile to v3.26.0 #223

Workflow file for this run

---
name: Miri
"on":
push:
branches:
- '**'
pull_request:
branches:
- '**'
workflow_dispatch:
permissions:
contents: read
jobs:
miri-portable:
name: Miri Portable Code
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v6
- name: Setup Rust nightly with Miri
uses: actions-rust-lang/setup-rust-toolchain@v1
with:
toolchain: nightly
components: miri
cache: true
- name: Run Miri on portable code (error module)
run: |
cargo miri test --lib error -- --test-threads=1
env:
MIRIFLAGS: -Zmiri-disable-isolation -Zmiri-symbolic-alignment-check
# --test-threads=1 is used for Miri to ensure deterministic execution and better UB detection
# This is a Miri-specific requirement, not related to test isolation
# No continue-on-error: These tests should pass and will fail CI if UB is detected
#
# Note: The config module is NOT tested here because it triggers rayon initialization
# (via slint → image → rayon dependency chain), which uses crossbeam-epoch 0.9.18.
# crossbeam-epoch 0.9.18 has known Stacked Borrows violations that cause Miri to fail,
# even without strict provenance checking. These are fixed in crossbeam-epoch 0.10.x
# but rayon 1.11 hasn't updated yet. The config module is still tested in the
# "best effort" full coverage job below (which allows failures for FFI/dependency issues).
miri-full:
name: Miri Full Coverage (Best Effort)
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v6
- name: Setup Rust nightly with Miri
uses: actions-rust-lang/setup-rust-toolchain@v1
with:
toolchain: nightly
components: miri
cache: true
- name: Run Miri on all library tests
run: cargo miri test --lib -- --test-threads=1
env:
MIRIFLAGS: -Zmiri-disable-isolation
continue-on-error: true
# --test-threads=1 is used for Miri to ensure deterministic execution and better UB detection
# This is a Miri-specific requirement, not related to test isolation
# Continue-on-error: Windows FFI calls will fail on Linux Miri
# but this still validates pure Rust code in other modules
- name: Run Miri with strict checking on all tests
run: cargo miri test --lib -- --test-threads=1
env:
MIRIFLAGS: -Zmiri-disable-isolation -Zmiri-strict-provenance -Zmiri-symbolic-alignment-check
continue-on-error: true
# --test-threads=1 is used for Miri to ensure deterministic execution and better UB detection
# Strict mode catches additional provenance and alignment issues