[Cron] cron-failure

Aberta
#435 5 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github-actions, julia
Domínio
ci-cd, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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)
Linguagem predominante
Julia
Estrelas
13
Forks
1
Merge médio
3h 33min
PRs com merge (30d)
55

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de control-toolbox/OptimalControlProblems.jl

Todas as issues de control-toolbox/OptimalControlProblems.jl

Issues semelhantes

Mais issues de Julia

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.