
from rtt tests in nightlies 16.6.x(-val), the following jobs *don't crash*, but display error messages:

  - job pu_mu0.0_d479 - https://atlasrtt.cern.ch/rtt/rel_0/16.6.x-val/build/i686-slc5-gcc43-opt/offline/recjobtransformtests/pu_mu0.0_d479/pu_mu0.0_d479_log
  - job pu_mu2.0_d480 - https://atlasrtt.cern.ch/rtt/rel_0/16.6.x-val/build/i686-slc5-gcc43-opt/offline/recjobtransformtests/pu_mu2.0_d480/pu_mu2.0_d480_log
  - job pu_mu4.0_d481 - https://atlasrtt.cern.ch/rtt/rel_0/16.6.x-val/build/i686-slc5-gcc43-opt/offline/recjobtransformtests/pu_mu4.0_d481/pu_mu4.0_d481_log
  - job pu_mu10.0_d482 - https://atlasrtt.cern.ch/rtt/rel_0/16.6.x-val/build/i686-slc5-gcc43-opt/offline/recjobtransformtests/pu_mu10.0_d482/pu_mu10.0_d482_log
  - job pu_mu15.0_d483 - https://atlasrtt.cern.ch/rtt/rel_0/16.6.x-val/build/i686-slc5-gcc43-opt/offline/recjobtransformtests/pu_mu15.0_d483/pu_mu15.0_d483_log

please click on the links above for *full logfiles*.

these errors are not detected by the rtt system, and jobs are not reported as bad (red).
*should the errors be flagged by rtt, or should the errors be demoted to warnings?*

best regards,
guilherme
reco validation shifter 

--------- brief logfile excerpt showing the crash -----------
guid retrieval: attempting to use fclistguid to retrieve guid from myaod.pool.root.
fclistguid -p myaod.pool.root
guid retrieval: 7621d623-6342-e011-915a-000423d5b46a (myaod.pool.root) found in xmlcatalog_file:poolfilecatalog.xml
retrying getsize('myntup_trig.root')
getsize('myntup_trig.root') failed
py:esdtoaod         *error* during execution of esdtoaod, exception caught: *[errno 2] no such file or directory: 'myntup_trig.root'*
py:esdtoaod          info jobtransform completed for esdtoaod with error code 63400 (exit code 0)
