Repository navigation
[Bug] ListTestCase interface exec failed. #459
Description
Description:
The ListTestCase interface throws a 500 exception when a test resource yaml file other than the one created exists in the atest directory.
Repro steps:
- git pull repo
- go build -o atest main.go
- ./atest server
- access front page and new create test resource.
- then click node.
Note: If there are privacy concerns, sanitize the data prior to
caused by the presence of yaml files other than the test resource file in the atest executable directory.
Activity
chore(deps): update jenkins/jenkins docker tag to v2.425 (#459)
linuxsuren-fs commentedon Oct 9, 2026
Tried to reproduce this on the latest
masterand it looks already fixed:fileLoader.ListTestSuitenow skips any file that fails to load or parse (with a warning log, seepkg/testing/loader_file.goaround L184-L193), andParseadditionally runs JSON-schema validation, so foreign YAML files (e.g. adocker-compose.yamlsitting next to the suites) get rejected and skipped instead of failing the whole listing.Verified locally with a scratch test: given one valid suite plus a
docker-compose.yamlin the same directory,ListTestSuitereturns the single valid suite witherr = nil, and the foreign file only produces afailed to parse datalog line (name is required,Additional property services is not allowed).@yuluo-yx could you re-check with a recent build and close this issue if it no longer reproduces? @LinuxSuRen feel free to close it directly if you consider it fixed.