[Cron] cron-failure

Ouverte
#435 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
github-actions, julia
Domaine
ci-cd, testing

Piste de recherche

Read the linked Workflow README and inspect the current cron reports and GitHub Actions runs for the failing scope; the payload shows JuMP is clean and the other listed scopes are awaiting runs. Reproduce the failure with the README’s command, then identify whether a problem definition, package, or upstream breakage is responsible. Done when all scopes are clean or an unsupported problem is marked :draft in ext/MetaData/<problem>.jl.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

cron-failure

Cron failures

About this tracking:
A problem marked :valid in metadata failed its slow tests (or the workflow itself crashed).

What to do:

  • Check the failing configuration and reproduce locally using the command below.
  • Fix the problem definition or package, or report an upstream breakage.
  • If the configuration is unsupported, set the problem to :draft in ext/MetaData/<problem>.jl.
  • Details: Workflow README. This issue updates itself; close when all scopes are clean.

Overall Scope Status

Scope Focus Cadence Status
JuMP — Nominal Convergence Default solver configuration (IPOPT/MadNLP on default discretization grids) Weekly (Tuesday 04:00 UTC) ✅ Clean
OptimalControl — Nominal Convergence High-level OptimalControl.jl modeling on standard grids and default solvers Weekly (Wednesday 04:00 UTC) Awaiting run
OptimalControlScalarized — Nominal Convergence Scalarized modeling where vector states/controls are unrolled into scalar components Weekly (Thursday 04:00 UTC) Awaiting run
JuMP — Solver Robustness Perturbs IPOPT solver parameters (mu_strategy, mu_init) to test numerical stability (#378) Monthly (1st, 04:00 UTC) ✅ Clean
OptimalControl — Solver Robustness Perturbs solver parameters for OptimalControl.jl formulations (#378) Monthly (1st, 04:00 UTC) ✅ Clean

JuMP — Nominal Convergence

Focus: Default solver configuration (IPOPT/MadNLP on default discretization grids)
Cadence & runners: CronJuMP.yml · weekly (Tuesday 04:00 UTC) · Julia 1.13, Ubuntu + Windows, CPU

✅ Clean · Run 42494171122 · 2026-11-08 15:27 UTC · Full scope report · Previous run

No findings.

📜 Recent history
  • 2026-11-08 · run — resolved: workflow (all clear)
  • 2026-11-08 · run — new: workflow (error)
## OptimalControl — Nominal Convergence

Focus: High-level OptimalControl.jl modeling on standard grids and default solvers
Cadence & runners: Weekly (Wednesday 04:00 UTC) · Julia 1.13, Ubuntu + Windows (CPU + GPU)

Awaiting next scheduled run.

OptimalControlScalarized — Nominal Convergence

Focus: Scalarized modeling where vector states/controls are unrolled into scalar components
Cadence & runners: Weekly (Thursday 04:00 UTC) · Julia 1.13, Ubuntu + Windows (CPU + GPU)

Awaiting next scheduled run.

JuMP — Solver Robustness

Focus: Perturbs IPOPT solver parameters (mu_strategy, mu_init) to test numerical stability (#378)
Cadence & runners: CronRobustness.yml · monthly (1st, 04:00 UTC) · Julia 1.13, Ubuntu + Windows, CPU

✅ Clean · Run 42494459775 · 2026-11-08 15:32 UTC · Full scope report · Previous run

No findings.

📜 Recent history
  • 2026-11-08 · run — resolved: workflow (all clear)
  • 2026-11-08 · run — new: workflow (error)

OptimalControl — Solver Robustness

Focus: Perturbs solver parameters for OptimalControl.jl formulations (#378)
Cadence & runners: CronRobustness.yml · monthly (1st, 04:00 UTC) · Julia 1.13, Ubuntu + Windows, CPU

✅ Clean · Run 42494459775 · 2026-11-08 15:56 UTC · Full scope report · Previous run

No findings.

📜 Recent history
  • 2026-11-08 · run — resolved: workflow (all clear)
  • 2026-11-08 · run — new: workflow (error)
Langage dominant
Julia
Étoiles
13
Forks
1
Merge moyen
3 h 33 min
PR mergées (30 j)
55

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de control-toolbox/OptimalControlProblems.jl

Toutes les issues de control-toolbox/OptimalControlProblems.jl

Issues similaires

Plus d'issues Julia

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.