Add Nsight Compute CLI python libraries

[fwyzard]

Properly package the Nsight Compute command line client and python libraries.

[cmsbuild]

A new Pull Request was created by @fwyzard (Andrea Bocci) for branch IB/CMSSW_10_5_X/gcc700.

@cmsbuild, @smuzaffar, @gudrutis, @mrodozov can you please review it and eventually sign? Thanks.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.

[fwyzard]

@smuzaffar do you think this should work ?

The idea is to have in the PATH the file nv-nsight-cu-cli, which internally will launch $CUDA_BASE/NsightCompute-1.0/target/linux-desktop-glibc_2_11_3-glx-x64/nv-nsight-cu-cli .

If it works, do you think it would make sense to merge the cuda-gdb wrapper package here as well ?

[smuzaffar]

@fwyzard , this should work. By the way, nv-nsight-cu-cli is already in PATH, so why you want to add wrapper?

Looks like nv-nsight-cu-cli is broken for slc6 (due to GLIBC version mismatch)

nv-nsight-cu-cli -v
nv-nsight-cu-cli: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by nv-nsight-cu-cli)

[fwyzard]

By the way, nv-nsight-cu-cli is already in PATH, so why you want to add wrapper?

I put it in the PATH moving it and its support libraries from $CUDA_BASE/NsightCompute-1.0/target/linux-desktop-glibc_2_11_3-glx-x64/nv-nsight-cu-cli to $CUDA_BASE/bin .
However I just discovered that it looks for some support files in ../../ProfileSectionTemplates by default, which then gets broken.

[fwyzard]

Looks like nv-nsight-cu-cli is broken for slc6 (due to GLIBC version mismatch)

Not much we can do - RHEL 6 and RHEL 7 use the same installer - apart from a bug report to NVIDIA.

[fwyzard]

@cmsbuild, please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/32532/console

[cmsbuild]

+1
Tested at: 4a26c87
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4630/32532/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4630/32532/summary.html

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 2 differences found in the comparisons
• DQMHistoTests: Total files compared: 33
• DQMHistoTests: Total histograms compared: 3153717
• DQMHistoTests: Total failures: 13
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3153500
• DQMHistoTests: Total skipped: 204
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
• Checked 137 log files, 14 edm output root files, 33 DQM output files

[fwyzard]

@smuzaffar, is it possible to test the external built by Jenkins interactively ?

[fwyzard]

OK, from a local build it seems to work as intended.

[smuzaffar]

@fwyzard , no it is not possible to test it interactively from jenkins. Once the jenkins job is done then the build area is cleaned up.
We can upload the RPMS to e.g. cms-PR<NUM> repository for any extra tests if needed.