Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI throughput #413

Closed
baltzell opened this issue Jan 3, 2025 · 2 comments · Fixed by JeffersonLab/clas12-validation#167 or #416
Closed

CI throughput #413

baltzell opened this issue Jan 3, 2025 · 2 comments · Fixed by JeffersonLab/clas12-validation#167 or #416

Comments

@baltzell
Copy link
Collaborator

baltzell commented Jan 3, 2025

Seems getting too slow sometimes, queuing. Is this repo a major contributor to that? If so, we should cut back job counts significantly.

@baltzell
Copy link
Collaborator Author

baltzell commented Jan 3, 2025

Probably the "validation" triggers need reduction: https://github.com/orgs/JeffersonLab/actions/metrics/usage

@c-dilks
Copy link
Member

c-dilks commented Jan 5, 2025

Probably the "validation" triggers need reduction: https://github.com/orgs/JeffersonLab/actions/metrics/usage

Yeah, by default clas12-validation runs 7 event generators x 6 configurations = 42 jobs per workflow:

{
  "evgen": [
    "e_K",
    "e_KC",
    "e_n",
    "e_g",
    "e_nC",
    "eFT_K",
    "e_gFT"
  ],
  "config": [
    "clas12-default",
    "rga_spring2018",
    "rga_fall2018",
    "rgk_fall2018_FTOn",
    "rgb_fall2019",
    "rgc_summer2022"
  ]
}

We probably don't need to run this many every time, and it indeed clogs the queue. I'm guilty of cancelling some validation jobs since they impede other CI work.

This matrix is configurable from the caller workflow (see the README file), and/or we can change the default matrix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants