libakerror/.gitea/workflows/ci.yaml

name: libakerror CI Build
run-name: ${{ gitea.actor }} libakerror test
on: [push]

jobs:
  cmake_build:
    runs-on: ubuntu-latest
    steps:
      - run: echo "Triggered by ${{ gitea.event_name }} from ${{ gitea.repository }}@${{ gitea.ref }}. Building on ${{ runner.os }}."
      - name: Check out repository code
        uses: actions/checkout@v4
      - name: dependencies
        run: |
          sudo apt-get update -y
          sudo apt-get install -y cmake gcc moreutils
      - name: build and install
        run: |
          mkdir installdir
          cmake -S . -B build -DCMAKE_INSTALL_PREFIX=installdir
          cmake --build build
          cmake --install build
      # --output-junit resolves relative to the test dir, so give an absolute
      # path to land the report in the workspace root for the reporter below.
      - name: test (JUnit)
        run: ctest --test-dir build --output-on-failure --output-junit "$(pwd)/ctest-junit.xml"
      # annotate_only: true skips creating a check run via the Checks API, which
      # Gitea does not support and 404s on (mikepenz/action-junit-report#23).
      # Results surface via the job summary instead.
      - name: publish test results
        if: always()
        uses: mikepenz/action-junit-report@v4
        with:
          report_paths: 'ctest-junit.xml'
          annotate_only: true
          detailed_summary: true
          include_passed: true
          fail_on_failure: 'true'
      - run: echo "🍏 This job's status is ${{ job.status }}."

  # Builds and tests the AKERR_USE_STDLIB=OFF configuration end to end (issue
  # #12), and separately proves that the generated header compiles under a
  # genuinely freestanding toolchain (-nostdinc -ffreestanding, no libc at
  # all) via tests/freestanding_fixture.c, which is never linked or run.
  cmake_build_freestanding:
    runs-on: ubuntu-latest
    steps:
      - name: Check out repository code
        uses: actions/checkout@v4
      - name: dependencies
        run: |
          sudo apt-get update -y
          sudo apt-get install -y cmake gcc
      - name: configure, build and test (AKERR_USE_STDLIB=OFF)
        run: |
          cmake -S . -B build-off -DAKERR_USE_STDLIB=OFF -DAKERR_THREADS=none
          cmake --build build-off
          ctest --test-dir build-off --output-on-failure
      - name: freestanding consumer fixture (compile-only, no libc)
        run: |
          gcc -c -std=c11 \
              -nostdinc -ffreestanding \
              -isystem "$(gcc -print-file-name=include)" \
              -I build-off/generated/include \
              -I tests \
              tests/freestanding_fixture.c -o /tmp/freestanding_fixture.o
      - run: echo "🍏 This job's status is ${{ job.status }}."

  sanitizer:
    runs-on: ubuntu-latest
    steps:
      - name: Check out repository code
        uses: actions/checkout@v4
      - name: dependencies
        run: |
          sudo apt-get update -y
          sudo apt-get install -y cmake gcc moreutils
      - name: build with AddressSanitizer and UBSan
        run: |
          cmake -S . -B build/asan -DAKERR_SANITIZE=address,undefined
          cmake --build build/asan
      - name: test with AddressSanitizer and UBSan
        run: ctest --test-dir build/asan --output-on-failure
      - run: echo "🍏 This job's status is ${{ job.status }}."

  coverage:
    runs-on: ubuntu-latest
    steps:
      - name: Check out repository code
        uses: actions/checkout@v4
      - name: dependencies
        run: |
          sudo apt-get update -y
          sudo apt-get install -y cmake gcc moreutils python3
      # Run the suite against a gcov-instrumented build and gate on coverage of
      # the library sources. Thresholds keep headroom below the current numbers
      # (src/error.c: ~94% line, ~60% branch) and apply per file as well as to
      # the total, so the generated status-name table cannot mask a regression.
      - name: coverage
        run: |
          python3 scripts/coverage.py --junit coverage-junit.xml --threshold 90 --branch-threshold 50
      # Publish even when the threshold gate fails, so gaps are visible.
      # Display-only (fail_on_failure: false); the --threshold above is the gate.
      # annotate_only avoids the Checks API 404 on Gitea (see note above).
      - name: publish coverage results
        if: always()
        uses: mikepenz/action-junit-report@v4
        with:
          report_paths: 'coverage-junit.xml'
          annotate_only: true
          detailed_summary: true
          include_passed: true
          fail_on_failure: 'false'
      - run: echo "🍏 This job's status is ${{ job.status }}."

  mutation_test:
    runs-on: ubuntu-latest
    steps:
      - name: Check out repository code
        uses: actions/checkout@v4
      - name: dependencies
        run: |
          sudo apt-get update -y
          sudo apt-get install -y cmake gcc moreutils python3
      # Verify the tests actually catch bugs: break the library many ways and
      # confirm the suite fails. Gated on src/error.c (fast, deterministic).
      # The threshold keeps headroom below the current score for equivalent
      # mutants; see tests/MUTATION.md. Run the full default target locally for
      # deeper (slower) coverage including the macro header.
      - name: mutation testing
        run: |
          python3 scripts/mutation_test.py --target src/error.c --junit mutation-junit.xml --threshold 65
      # Publish even when the threshold gate fails, so survivors are visible.
      # Display-only (fail_on_failure: false); the --threshold above is the gate.
      # annotate_only avoids the Checks API 404 on Gitea (see note above).
      - name: publish mutation results
        if: always()
        uses: mikepenz/action-junit-report@v4
        with:
          report_paths: 'mutation-junit.xml'
          annotate_only: true
          detailed_summary: true
          include_passed: true
          fail_on_failure: 'false'
      - run: echo "🍏 This job's status is ${{ job.status }}."