hyperbee.migrations/.github/workflows/multi_node_tests.yml at main · Stillpoint-Software/hyperbee.migrations · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
name: Multi-Node Integration Tests (manual)

# Multi-node OpenSearch tests live behind [TestCategory("MultiNode")]. They
# spin up a 3-node OpenSearch cluster and exercise behaviors single-node
# Testcontainers fundamentally masks (GREEN-threshold, replica allocation,
# shard relocation under load, PA-2 lock-index replicas:0 invariant).
#
# Why this workflow is manual-only: GitHub-hosted runners cannot reliably
# sustain 3 OpenSearch JVMs (~512MB each) plus the .NET test process plus
# Docker overhead. The cluster fails to converge to GREEN within 180s on
# the standard runner SKU, and every downstream test assertion cascades
# from that (reindex 503, lock socket exceptions, etc.). The cron schedule
# was producing zero signal — every nightly run failed for the same
# infrastructure reason — and the noise was actively misleading.
#
# What changed (2026-05-09):
#   - Cron schedule removed. Trigger this manually (workflow_dispatch) only
#     when a developer wants to validate on GitHub-hosted infrastructure.
#   - The MultiNode test classes are also tagged [TestCategory("LocalOnly")]
#     so any future filter that excludes LocalOnly skips them automatically.
#   - The test suite is the source of truth: `TestCategory=MultiNode`
#     selects them; running locally is the supported path.

on:
  workflow_dispatch:

permissions:
  contents: read

concurrency:
  group: multi-node-${{ github.ref }}
  cancel-in-progress: true

jobs:
  multi-node:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Setup .NET
        uses: actions/setup-dotnet@v4
        with:
          dotnet-version: |
            8.0.x
            9.0.x
            10.0.x

      - name: Restore
        run: dotnet restore tests/Hyperbee.Migrations.Integration.Tests/Hyperbee.Migrations.Integration.Tests.csproj

      - name: Build (with EnableIntegrationTests)
        run: >-
          dotnet build
          tests/Hyperbee.Migrations.Integration.Tests/Hyperbee.Migrations.Integration.Tests.csproj
          -c Release
          --no-restore
          /p:EnableIntegrationTests=true

      - name: Run multi-node tests (TestCategory=MultiNode)
        # Tests use [TestCategory("MultiNode")] so this filter picks them up
        # without affecting other test classes. The MultiNode test class's
        # [ClassInitialize] spins up the 3-node cluster.
        # HYPERBEE_TESTS_SKIP_SINGLE_NODE=true bypasses the assembly-level
        # single-node container startup (Mongo, Postgres, Couchbase,
        # Aerospike, single-node OpenSearch) since the MultiNode tests
        # don't need any of them.
        env:
          HYPERBEE_TESTS_SKIP_SINGLE_NODE: "true"
        run: >-
          dotnet test
          tests/Hyperbee.Migrations.Integration.Tests/Hyperbee.Migrations.Integration.Tests.csproj
          -c Release
          -f net10.0
          --no-build
          --filter "TestCategory=MultiNode"
          --logger "trx;LogFileName=multinode.trx"
          --logger "console;verbosity=normal"
          /p:EnableIntegrationTests=true

      - name: Upload test results
        if: always()
        uses: actions/upload-artifact@v4
        with:
          name: multi-node-test-results
          path: '**/*.trx'
          if-no-files-found: warn