Docker build failures don't propagate

Open
#1 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, github-actions

Research direction

Start with the linked tinycc Docker build run and inspect how its failure is reported by the workflow. Trace the relevant workflow entry point and determine what must change so that a failed Docker build causes the overall run to fail; done means the failure is no longer reported as successful.

Written by the indexing model from the issue text.

Description

Dominant language
Python
Stars
26
Forks
44
Avg merge
15h 40m
Merged PRs (30d)
6

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from compiler-explorer/compiler-workflows

All issues in compiler-explorer/compiler-workflows

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.