getTaskPath() in signals_test.go returns bare filename instead of full path #2970

Bug Description

In signals_test.go, the getTaskPath() helper function has a subtle but impactful bug: it calls os.Stat("./bin/task") and then returns info.Name(). The FileInfo.Name() method returns only the base filename (i.e. "task"), not the path that was passed to os.Stat.

Affected Code

// signals_test.go, line 190-193
func getTaskPath() (string, error) {
    if info, err := os.Stat("./bin/task"); err == nil {
        return info.Name(), nil  // ❌ returns "task", not "./bin/task"
    }
    ...
}

Root Cause

From the Go standard library documentation for fs.FileInfo.Name():

Name returns the name of the file corresponding to this entry, for a regular file, this is the base name of the file.

So info.Name() returns "task" — not "./bin/task".

Impact

When the signal tests call getTaskPath() and ./bin/task exists, the function returns "task" (bare filename). This path is then passed to exec.Command(). On systems where task is also installed globally (in $PATH), the tests silently run against the system-installed binary instead of the locally-built one from ./bin/task. This can mask failures in locally-built binaries and cause signal tests to pass even when the local build is broken.

Expected Behavior

getTaskPath() should return "./bin/task" when the binary exists at that path.

Fix

func getTaskPath() (string, error) {
    const localTaskBin = "./bin/task"
    if _, err := os.Stat(localTaskBin); err == nil {
        return localTaskBin, nil  // ✅ returns "./bin/task"
    }
    ...
}

Steps to Reproduce

1. Build task locally: go build -o ./bin/task ./cmd/task
2. Run signal tests: go test -tags signals -run TestSignalSentToProcessGroup ./...
3. Observe that getTaskPath() returns "task" instead of "./bin/task"

Environment

• Go version: go1.24
• OS: Linux