Empty Igprof Comparison cpu usage RECO produce methods

[clacaputo]

Igprof Comparison cpu usage RECO produce methods item, produced during PR tests, is empty. Here an example: Igprof Comparison cpu usage RECO produce methods..

I've seen it also a few weeks ago and thought it was temporary. I can't say when the first occurrence happened.

[cmsbuild]

A new Issue was created by @clacaputo Claudio Caputo.

@Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[makortel]

assign core

[makortel]

@gartung Could you take a look?

[cmsbuild]

New categories assigned: core

@Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks

[gartung]

I inadvertently removed the python file used to produce that report when I was cleaning up the repo.

 /data/cmsbld/jenkins/workspace/ib-run-pr-profiling/profiling/Analyze_tool/compare_cpu_txt.py --old CMSSW_13_0_X_2023-01-12-2300_RES_CPU_step3.txt --new RES_CPU_step3.txt
/data/cmsbld/jenkins/workspace/ib-run-pr-profiling/cms-bot/pr_testing/run-pr-profiling.sh: line 48: /data/cmsbld/jenkins/workspace/ib-run-pr-profiling/profiling/Analyze_tool/compare_cpu_txt.py: No such file or directory

I am putting that back now.

[gartung]

I reran the Jenkins job and the file was created. I am not sure where it was uploaded. You may need to rerun the pull request tests to get the new results.

[gartung]

It appears that the files for the IB could not be found or didn't get downloaded the second time I ran it.

+ get_jenkins_artifacts igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt CMSSW_13_0_X_2023-01-13-1100_RES_CPU_step3.txt
+ local SRC=igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt
+ local DES=CMSSW_13_0_X_2023-01-13-1100_RES_CPU_step3.txt
+ local AFDIR=/data/sdt/SDT/jenkins-artifacts
++ echo igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt
++ sed 's|^/*||;s|/.*||'
++ grep '^ib-baseline-tests$'
++ wc -l
+ '[' 0 -eq 1 ']'
+ '[' X = X -a -e /cvmfs/cms-ci.cern.ch/jenkins-artifacts/igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt ']'
+ case $SRC in
++ dirname CMSSW_13_0_X_2023-01-13-1100_RES_CPU_step3.txt
+ mkdir -p .
+ has_jenkins_artifacts igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt
+ local SRC=igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt
+ local TYPE=
+ local AFDIR=/data/sdt/SDT/jenkins-artifacts
++ echo igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt
++ sed 's|^/*||;s|/.*||'
++ wc -l
++ grep '^ib-baseline-tests$'
+ '[' 0 -eq 1 ']'
+ '[' X = X ']'
+ TYPE=-e
+ for i in 1 2 3 4 5 6 7 8 9
++ grep '^JA_RUN1='
++ timeout 60 ssh -q -o ConnectTimeout=60 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ServerAliveInterval=60 cmsbuild@cmssdt01.cern.ch 'echo JA_RUN1=CONN && test -e /data/sdt/SDT/jenkins-artifacts/igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/RES_CPU_step3.txt || echo JA_RUN1=FAIL'
++ wc -l
+ RES=2
+ '[' 2 -eq 1 ']'
+ '[' 2 -eq 2 ']'
+ echo JA_STATUS=ERROR
JA_STATUS=ERROR
+ return 1
+ return 1
+ true
+ /data/cmsbld/jenkins/workspace/ib-run-pr-profiling/profiling/Analyze_tool/compare_cpu_txt.py --old CMSSW_13_0_X_2023-01-13-1100_RES_CPU_step3.txt --new RES_CPU_step3.txt
Traceback (most recent call last):
  File "/data/cmsbld/jenkins/workspace/ib-run-pr-profiling/profiling/Analyze_tool/compare_cpu_txt.py", line 59, in <module>
    with open(args.old) as f:
FileNotFoundError: [Errno 2] No such file or directory: 'CMSSW_13_0_X_2023-01-13-1100_RES_CPU_step3.txt'

[gartung]

The igprof cpu profile for the 01-13-1100 IB crashed so there was no 'CMSSW_13_0_X_2023-01-13-1100_RES_CPU_step3.txt' file prodiuced.
https://cmssdt.cern.ch/SDT/jenkins-artifacts/igprof/CMSSW_13_0_X_2023-01-13-1100/el8_amd64_gcc11/profiling/11834.21/step3_igprof_cpu.log

[gartung]

It worked the second time
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-a3f7c8/30032/profiling/11834.21/RES_CPU_compare_11834.21.txt

[gartung]

@clacaputo It appears to be fixed.

[smuzaffar]

should we close this issue then?