Job 'build' uploads an artifact with actions/upload-artifact. Job 'test' in the same workflow needs those files. What must 'test' do?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Artifacts do not auto-appear in dependent jobs. Upload in the producer, needs for ordering, download-artifact in the consumer — cache is a different sharing mechanism.
Full explanation below image
Full Explanation
Each job gets a fresh workspace on hosted runners. Files left on disk in build are not present in test unless shared via artifacts, cache, or external storage. The standard pattern is actions/upload-artifact in build, needs: build on test, then actions/download-artifact. Artifacts differ from caches: artifacts are explicit build outputs for sharing or downloading from the UI; caches accelerate package installs across runs. GitHub Packages is a package registry, not the automatic destination of upload-artifact. Forgetting download-artifact is a common pipeline bug. Artifact retention policies eventually expire old artifacts; do not treat them as permanent releases storage for production binaries.