报告中心
查看测试结果、日志链接和 AI 分析结论
结果 10
成功 1 · 失败 8 · 已分析 8
结果
10
成功
1
失败
8
已分析
8
测试结果
没有测试结果记录，通常表示执行器还未回传 report。
AI 分析
没有 AI 分析记录。一般是任务还没失败，或者分析任务还没跑完。
成功云鹿商场·API smoke tests
环境 dev · 创建于 2026/5/10 09:18:16
开始时间 2026/5/10 09:18:18 · 结束时间 2026/5/10 09:18:20
测试结果
exit_code=0
AI 分析
没有 AI 分析记录。一般是任务还没失败，或者分析任务还没跑完。
失败云鹿商场·API smoke tests
环境 dev · 创建于 2026/5/10 02:35:11
开始时间 2026/5/10 02:37:00 · 结束时间 2026/5/10 02:37:13
测试结果
exit_code=-1
AI 分析
失败原因：Test exited with code -1, indicating a process crash or forceful termination (e.g., segfault, unhandled exception, or timeout). No test output log was captured.
影响范围：The entire test suite execution is blocked, preventing validation of the affected feature or code path in the 'dev' environment.
修复建议：Investigate potential causes: unhandled exception, segmentation fault, resource exhaustion, or environment misconfiguration. Enable core dumps, increase logging, and run the test in isolation with additional diagnostics. Check for recent code changes or updates to dependencies.
30%
失败云鹿商场·API smoke tests
环境 dev · 创建于 2026/5/9 00:08:09
开始时间 2026/5/10 02:36:32 · 结束时间 2026/5/10 02:36:44
测试结果
exit_code=-1
AI 分析
失败原因：Test process terminated abnormally (exit code -1) with no output log, indicating a crash or execution infrastructure issue.
影响范围：Entire test suite execution halted, blocking validation of all features under this suite.
修复建议：Check for environment setup issues such as missing dependencies, out-of-memory errors, or network failures. Restart the test environment and re-run the suite.
30%
失败云鹿商场·API smoke tests
环境 staging · 创建于 2026/5/1 02:35:31
开始时间 2026/5/1 02:39:45 · 结束时间 2026/5/1 02:39:45
测试结果
exit_code=1
AI 分析
失败原因：The pytest module is not installed in the Python environment, causing the test runner to fail.
影响范围：All tests in the suite are blocked from execution, preventing any test validation in the staging environment.
修复建议：Install the pytest module using pip (e.g., pip install pytest) or ensure the test environment's dependencies are properly configured.
0%
失败云鹿商场·API smoke tests
环境 dev · 创建于 2026/5/1 02:30:56
开始时间 2026/5/1 02:39:40 · 结束时间 2026/5/1 02:39:40
测试结果
exit_code=1
AI 分析
失败原因：pytest module is missing in the Python environment
影响范围：Unable to execute any tests in the test suite
修复建议：Install pytest using 'pip install pytest' or ensure the Python environment for the dev environment has pytest available
0%
失败云鹿商场·API full regression
环境 dev · 创建于 2026/5/1 02:18:30
开始时间 2026/5/1 02:39:34 · 结束时间 2026/5/1 02:39:35
测试结果
exit_code=1
AI 分析
失败原因：pytest module is not installed in the Python 3.14 environment
影响范围：All test execution is blocked; no tests can be discovered or run in the dev environment
修复建议：Install pytest in the environment, e.g., run 'pip install pytest' or ensure the dev environment's requirements/dependencies include pytest for Python 3.14
0%
失败云鹿商场·API full regression
环境 dev · 创建于 2026/5/1 01:50:52
开始时间 2026/5/1 02:39:29 · 结束时间 2026/5/1 02:39:29
测试结果
exit_code=1
AI 分析
失败原因：pytest module is not installed in the Python environment
影响范围：Unable to run any pytest-based tests in the 'dev' environment
修复建议：Install pytest using pip install pytest or add it to the project dependencies (e.g., requirements.txt)
0%
失败云鹿商场·API smoke tests
环境 dev · 创建于 2026/4/30 16:55:55
开始时间 2026/4/30 17:17:16 · 结束时间 2026/4/30 17:17:16
测试结果
exit_code=1
AI 分析
失败原因：Missing pytest module in Python environment
影响范围：Unable to run the test suite; no tests executed
修复建议：Install pytest in the Python environment using pip install pytest
0%
失败云鹿商场·API smoke tests
环境 dev · 创建于 2026/4/30 16:55:54
开始时间 2026/4/30 17:03:23 · 结束时间 2026/4/30 17:04:08
测试结果
exit_code=-1
AI 分析
失败原因：Test execution failed with exit code -1, indicating a crash or abnormal termination (e.g., segmentation fault, timeout, or resource exhaustion). No test output log is available.
影响范围：The entire test suite is blocked, preventing validation of functionality under test. This could halt CI/CD pipelines and delay releases.
修复建议：Investigate the test environment and test runner configuration for resource limits, memory issues, or missing dependencies. Check if the suite requires additional setup or if a specific test case causes a crash. Consider enabling detailed logging or running the suite in isolation to identify the failing test.
10%