[Bug]: e2e script flag parsing is broken

Abierto Apto para principiantes
  • ¿Algo no está bien?
#2,217 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@ericcurtin ya está trabajando en esto.

Desde el 5/10/2026.

  • #2226 de @ericcurtin — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go, shell
Área
testing

Línea de trabajo

Empieza leyendo hack/run-e2e.sh y reproduciendo las dos formas del comando indicadas en el issue; el fallo reportado se produce al invocar la prueba e2e de capabilities. Compara cómo gestiona el script los flags y la ruta de la suite en cada orden, y luego confirma que ambos comandos se comportan igual y que --no-color llega a la prueba.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area/dev-infra area/tests kind/bug
What happened?
./hack/run-e2e.sh ./internal/e2e/suites/networking -v -args --no-color

and

./hack/run-e2e.sh -v ./internal/e2e/suites/networking -args --no-color

Do not do the same thing

Expected Behavior

I would expect

./hack/run-e2e.sh ./internal/e2e/suites/networking -v -args --no-color

and

./hack/run-e2e.sh -v ./internal/e2e/suites/networking -args --no-color

To do the same thing.

Steps to Reproduce

./hack/run-e2e.sh -v ./internal/e2e/suites/networking -args --no-color

Sandbox Runtime

gVisor (runsc)

Agent Substrate Version / Commit SHA

3dfddb1fb2a26e2a4db2c56f427d0f05f1fd0991

Kubernetes Version & Environment

kind version 0.31.0

Host OS & Architecture

Linux amd64

Relevant Logs and Diagnostic Output
Usage of /tmp/go-build3858815266/b001/capabilities.test:
      --e2e                                         run e2e tests
      --kube-config string                          Location of the kubeconfig
      --kube-context string                         Kubernetes context to use
      --no-color                                    disable colors in output
      --storage-class string                        StorageClass to use for external volume tests (default "csi-nfs-sc")
      --test.artifacts                              store test artifacts in test.,outputdir
      --test.bench regexp                           run only benchmarks matching regexp
      --test.benchmem                               print memory allocations for benchmarks
      --test.benchtime d                            run each benchmark for duration d or N times if `d` is of the form Nx (default 1s)
      --test.blockprofile file                      write a goroutine blocking profile to file
      --test.blockprofilerate rate                  set blocking profile rate (see runtime.SetBlockProfileRate) (default 1)
      --test.count n                                run tests and benchmarks n times (default 1)
      --test.coverprofile file                      write a coverage profile to file
      --test.cpu list                               comma-separated list of cpu counts to run each test with
      --test.cpuprofile file                        write a cpu profile to file
      --test.failfast                               do not start new tests after the first test failure
      --test.fullpath                               show full file names in error messages
      --test.fuzz regexp                            run the fuzz test matching regexp
      --test.fuzzcachedir string                    directory where interesting fuzzing inputs are stored (for use only by cmd/go)
      --test.fuzzminimizetime durationOrCountFlag   time to spend minimizing a value after finding a failing input (default 1m0s)
      --test.fuzztime durationOrCountFlag           time to spend fuzzing; default is to run indefinitely (default 0s)
      --test.fuzzworker                             coordinate with the parent process to fuzz random values (for use only by cmd/go)
      --test.gocoverdir string                      write coverage intermediate files to this directory
      --test.list regexp                            list tests, examples, and benchmarks matching regexp then exit
      --test.memprofile file                        write an allocation profile to file
      --test.memprofilerate rate                    set memory allocation profiling rate (see runtime.MemProfileRate)
      --test.mutexprofile string                    write a mutex contention profile to the named file after execution
      --test.mutexprofilefraction int               if >= 0, calls runtime.SetMutexProfileFraction() (default 1)
      --test.outputdir dir                          write profiles to dir
      --test.paniconexit0                           panic on call to os.Exit(0)
      --test.parallel n                             run at most n tests in parallel (default 12)
      --test.run regexp                             run only tests and examples matching regexp
      --test.short                                  run smaller test suite to save time
      --test.shuffle string                         randomize the execution order of tests and benchmarks (default "off")
      --test.skip regexp                            do not list or run tests matching regexp
      --test.testlogfile file                       write test action log to file (for use only by cmd/go)
      --test.timeout d                              panic test binary after duration d (default 0, timeout disabled) (default 0s)
      --test.trace file                             write an execution trace to file
      --test.v chattyFlag[=true]                    verbose: print additional output
unknown shorthand flag: 'a' in -args
FAIL	github.com/agent-substrate/substrate/internal/e2e/suites/capabilities	0.037s
Additional Context

No response

Confirmation
  • I have searched existing issues and verified that this is not a duplicate.
  • I have verified that this issue occurs on the latest commit on main.
Lenguaje dominante
Go
Estrellas
6.1k
Forks
676
Merge medio
2 d 1 h
PR fusionados (30 d)
481

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de agent-substrate/substrate

Todos los issues de agent-substrate/substrate

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.