Skip to content

Problem: no need DecreaseExecutionIdx to redo after using lock #27

Problem: no need DecreaseExecutionIdx to redo after using lock

Problem: no need DecreaseExecutionIdx to redo after using lock #27

Triggered via pull request September 12, 2024 02:08
@mmsqemmsqe
synchronize #14
mmsqe:resume_dep
Status Failure
Total duration 22s
Artifacts

go.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build: scheduler.go#L180
s.DecreaseExecutionIdx undefined (type *Scheduler has no field or method DecreaseExecutionIdx)
build
Process completed with exit code 1.
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/