Skip to content
Controller Tests

Add guardrails orchestrator CRD and controller #696

Sign in to view logs

Add guardrails orchestrator CRD and controller

Add guardrails orchestrator CRD and controller #696

Triggered via pull request October 18, 2024 18:24
@christinaexyouchristinaexyou
synchronize #300
christinaexyou:dev/guardrails-orch
Status Failure
Total duration 54s
Artifacts –

controller-tests.yaml

on: pull_request
build
44s
build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build: controllers/guardrails/guardrails_controller.go#L42
missing go.sum entry for module providing package github.com/docker/docker/api/types/volume (imported by github.com/trustyai-explainability/trustyai-service-operator/controllers/guardrails); to add:
build: controllers/guardrails/guardrails_controller.go#L231
expected type, found ')'
build: controllers/guardrails/guardrails_controller.go#L235
expected '{', found 'return'
build: controllers/guardrails/guardrails_controller.go#L235
expected operand, found 'return'
build: controllers/guardrails/guardrails_controller.go#L240
missing ',' in argument list
build: controllers/guardrails/guardrails_controller.go#L240
expected operand, found '.'
build: controllers/guardrails/guardrails_controller.go#L251
missing ',' in argument list
build: controllers/guardrails/guardrails_controller.go#L251
expected operand, found ']'
build: controllers/guardrails/guardrails_controller.go#L251
missing ',' in argument list
build: controllers/guardrails/guardrails_controller.go#L251
expected operand, found newline
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/