mirror of
https://github.com/hanzoai/expr.git
synced 2026-09-24 16:58:58 +00:00
zeekayandHanzo Dev
7fc0117f4f
github.com has no runner for hanzo-build-linux-amd64, so a caller under .github/workflows is a gate that can never be scheduled. This is the ~7-line caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1. Co-authored-by: Hanzo Dev <[email protected]>
19 lines
945 B
YAML
19 lines
945 B
YAML
# Canonical CI/CD config for hanzoai/expr — read by the hanzoai/ci reusable
|
|
# workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
|
|
#
|
|
# LIBRARY: the expr expression language, a pure Go module. No image, no deploy.
|
|
#
|
|
# `go test ./...`, deliberately NOT `go build ./...`. Two reasons, and the second
|
|
# is the interesting one:
|
|
# - This is a compiler + VM. Its correctness lives entirely in the suite
|
|
# (parser, checker, optimizer, vm); a compile-only gate proves nothing about
|
|
# whether an expression still evaluates to the right answer.
|
|
# - `go build ./...` FAILS here on a healthy tree: test/examples is
|
|
# `package main` whose only content is a _test.go, so the linker reports
|
|
# "function main is undeclared in the main package". `go test` builds that
|
|
# package the way it is meant to be built. A gate that is red on a green
|
|
# repo teaches everyone to ignore it.
|
|
test:
|
|
- name: test
|
|
run: go test ./...
|