A civic pipeline log shows ModuleNotFoundError: No module named 'meraki' during the install/import phase, with no AssertionError lines. Which failure class does the log show?
Select an answer to reveal the explanation.
Short Explanation
ModuleNotFound is the empty shelf at checkout—install never got the package. AssertionError is the failed taste test later. Read the words; don’t mix the baskets.
Full Explanation
ModuleNotFoundError: No module named 'meraki' during the install/import phase, with no AssertionError lines, is a missing-package / install failure—not a red-test assertion failure. The civic runner never imported the Meraki client successfully, so the environment is incomplete. Classification from the exception type keeps diagnosis on packaging rather than on test expectations or cluster rollouts.
Failed unit-test assertions after dependencies resolved cleanly would produce AssertionError or FAILED test names after imports succeed; those markers are absent. A Kubernetes Deployment rollout timeout with healthy install and tests presupposes both earlier stages passed; this log never leaves import. Incompatible libX pins where both packages installed successfully first is the wrong class when a named module is simply not present—here the package was never obtained, not merely conflicting after install.
Exam caveat: ModuleNotFound during install/import is treated as dependency obtainment failure even when some earlier pip steps looked partially green—import is part of proving the install. Operational check: ensure meraki (or the declared client) is pinned in requirements, clear stale caches if needed, re-run install, and confirm python -c "import meraki" succeeds on the runner before enabling the test stage.