debug-test-errors
Guide for understanding expected errors and warnings in test output for this project. Covers SSH host key warnings (normal, expected, not failures), logging level meanings (ERROR vs WARN vs DEBUG), and when to be concerned vs when to ignore. Use when debugging E2E test output, seeing red or yellow warnings in tests, or investigating unexpected-looking log messages. Triggers on "test error", "test warning", "SSH warning", "E2E output", "debug test", "test failure", "known issue", "expected error", or "test output".
来源信息
- 仓库
- torrust/torrust-tracker-deployer
- 最近来源活动
- 2026年2月25日 19:30
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 5
- Forks
- 2
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- debug-test-errors
- description
- Guide for understanding expected errors and warnings in test output for this project. Covers SSH host key warnings (normal, expected, not failures), logging level meanings (ERROR vs WARN vs DEBUG), and when to be concerned vs when to ignore. Use when debugging E2E test output, seeing red or yellow warnings in tests, or investigating unexpected-looking log messages. Triggers on "test error", "test warning", "SSH warning", "E2E output", "debug test", "test failure", "known issue", "expected error", or "test output".
- metadata
- {"author":"torrust","version":"1.0"}
# Debugging Test Errors
## Expected: SSH Host Key Warnings
This warning is **normal and expected** — not a failure:
```text
WARN SSH warning detected, operation: "ssh_warning", host_ip: 127.0.0.1,
Warning: Permanently added '[127.0.0.1]:32825' (ED25519) to the list of known hosts.
```
**Why it appears**: SSH connects to new hosts with `-o StrictHostKeyChecking=no` for automation.
SSH adds the host key to `known_hosts` and informs us — this is normal security behavior.
**What it means**: SSH is connecting successfully. This is working correctly.
## Log Level Guide
| Level | Meaning | Action required? |
| ------- | ----------------------------------------------- | ---------------- |
| `ERROR` | Actual failure requiring attention | ✅ Yes |
| `WARN` | Expected warning (e.g., SSH host key additions) | ❌ Usually no |
| `DEBUG` | Detailed execution info for troubleshooting | ❌ No |
## When to Actually Be Concerned
Contact the team or file an issue for:
- **Process failures**: Overall command or test returns non-zero exit code
- **Connection errors**: "Connection refused", "Host unreachable"
- **Permission errors**: Unexpected "permission denied"
- **Service failures**: Docker containers not starting
- **Data corruption**: Invalid configs, lost state
- **Unknown patterns**: Errors not listed in known-issues
## How to Check if a Test Actually Failed
The overall exit code matters, not individual WARN messages:
```bash
# Run E2E test — check exit code
cargo run --bin e2e-infrastructure-lifecycle-tests; echo "Exit: $?"
# Look for these indicators of real failure (not SSH warnings):
# - "FAILED:", "ERROR:", "panicked at"
# - Non-zero exit code
```
## Common False Alarms
| What you see | Is it a failure? |
| -------------------------------------- | ---------------- |
| SSH host key WARN in test logs | ❌ Expected |
| WARN-level log lines | ❌ Usually no |
| "Permanently added ... to known_hosts" | ❌ Expected |
| "Grafana not ready yet, retrying..." | ❌ Expected |
| Test prints red/orange text | Check exit code |
## Reference
Known issues: [`docs/contributing/known-issues.md`](../../docs/contributing/known-issues.md)
E2E testing: [`docs/e2e-testing/`](../../docs/e2e-testing/)
在 GitHub 查看