# Windows platform selectors may use windows/ARCH for both ABIs or the more
# specific windows-msvc/ARCH and windows-mingw/ARCH forms.
host_skips:
  - directive: run
    case: fixedbugs/issue16016.go
    reason: the test intentionally creates enough goroutines to exhaust LLGo's one-thread-per-goroutine host limit
  - directive: run
    case: chan/goroutines.go
    reason: the test intentionally creates enough goroutines to exhaust LLGo's one-thread-per-goroutine host limit
  - directive: run
    case: chanlinear.go
    reason: the test repeatedly doubles a goroutine-per-channel workload and can exhaust LLGo's one-thread-per-goroutine host limit
  - version: go1.26
    platform: darwin/arm64
    directive: runoutput
    case: fixedbugs/bug449.go
    reason: go1.26 bug449 generated build exceeds the darwin/arm64 hosted runner resource budget
  - version: go1.26
    platform: linux/amd64
    directive: runoutput
    case: fixedbugs/bug449.go
    reason: go1.26 bug449 generated build exceeds the linux/amd64 hosted runner memory budget
timeouts:
  - platform: darwin/amd64
    directive: run
    case: recover.go
    timeout: 10m
    reason: the complete panic/recover compiler stress exceeded the 3m build budget on paired Intel macOS
  - platform: wasip1/wasm
    directive: run
    case: cmplxdivide.go
    timeout: 10m
    reason: the complete complex division table passed in 249s with time spent in LLVM WebAssembly register stackification
  - platform: darwin/amd64
    directive: run
    case: abi/uglyfib.go
    timeout: 90s
    reason: the full recursive ABI stress passed in 35-46s but exceeded 60s on a hosted Intel runner where adjacent cases also took twice as long
  - platform: js/wasm
    directive: run
    case: winbatch.go
    timeout: 6m
    reason: the full GOROOT filesystem walk took 195s on Emscripten32 locally and exceeded 240s on the paired hosted runner
  - platform: js/wasm
    directive: run
    case: fixedbugs/issue78081.go
    timeout: 6m
    reason: the 1.6 million-iteration stack and GC stress loop took 147s on a passing GoJS run and exceeded 180s on another runner
  - platform: wasip1/wasm
    directive: run
    case: fixedbugs/issue78081.go
    timeout: 6m
    reason: the full 1.6 million-iteration stack and GC stress exceeded 60s on the paired WASI runner and took 125s with the qualified Wasmer
  - platform: js/wasm
    directive: run
    case: fixedbugs/issue79186.go
    timeout: 4m
    reason: the full 51.2 million-operation RWMutex loop passed in 55.7s on GoJS but exceeded 2m on a paired Emscripten64 runner
  - platform: js/wasm
    directive: runoutput
    case: fixedbugs/issue5162.go
    timeout: 7m
    reason: building the 768 generated array-comparison functions exhausted the 5m budget while Go 1.26 and Go 1.27 shards shared a loaded GoJS runner
  - platform: darwin/arm64
    directive: run
    case: fixedbugs/issue79186.go
    timeout: 90s
    reason: the 51.2 million-operation RWMutex stress loop needs load-dependent runtime slack
  - platform: linux/amd64
    directive: run
    case: fixedbugs/issue79186.go
    timeout: 90s
    reason: the 51.2 million-operation RWMutex stress loop needs load-dependent runtime slack
  - platform: windows/amd64
    directive: run
    case: fixedbugs/issue79186.go
    timeout: 90s
    reason: the 51.2 million-operation RWMutex stress loop needs load-dependent runtime slack
  - platform: windows/arm64
    directive: run
    case: fixedbugs/issue79186.go
    timeout: 90s
    reason: the 51.2 million-operation RWMutex stress loop needs load-dependent runtime slack
  - platform: windows/386
    directive: run
    case: fixedbugs/issue79186.go
    timeout: 90s
    reason: the 51.2 million-operation RWMutex stress loop needs load-dependent runtime slack
  - version: go1.26
    platform: darwin/arm64
    directive: run
    case: fixedbugs/issue19658.go
    timeout: 2m
    reason: the test launches 19 nested go run commands and needs load-dependent runtime slack
  - version: go1.26
    platform: linux/amd64
    directive: run
    case: abi/uglyfib.go
    timeout: 1m
    reason: uglyfib runs close to the default timeout on loaded linux/amd64 runners
  - platform: windows/386
    directive: run
    case: abi/uglyfib.go
    timeout: 90s
    reason: uglyfib can exceed the default timeout on loaded Windows 386 runners
  - platform: windows/386
    directive: runoutput
    case: index0.go
    timeout: 90s
    reason: the generated index stress program can exceed the default timeout on loaded Windows 386 runners
  - version: go1.26
    platform: windows/386
    directive: run
    case: fixedbugs/issue16037_run.go
    timeout: 3m
    reason: the test builds generated source with 5000 fields and getter methods at runtime; its LLGo artifact exceeded the default one-minute run limit on loaded Windows MSVC and MinGW 386 runners
  - platform: windows/amd64
    directive: run
    case: fixedbugs/issue25897a.go
    timeout: 90s
    reason: the single-P continuous-GC loop needs load-dependent runtime slack on Windows amd64
  - platform: windows/386
    directive: run
    case: fixedbugs/issue25897a.go
    timeout: 90s
    reason: the single-P continuous-GC loop needs load-dependent runtime slack on Windows 386
  - platform: windows/arm64
    directive: run
    case: fixedbugs/issue25897a.go
    timeout: 90s
    reason: the single-P continuous-GC loop needs load-dependent runtime slack on Windows ARM64
  - platform: windows/386
    directive: run
    case: fixedbugs/issue30041.go
    timeout: 90s
    reason: the continuous-GC and reflect.MakeFunc stress loop needs load-dependent runtime slack on Windows 386
  - platform: windows/386
    directive: run
    case: fixedbugs/issue39541.go
    timeout: 90s
    reason: the one-million reflect.MakeFunc concurrent call loop needs load-dependent runtime slack on Windows 386
  - platform: windows/amd64
    directive: run
    case: fixedbugs/issue39541.go
    timeout: 2m
    reason: the one-million reflect.MakeFunc concurrent call loop exceeded the default minute on a paired Windows MSVC/amd64 runner; retain a bounded run with all output and exit checks
  - platform: darwin/amd64
    directive: runoutput
    case: rangegen.go
    timeout: 10m
    reason: both paired Go versions exceeded the default 3m generated-build timeout for the 6.4 MB compiler torture test on Intel macOS
  - platform: js/wasm
    directive: runoutput
    case: rangegen.go
    timeout: 15m
    reason: the large generated range-over-func program exceeds the default 3m build timeout on Emscripten; retain the complete test with a bounded compiler budget
  - platform: wasip1/wasm
    directive: runoutput
    case: rangegen.go
    timeout: 15m
    reason: the full generated range-over-func program exceeded the default 3m build budget on the paired WASI runner
  - platform: darwin/arm64
    directive: runoutput
    case: rangegen.go
    timeout: 20m
    reason: rangegen generates a large compiler torture test; paired Go 1.26/1.27 builds exceeded the default 3m build timeout on darwin/arm64 CI
  - platform: linux/amd64
    directive: runoutput
    case: rangegen.go
    timeout: 10m
    reason: rangegen generates a 6.4 MB compiler torture test; allow bounded build time while its 3 GiB heap target stays under the 4 GiB host guard
  - platform: windows-mingw/amd64
    directive: runoutput
    case: rangegen.go
    timeout: 10m
    reason: both Go 1.26 and 1.27 generated builds exceeded the default 3m timeout on Windows MinGW/amd64, peaking at 3.3 GiB each; keep the case enabled with bounded build time
  - platform: windows/arm64
    directive: runoutput
    case: rangegen.go
    timeout: 10m
    reason: the generated build still reached the 4 GiB guard with a 2 GiB Go heap target on Windows MSVC/ARM64; allow bounded build time with a case-local 1 GiB target while retaining the host resource guard
  - version: go1.26
    platform: linux/amd64
    directive: run
    case: nosplit.go
    timeout: 2m
    reason: nosplit run runs past the default timeout on linux/amd64
flakes:
xfails:
  - directive: run
    case: genmeth1.go
    reason: the current go/types and x/tools SSA path panics while instantiating the new generic-method test
  - platform: windows/amd64
    directive: run
    case: fixedbugs/issue58300.go
    reason: LLGo emits unexpected runtime output for the unsafe string conversion test on Windows amd64
  - platform: windows/386
    directive: run
    case: fixedbugs/bug114.go
    reason: the Go baseline cannot build this case in the Windows 386 target environment
  - platform: windows/386
    directive: run
    case: gcgort.go
    reason: LLGo fails the concurrent GC stress test on Windows 386
  - platform: windows/386
    directive: run
    case: printbig.go
    reason: the Go baseline cannot build this large-constant case in the Windows 386 target environment
  - platform: windows/386
    directive: run
    case: fixedbugs/issue23305.go
    reason: the Go baseline cannot build this case in the Windows 386 target environment
  - version: go1.27
    platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue34968.go
    reason: the Go 1.27 baseline cannot build this cgo checkptr case in the Windows MSVC 386 target environment
  - version: go1.26
    platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue34968.go
    reason: the Go 1.26 baseline cannot build runtime/cgo because Clang rejects -mthreads in the Windows MSVC 386 target environment
  - version: go1.26
    platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/issue34968.go
    reason: the Go 1.26 baseline cannot build runtime/cgo because Clang rejects -mthreads in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/issue34968.go
    reason: the Go 1.26 baseline cannot build runtime/cgo because Clang rejects -mthreads in the Windows MSVC arm64 target environment
  - version: go1.27
    platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue47227.go
    reason: the Go 1.27 baseline cannot build this cgo case in the Windows MSVC 386 target environment
  - version: go1.26
    platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue47227.go
    reason: the Go 1.26 baseline cannot build runtime/cgo because Clang rejects -mthreads in the Windows MSVC 386 target environment
  - version: go1.26
    platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/issue47227.go
    reason: the Go 1.26 baseline cannot build runtime/cgo because Clang rejects -mthreads in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/issue47227.go
    reason: the Go 1.26 baseline cannot build runtime/cgo because Clang rejects -mthreads in the Windows MSVC arm64 target environment
  - platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue40954.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC 386 target environment
  - platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/issue40954.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/issue40954.go
    reason: Go 1.26 cgo passes the unsupported -mthreads flag to Clang/MSVC; Go 1.27 no longer does (golang/go#80290)
  - platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue46903.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC 386 target environment
  - platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/issue46903.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/issue46903.go
    reason: Go 1.26 cgo passes the unsupported -mthreads flag to Clang/MSVC; Go 1.27 no longer does (golang/go#80290)
  - platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue51733.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC 386 target environment
  - platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/issue51733.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/issue51733.go
    reason: Go 1.26 cgo passes the unsupported -mthreads flag to Clang/MSVC; Go 1.27 no longer does (golang/go#80290)
  - platform: windows-msvc/386
    directive: run
    case: fixedbugs/bug514.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC 386 target environment
  - platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/bug514.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/bug514.go
    reason: Go 1.26 cgo passes the unsupported -mthreads flag to Clang/MSVC; Go 1.27 no longer does (golang/go#80290)
  - platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue42032.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC 386 target environment
  - platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/issue42032.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/issue42032.go
    reason: Go 1.26 cgo passes the unsupported -mthreads flag to Clang/MSVC; Go 1.27 no longer does (golang/go#80290)
  - platform: windows-msvc/386
    directive: run
    case: fixedbugs/issue42076.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC 386 target environment
  - platform: windows-msvc/amd64
    directive: run
    case: fixedbugs/issue42076.go
    reason: the Go baseline cannot build or run this cgo case in the Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: fixedbugs/issue42076.go
    reason: Go 1.26 cgo passes the unsupported -mthreads flag to Clang/MSVC; Go 1.27 no longer does (golang/go#80290)
  - version: go1.26
    platform: windows-msvc/386
    directive: run
    case: linkmain_run.go
    reason: the nested baseline go run exits unsuccessfully in the Go 1.26 Windows MSVC 386 target environment
  - version: go1.26
    platform: windows-msvc/amd64
    directive: run
    case: linkmain_run.go
    reason: the nested baseline go run exits unsuccessfully in the Go 1.26 Windows MSVC amd64 target environment
  - version: go1.26
    platform: windows-msvc/arm64
    directive: run
    case: linkmain_run.go
    reason: the nested baseline go run exits unsuccessfully in the Go 1.26 Windows MSVC arm64 target environment
  - directive: errorcheck
    case: fixedbugs/issue4776.go
    reason: llgo parser uses a different missing-package-clause diagnostic
  - directive: errorcheck
    case: fixedbugs/issue4405.go
    reason: llgo parser recovery emits additional malformed-statement diagnostics
  - directive: errorcheck
    case: fixedbugs/issue13266.go
    reason: llgo parser uses a different malformed-package-clause diagnostic
  - version: go1.26
    directive: errorcheck
    case: fixedbugs/issue20789.go
    reason: llgo parser does not emit the expected malformed-name diagnostic
  - directive: errorcheck
    case: fixedbugs/bug050.go
    reason: llgo parser emits an additional malformed-declaration diagnostic
  - directive: errorcheck
    case: bombad.go
    reason: llgo parser recovery emits additional byte-order-mark diagnostics

  - directive: run
    case: heapsampling.go
    reason: LLGo does not currently report the heap-profile samples required by this runtime test
  - platform: J32-GoJS
    directive: run
    case: init1.go
    reason: the conservative linear collector retains enough loop-temporary pointers to grow memory past this Go allocator threshold
  - platform: J32-Emscripten
    directive: run
    case: init1.go
    reason: the conservative linear collector retains enough loop-temporary pointers to grow memory past this Go allocator threshold
  - platform: js/wasm
    directive: errorcheck
    case: fixedbugs/issue5089.go
    reason: LLGo does not yet diagnose a method declaration on a non-local type