Browse Source

Fix drc/erc back to using info severity.

These aren't some sort of critical error, error severity gets sent to stderr in cli.
pcb_db
Marek Roszko 9 months ago
parent
commit
6a92e5f02d
  1. 2
      eeschema/eeschema_jobs_handler.cpp
  2. 6
      pcbnew/pcbnew_jobs_handler.cpp

2
eeschema/eeschema_jobs_handler.cpp

@ -1149,7 +1149,7 @@ int EESCHEMA_JOBS_HANDLER::JobSchErc( JOB* aJob )
m_reporter->Report( wxString::Format( _( "Found %d violations\n" ),
markersProvider->GetCount() ),
RPT_SEVERITY_ERROR );
RPT_SEVERITY_INFO );
ERC_REPORT reportWriter( sch, units );

6
pcbnew/pcbnew_jobs_handler.cpp

@ -1762,16 +1762,16 @@ int PCBNEW_JOBS_HANDLER::JobExportDrc( JOB* aJob )
m_reporter->Report( wxString::Format( _( "Found %d violations\n" ),
markersProvider->GetCount() ),
RPT_SEVERITY_ERROR );
RPT_SEVERITY_INFO );
m_reporter->Report( wxString::Format( _( "Found %d unconnected items\n" ),
ratsnestProvider->GetCount() ),
RPT_SEVERITY_ERROR );
RPT_SEVERITY_INFO );
if( checkParity )
{
m_reporter->Report( wxString::Format( _( "Found %d schematic parity issues\n" ),
fpWarningsProvider->GetCount() ),
RPT_SEVERITY_ERROR );
RPT_SEVERITY_INFO );
}
DRC_REPORT reportWriter( brd, units, markersProvider, ratsnestProvider, fpWarningsProvider );

Loading…
Cancel
Save