Commit Graph

7 Commits

Author SHA1 Message Date
brent.edwards 61d00ef037 fix(forgejo): changing from "uv=0.8.0" to "uv==0.8.0"
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 39s
CI / build (pull_request) Successful in 56s
CI / lint (pull_request) Successful in 1m4s
CI / quality (pull_request) Successful in 1m6s
CI / benchmark-regression (pull_request) Failing after 1m8s
CI / typecheck (pull_request) Successful in 1m32s
CI / security (pull_request) Successful in 1m40s
CI / push-validation (pull_request) Successful in 29s
CI / integration_tests (pull_request) Successful in 3m35s
CI / e2e_tests (pull_request) Successful in 4m17s
CI / unit_tests (pull_request) Successful in 6m49s
CI / docker (pull_request) Failing after 2s
CI / coverage (pull_request) Successful in 11m36s
CI / status-check (pull_request) Failing after 3s
2026-05-04 23:09:47 +00:00
HAL9000 d1c6376484 fix(ci): restore benchmark-regression trigger to pull_request events in master.yml
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / helm (push) Waiting to run
CI / push-validation (push) Waiting to run
CI / status-check (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / benchmark-regression (push) Waiting to run
The benchmark-regression job was missing from master.yml entirely. Since master.yml
triggers on both push and pull_request events, adding the job here with the guard
  if: forgejo.event_name == 'pull_request'
ensures it runs on PRs. The job syncs prior ASV results from S3 (gracefully skips
if credentials are not configured), runs nox -s benchmark_regression, and uploads
the log as an artifact. It is intentionally NOT added to status-check's required
needs list so that benchmark regressions are informational and do not block PR merges.

ISSUES CLOSED: #10716
2026-05-02 21:57:26 +00:00
hurui200320 5580d07419 fix(ci): fix uv install syntax
CI / lint (push) Successful in 39s
CI / security (push) Successful in 1m8s
CI / typecheck (push) Successful in 1m28s
CI / quality (push) Successful in 57s
CI / helm (push) Successful in 38s
CI / build (push) Successful in 42s
CI / push-validation (push) Successful in 24s
CI / e2e_tests (push) Successful in 3m27s
CI / integration_tests (push) Successful in 4m42s
CI / unit_tests (push) Successful in 6m1s
CI / docker (push) Successful in 1m51s
CI / coverage (push) Successful in 10m43s
CI / status-check (push) Successful in 3s
CI / benchmark-publish (push) Successful in 1h37m26s
CI / push-validation (pull_request) Successful in 32s
CI / helm (pull_request) Successful in 34s
CI / lint (pull_request) Successful in 56s
CI / build (pull_request) Successful in 54s
CI / quality (pull_request) Successful in 1m20s
CI / typecheck (pull_request) Successful in 1m24s
CI / security (pull_request) Successful in 1m31s
CI / benchmark-publish (pull_request) Has been skipped
CI / integration_tests (pull_request) Successful in 3m30s
CI / e2e_tests (pull_request) Successful in 4m21s
CI / unit_tests (pull_request) Successful in 4m45s
CI / docker (pull_request) Successful in 1m26s
CI / coverage (pull_request) Successful in 10m53s
CI / status-check (pull_request) Successful in 3s
2026-05-01 03:04:09 +00:00
HAL9000 087314843a ci: remove benchmark-regression job from PR workflow (already in scheduled)
CI / push-validation (pull_request) Successful in 28s
CI / helm (pull_request) Successful in 32s
CI / lint (pull_request) Successful in 1m3s
CI / build (pull_request) Successful in 59s
CI / quality (pull_request) Successful in 1m26s
CI / security (pull_request) Successful in 1m38s
CI / typecheck (pull_request) Successful in 1m46s
CI / e2e_tests (pull_request) Successful in 3m51s
CI / integration_tests (pull_request) Successful in 4m0s
CI / unit_tests (pull_request) Successful in 6m7s
CI / docker (pull_request) Successful in 1m34s
CI / coverage (pull_request) Successful in 11m9s
CI / benchmark-publish (push) Waiting to run
CI / status-check (pull_request) Successful in 3s
CI / helm (push) Successful in 28s
CI / push-validation (push) Successful in 29s
CI / lint (push) Successful in 1m0s
CI / quality (push) Successful in 1m13s
CI / typecheck (push) Successful in 1m23s
CI / build (push) Successful in 1m3s
CI / security (push) Successful in 1m31s
CI / integration_tests (push) Successful in 4m20s
CI / e2e_tests (push) Successful in 5m11s
CI / unit_tests (push) Successful in 10m37s
CI / docker (push) Successful in 1m24s
CI / benchmark-publish (pull_request) Has been skipped
CI / coverage (push) Successful in 12m19s
CI / status-check (push) Successful in 3s
The benchmark-regression job was supposed to be moved to the dedicated benchmark-scheduled.yml workflow (commit 44fc7411, issue #9040), but was accidentally left in master.yml. This caused every PR to run a 1h+ ASV benchmark suite on the docker-benchmark runner, blocking PR feedback.

The benchmark-regression job now lives exclusively in .forgejo/workflows/benchmark-scheduled.yml and runs on a nightly schedule (2 AM UTC) and on workflow_dispatch. The benchmark-publish job (push to master) remains in master.yml as intended.
2026-04-26 12:35:39 +00:00
CoreRasurae 9c5f19854d ci(docker): Ensure CI uses CT docker proxy to workaround Docker ratelimit issues
CI / push-validation (push) Successful in 26s
CI / helm (push) Successful in 33s
CI / build (push) Successful in 1m18s
CI / lint (push) Successful in 1m24s
CI / quality (push) Successful in 1m38s
CI / benchmark-regression (push) Has been skipped
CI / typecheck (push) Successful in 2m3s
CI / security (push) Successful in 2m5s
CI / benchmark-publish (push) Has started running
CI / e2e_tests (push) Successful in 4m33s
CI / unit_tests (push) Successful in 5m24s
CI / integration_tests (push) Successful in 5m37s
CI / docker (push) Successful in 1m34s
CI / coverage (push) Successful in 11m4s
CI / status-check (push) Successful in 4s
CI / push-validation (pull_request) Successful in 24s
CI / helm (pull_request) Successful in 29s
CI / build (pull_request) Successful in 53s
CI / lint (pull_request) Successful in 57s
CI / quality (pull_request) Successful in 1m15s
CI / typecheck (pull_request) Successful in 1m29s
CI / security (pull_request) Successful in 1m29s
CI / integration_tests (pull_request) Successful in 3m24s
CI / e2e_tests (pull_request) Successful in 3m53s
CI / benchmark-publish (pull_request) Has been skipped
CI / unit_tests (pull_request) Successful in 6m5s
CI / docker (pull_request) Successful in 1m29s
CI / coverage (pull_request) Successful in 11m7s
CI / status-check (pull_request) Successful in 3s
CI / benchmark-regression (pull_request) Successful in 1h10m43s
ISSUES CLOSED: #10856
2026-04-24 21:58:51 +01:00
hurui200320 b56abc4fac fix(ci): correct invalid workflow configuration in master.yml
CI / push-validation (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 34s
CI / build (pull_request) Successful in 3m48s
CI / lint (pull_request) Successful in 3m55s
CI / quality (pull_request) Successful in 4m20s
CI / typecheck (pull_request) Successful in 4m35s
CI / security (pull_request) Successful in 4m42s
CI / e2e_tests (pull_request) Successful in 7m7s
CI / unit_tests (pull_request) Successful in 7m16s
CI / integration_tests (pull_request) Successful in 7m47s
CI / docker (pull_request) Successful in 1m37s
CI / coverage (pull_request) Successful in 15m4s
CI / status-check (pull_request) Successful in 3s
CI / benchmark-regression (push) Waiting to run
CI / benchmark-publish (push) Waiting to run
CI / push-validation (push) Successful in 23s
CI / helm (push) Successful in 30s
CI / build (push) Successful in 3m51s
CI / lint (push) Successful in 3m57s
CI / quality (push) Successful in 4m21s
CI / security (push) Successful in 4m31s
CI / typecheck (push) Successful in 4m41s
CI / e2e_tests (push) Successful in 7m15s
CI / integration_tests (push) Successful in 7m52s
CI / unit_tests (push) Successful in 9m0s
CI / docker (push) Successful in 1m36s
CI / coverage (push) Successful in 14m58s
CI / status-check (push) Successful in 3s
CI / benchmark-regression (pull_request) Has been cancelled
CI / benchmark-publish (pull_request) Has been cancelled
Five issues were identified and fixed in .forgejo/workflows/master.yml:

1. Added 'pull_request' trigger to the 'on:' block so the
   benchmark-regression job (which conditions on pull_request events)
   can actually execute. Previously only 'push' was listed, making
   the job permanently unreachable.

2. Removed the 'needs: [lint, typecheck, security, quality]' dependency
   from benchmark-regression. Those jobs are defined in ci.yml, not in
   master.yml, so referencing them here made the workflow structurally
   invalid and would be rejected by Forgejo Actions at parse time.

3. Fixed malformed YAML in benchmark-publish: the ASV_S3_BUCKET
   expression had a line break inside '${{ ... }}', which is invalid
   YAML and caused a parse error.

4. Fixed 'rentention-days' typo to 'retention-days' in both the
   benchmark-regression and benchmark-publish upload-artifact steps.
   The misspelling caused the retention policy to be silently ignored.

5. Fixed step name typo 'Run asv ia nox' -> 'Run asv via nox' in the
   benchmark-publish job.

ISSUES CLOSED: #10804
2026-04-21 18:17:38 +08:00
clever-agent 19664f8162 Build: Added back the benchmark tests but made them so they only run after pull requests into master
CI / push-validation (push) Successful in 17s
CI / build (push) Successful in 18s
CI / helm (push) Successful in 25s
CI / quality (push) Successful in 42s
CI / typecheck (push) Successful in 49s
CI / e2e_tests (push) Successful in 2m39s
CI / lint (push) Successful in 3m25s
CI / security (push) Successful in 4m4s
CI / integration_tests (push) Successful in 9m45s
CI / unit_tests (push) Successful in 10m32s
CI / docker (push) Successful in 21s
CI / coverage (push) Has been cancelled
CI / benchmark-publish (push) Has been cancelled
CI / status-check (push) Has been cancelled
CI / benchmark-regression (push) Has been cancelled
2026-04-15 13:09:42 -04:00