Skip to content
Go Analyse

create a separate workflow for go analyze #2

Sign in to view logs

create a separate workflow for go analyze

create a separate workflow for go analyze #2

Triggered via pull request April 24, 2024 21:10
@eljohnson92eljohnson92
synchronize #286
separate-go-analyse
Status Failure
Total duration 3m 24s
Artifacts –

go-analyse.yml

on: pull_request
changes
4s
changes
go-analyse
3m 1s
go-analyse
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
go-analyse
Failed to run: Error: failed to get action config: connect ECONNREFUSED 54.185.253.63:443, Error: failed to get action config: connect ECONNREFUSED 54.185.253.63:443 at getConfig (/home/runner/work/_actions/golangci/golangci-lint-action/v4/dist/run/index.js:91268:15) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async findLintVersion (/home/runner/work/_actions/golangci/golangci-lint-action/v4/dist/run/index.js:91289:20) at async prepareLint (/home/runner/work/_actions/golangci/golangci-lint-action/v4/dist/run/index.js:90837:27) at async prepareEnv (/home/runner/work/_actions/golangci/golangci-lint-action/v4/dist/run/index.js:90898:22)
go-analyse
failed to get action config: connect ECONNREFUSED 54.185.253.63:443
changes
Unexpected input(s) 'predicate-quantifier', valid inputs are ['token', 'working-directory', 'ref', 'base', 'filters', 'list-files', 'initial-fetch-depth']