Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmssam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • etf
  • cmssam
  • Issues
  • #1

Closed
Open
Created Oct 26, 2017 by Rokas Maciulaitis@rmaciula

MC test local stage out failures with no info

Hi,

Looking at MC test log of T2_ES_IFCA [1], I realized that stage out was done to PIC (fallback option). Would be nice to have more detailed log, because now there is nothing about local stage out when it fails. We should print something in this part [2].

In IFCA case, local stage out is failing because targetPFN [3] variable is none, due missing missing/wrong rule in storage.xml. But tests is succeeding as fallback stage out to PIC works well.

[1] http://wlcg-sam-cms.cern.ch/dashboard/request.py/metricOutput?host=gridce01.ifca.es&time=2017-10-26T07:40:18Z&metricfqan=org.cms.WN-mc%20(_cms_Role_production)

[2] https://gitlab.cern.ch/etf/cmssam/blob/master/SiteTests/MonteCarlo/cms-MC-test/RuntimeSAMStageOut.py#L226

[3] https://gitlab.cern.ch/etf/cmssam/blob/master/SiteTests/MonteCarlo/cms-MC-test/RuntimeSAMStageOut.py#L197

Edited Oct 26, 2017 by Rokas Maciulaitis
Assignee
Assign to
Time tracking