Remove leading ../../ from logArchive tarballs

[amaltaro]

Fixes #10867

Status

ready

Description

The arcname option allow us to specify an alternative name for the file in the tarball archive. It turns out we were removing only part of the initial path, instead of removing the ../../ as well.

With this change, files inside the tarball should all be set as a top level/directory.

Is it backward compatible (if not, which system it affects?)

YES

Related PRs

None

External dependencies / deployment changes

None

[cmsdmwmbot]

Jenkins results:

• Python2 Unit tests: succeeded
• Python3 Unit tests: succeeded
  • 2 changes in unstable tests
• Python2 Pylint check: failed
  • 3 warnings and errors that must be fixed
  • 1 warnings
  • 13 comments to review
• Python3 Pylint check: failed
  • 5 warnings and errors that must be fixed
  • 1 warnings
  • 8 comments to review
• Pylint py3k check: succeeded
• Pycodestyle check: succeeded
  • 3 comments to review

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-WMCore-PR-test/12516/artifact/artifacts/PullRequestReport.html

[amaltaro]

Haaa, and this fixes the problem. New tarball files created with this patch look like:

_condor_stderr
job/WMTaskSpace/cmsRun1/cmsRun1-stderr.log
job/WMTaskSpace/cmsRun1/PSet.py
job/WMTaskSpace/cmsRun1/Report.pkl
job/WMTaskSpace/cmsRun1/FrameworkJobReport.xml
job/WMTaskSpace/cmsRun1/PSet.pkl
job/WMTaskSpace/cmsRun1/cmsRun1-stdout.log
job/WMTaskSpace/stageOut1/Report.pkl
_condor_stdout
wmagentJob.log

[amaltaro]

Sorry for rushing with this, but I want to put it in a new patch release still this morning. Feedback is welcome at any time.