golang/go

x/tools/go/packages: TestConfigDir failures

Open

#59,985 opened on May 4, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationTestingToolshelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

#!watchflakes
post <- pkg == "golang.org/x/tools/go/packages" && test == "TestConfigDir"

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestConfigDir (0.00s)
    --- FAIL: TestConfigDir/Modules (134.14s)
        packages_test.go:481: dir "/opt/golang/tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/TestConfigDir_Modules2691312952/fake", pattern "./b": got , want "b"
        packages_test.go:490: dir "/opt/golang/tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/TestConfigDir_Modules2691312952/fake", pattern "./b": error true, want false

— watchflakes

Contributor guide

Research direction
Examine the test failure in TestConfigDir for Modules subtest. The test expects a package name 'b' but got empty. Trace the logic in packages.go that loads packages for the directory.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70