Improve script failure messages with error-code guidance and CI coverage

[Copilot]

Script failures were surfacing raw errors without using the available return/error codes. This change turns those codes into actionable diagnostics for common failure modes such as network/download issues, disk exhaustion, and native segfaults, and ensures the new guidance test runs in GitHub Actions.

• Error-code guidance

  • Detects meaningful error codes from script return values and error text.
  • Maps common failure classes to short, actionable suggestions:
    • disk space / No space left on device
    • network / download / timeout / TLS / DNS failures
    • segmentation faults / signal-based native crashes
    • command-not-found / not-executable / killed / interrupted

• Script execution path

  • Enriches ScriptExecutionError with detected error_code and structured guidance.
  • Hooks the guidance into the existing script failure path in script_action.py at the point where script return codes are already available.

• CLI reporting

  • Extends top-level error reporting to print:
    • detected error code
    • likely cause
    • targeted suggestions
  • Keeps the existing rerun command and issue-reporting context intact.

• Focused coverage

  • Adds a small test covering guidance detection and emitted error-reporting output.
  • Wires .github/scripts/test_error_guidance.py into .github/workflows/test-mlc-core-actions.yaml so it runs in CI as part of the existing core actions workflow.
  • Ignores generated .mlc-log.txt to avoid accidental artifact commits.

{
    "return": 1,
    "error": "Command execution failed with error code 28. No space left on device."
}

Now reports guidance along the lines of:

• detected error code: 28
• likely cause: disk space exhaustion
• suggestions: free space in work/cache directories and retry

✅ PR Checklist

• Target branch is dev

📌 Note: PRs must be raised against dev. Do not commit directly to main.

✅ Testing & CI

• Have tested the changes in my local environment, else have properly conveyed in the PR description
• The change includes a GitHub Action to test the script(if it is possible to be added).
• No existing GitHub Actions are failing because of this change.

📚 Documentation

• README or help docs are updated for new features or changes.
• CLI help messages are meaningful and complete.

📁 File Hygiene & Output Handling

• No unintended files (e.g., logs, cache, temp files, pycache, output folders) are committed.

🛡️ Safety & Security

• No secrets or credentials are committed.
• Paths, shell commands, and environment handling are safe and portable.

🙌 Contribution Hygiene

• PR title and description are concise and clearly state the purpose of the change.
• Related issues (if any) are properly referenced using Fixes # or Closes #.
• All reviewer feedback has been addressed.

[github-actions]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[github-actions]

🤖 AI PR Review Summary\n\nAdds error code detection and actionable guidance for script execution failures. Introduces parsing of error messages to extract error codes and provide user-friendly suggestions for common errors like disk space, segmentation faults, and network issues. Integrates this guidance into the error reporting mechanism and adds unit tests for validation. Risks include potential mismatches in error code extraction patterns and incomplete coverage of error scenarios, but overall design improves user experience by providing clearer error diagnostics.

[github-actions]

🤖 AI PR Review Summary\n\nAdds comprehensive error code detection and actionable guidance for script execution failures. Introduces new utility functions in error_codes.py to parse error codes from messages and provide user-friendly suggestions. Enhances ScriptExecutionError to carry error guidance, integrates guidance generation in script_action.py, and improves error reporting in main.py to log detailed guidance. Adds unit tests for error guidance detection and reporting. Risks include maintaining accurate error pattern matching and ensuring guidance remains relevant and clear.

[github-actions]

🤖 AI PR Review Summary\n\nAdds comprehensive error code detection and actionable guidance for script failures, enhancing error reporting with detailed suggestions. Introduces new utility functions in error_codes.py to parse error codes from messages and return codes, and integrates these into script execution error handling and logging. Risks include potential mismatches in error code extraction patterns and the need to maintain updated error guidance as new error types emerge.

[github-actions]

🤖 AI PR Review Summary\n\nAdds comprehensive error code detection and actionable guidance for script execution failures. Introduces error code parsing from messages, enriches ScriptExecutionError with error guidance, and enhances error reporting with detailed suggestions. Includes unit tests for error guidance detection and logging. Risks include maintaining accuracy of error pattern matching and ensuring guidance remains relevant across diverse error scenarios.

[arjunsuresh]

where is .github/scripts/test_error_guidance.py used in github actions?

[github-actions]

🤖 AI PR Review Summary\n\nAdds comprehensive error code detection and actionable guidance for script execution failures. Introduces error code parsing from messages, enriches ScriptExecutionError with error guidance, and enhances error reporting with detailed suggestions. Includes unit tests for error guidance functionality. Risks include maintaining accuracy of error pattern matching and ensuring guidance remains relevant across diverse environments.

[arjunsuresh]

@copilot where's this test used in github actions?

[Copilot]

It wasn’t wired into GitHub Actions before. I’ve added it to .github/workflows/test-mlc-core-actions.yaml, so it now runs as Test 3c - error guidance handling in CI. Commit: bfd555a. No UI change.

[github-actions]

🤖 AI PR Review Summary\n\nAdds error code detection and actionable guidance for script execution failures. Introduces get_error_guidance to parse error codes from return codes and messages, providing user-friendly suggestions for common errors like disk space, segmentation faults, and network issues. Integrates this guidance into ScriptExecutionError and _report_error for improved error reporting. Adds unit tests for error guidance and updates CI workflow to run these tests. Risks include ensuring error code detection patterns cover relevant cases and that error guidance messages remain accurate and helpful.