Common validation failures and what they mean

Use the stage of the failure and the observed error to choose the next action. Keep the assignment's intended behavior authoritative; a green check against a wrong solution is still a wrong assignment.

Solution or test failure

If actual output differs from expected output, run the instructor solution on that input. Fix a solution bug, correct the test input or comparison, or revise the requirement. Expected output should reflect observed behavior of a correct solution. Timeouts can mean an infinite loop, a missing input, or an overly expensive case. A crash often points to a code bug, missing file, or dependency.

Dependency or compile failure

Configure the required library through the assignment dependency controls or upload a supported root manifest so sandbox validation and GitHub Actions use the same installation contract. Check filenames, imports, compiler output, and any platform-specific assumptions.

Deploy or post-push failure

Deploy-time Tier 2 builds and checks the workflow before publishing. If it fails, review the evidence and return to Review & Edit. If the real GitHub Actions run fails after publication, open the linked Actions log and repair before creating student repositories. Report repeated workflow-builder errors through the support messenger with the assignment URL; those may need a CodeTeach fix.

After any artifact change, review the current package, reapprove the instructions, and rerun quality validation. Read the step-by-step recovery guide.