Skip to content

ci - check for critical warnings such as timing closure

I'm working with the v1 release and I'm surprised to see 102 critical warnings (see also latest master pipeline job at https://gitlab.cern.ch/be-cem-edl/diot/fmc-carrier/-/jobs/58923931). I suggest to modify the ci scripts to abort in case of critical warnings, do you agree? I started fixing some but there's just too many (mainly bd missing signals).

Checking for critical warnings will also cover the 'timing closure' check which is not being done I believe.