chore: update test tooling #75
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: t.behrendt/realDynDNS#75
Reference in New Issue
Block a user
Delete Branch "chore-update-test-tooling"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The PR introduces a YAML syntax error in the workflows by using hyphens under runs-on, which is invalid. The changes align with the title for tooling updates but require fixing the CI/CD configuration syntax.
Fix the runs-on syntax in workflows/ci.yaml and workflows/cd.yaml to use a valid list format (e.g., runs-on: [ubuntu-latest, linux_amd64])
Verify that the new test targets (test-unit, test-race) are correctly integrated into the existing test流程
Confirm that the added tool dependencies in go.mod/go.sum are necessary and properly versioned
The
runs-onfield in GitHub Actions workflows should be a string, not a list. The current syntax will cause the workflow to fail.The
go tool gcov2lcovcommand in the Makefile is incorrect - the tool should be referenced by its full path or ensure it's available in the PATH.The
tooldirective in go.mod is non-standard and may not function as intended. Consider usinggo mod tidyor standard tooling practices instead.The PR description is empty - adding a brief explanation of the changes would improve clarity.
The PR introduces several issues that need addressing before merging.
Fix the runs-on syntax in workflows/ci.yaml and workflows/cd.yaml to use a valid list format (e.g., runs-on: [ubuntu-latest, linux_amd64])
Verify that the new test targets (test-unit, test-race) are correctly integrated into the existing test流程
Confirm that the added tool dependencies in go.mod/go.sum are necessary and properly versioned
The
runs-onfield in GitHub Actions workflows should be a string, not a list. The current syntax will cause the workflow to fail.The
go tool gcov2lcovcommand in the Makefile is incorrect - the tool should be referenced by its full path or ensure it's available in the PATH.The
tooldirective in go.mod is non-standard and may not function as intended. Consider usinggo mod tidyor standard tooling practices instead.The PR description is empty - adding a brief explanation of the changes would improve clarity.