Must every sanity warning be zero?
From PDVerse PnR Interview Handbook · pdVerse Mentor Guide
Short Answer
No; each warning must be classified as a defect or justified intent with named objects, evidence, owner, risk, and review date.
Technical Explanation
A warning is a request for engineering judgment. Some warnings describe intentional structures, but each remaining object still needs a reason, owner, and reviewable evidence.
What To Check
• Warning sign: A team suppresses a warning ID globally or accepts a stable count without checking membership. • Inspect: Keep at least two possible causes open, then use one named object and the active mode or scenario to separate them. • Correct: Fix defects, record narrow waivers, rerun from the clean checkpoint, and compare both counts and object sets.
Command Checks & Actions
• get_message_info -warning_count: summarizes messages for triage
• check_timing: finds missing or inconsistent timing setup
Run the commands in order. Each line answers a separate part of the check.Healthy, Suspicious & Hard-stop Results
• Expected: No; each warning must be classified as a defect or justified intent with named objects, evidence, owner, risk, and review date. • Investigate: A team suppresses a warning ID globally or accepts a stable count without checking membership. • Stop before floorplanning when required logic or timing coverage is missing or unexplained. Fix defects, record narrow waivers, rerun from the clean checkpoint, and compare both counts and object sets.
Common Mistake
Do not assume the check passed just because ICC2 continued: A team suppresses a warning ID globally or accepts a stable count without checking membership. Fix or narrowly justify the named objects, then rerun the same command.
What The Interviewer Is Testing
Be ready to explain why this matters before floorplanning: A team suppresses a warning ID globally or accepts a stable count without checking membership.
Follow-up Question & Model Response
Model response: “I would save the report, inspect one affected object in the correct block and scenario, and make or request this correction: Fix defects, record narrow waivers, rerun from the clean checkpoint, and compare both counts and object sets. Then I would reopen the clean checkpoint and rerun the same evidence.”
Practical Example
Symptom: A team suppresses a warning ID globally or accepts a stable count without checking membership. Corrective path: Fix defects, record narrow waivers, rerun from the clean checkpoint, and compare both counts and object sets.
Continue practising