Log forensics real runs, broken on purpose
Every case is the tail of a real run. Read it, say what went wrong or what to do next, and the fix is shown with the answer. Choose the stage you want to practise, or take them all mixed together.
What the tools were told 13 cases
The run stops, or goes quietly wrong, because of something you wrote before it started.
Files and configuration
The run stops before any real work, because something it was told to read is not there.
missing filewrong sitebad pathConstraints
The constraints file loads but does not say what the author thought it said.
no clockpattern matches nothingunconstrained portsBuilding the design 17 cases
A stage cannot do its work, or does it and leaves something worth noticing.
Synthesis
The netlist cannot be built from the source it was given.
undefined moduleinferred latchmappingFloorplan and placement
There is not enough room, or what is there cannot be legalized.
utilizationdensitylegalizationClock tree
The tree cannot be built from the cells it was given.
no buffersskewinsertion delayRouting
The wires have to fit, and what the router reports on the way needs reading.
congestionviolationsantennaJudging the result 9 cases
The run finished. Now the numbers and the checks decide whether it counts.
Not the design at all 2 cases
Failures of the machine the job ran on, which often say nothing about themselves.