gf180-trng's nightly fails the synthesis staleness guard on four of the last five runs, because the committed netlist came from Yosys 0.67 while the nightly pins 0.69. Because later steps don't run after a failure, the layout and floorplan report checks are skipped, so the nightly says nothing about them. Nightly is red at one guard, so the freshness steps after it are skipped.

Silent failure reported against gf180-trng (2AMLogic)

gf180-trng (2AMLogic)Simulation & verificationSilent failureMedium confidence

What engineers report

A silent failure reported against gf180-trng (2AMLogic): reports success, or uses stale data, while the result is wrong or missing.

Recorded mode: validation / failure

Analyst note

From the Grok pain-radar digests, Nov 13-14 2026 (Nov 13 10:41 AM ET through Nov 14 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-14: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to gf180-trng (2AMLogic).

Evidence

  1. 12AMLogic/gf180-trng Issue #866: pdk-nightly is red at the synthesis staleness guard, so the layout and floorplan freshness steps are skippedgithub.com

More recurring errors in gf180-trng (2AMLogic)

See all 2 gf180-trng (2AMLogic) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.