alternative-comparisons timeouts on a large set of changes about cms-bot HOT 6 CLOSED

A new Issue was created by @slava77 Slava Krutelyov.

@davidlange6, @Dr15Jones, @smuzaffar, @fabiocos can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

from cms-bot.

@slava77 , unfortunately build area was cleaned up after the jenkins job. I have restarted the comparison job (after modifying the job configuration to not delete the workspace if job aborts). Once this is done I will provide you the tar file

from cms-bot.

Something like this can be applied to resolve this issue as well.
However, perhaps a more straightforward logic of a timeout per individual diff is more appropriate in the jenkins jobs.

I think it would be good enough to know that a given workflow had "gazillion changes" in the DQM histograms. For the details (if they need to be checked) the alternative-comparisons would anyway be impractical in such case (so one would have to check RelMon or download the files to e.g. a private DQM GUI).

from cms-bot.

while rerunning manually compare_useng_files.py with the settings used in the regular procedure, I indeed do see lots of plots being produced for this specific case as result of test failures

from cms-bot.

@slava77 , jenkins job finished now and tar file is available /afs/cern.ch/work/m/muzaffar/public/compare-root23135.tar.gz (6GB). Alternative-comparison for all other workflows took just few seconds but for 250202.181 it did not finish.

from cms-bot.

closing after the fix in #986

from cms-bot.