[Cron] cron-convergence

Aberta
  • Algo errado?
#367 0 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
25/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github-actions, julia
Domínio
testing-qa

Direção de pesquisa

Open the linked GitHub Actions run and compare its report with the previous report on the results branch, following the repository workflow README’s “What to do with the cron issues” guidance. The entry identifies a lost convergence for the JuMP model moonlander on Windows with JuMP 1.13 and Ipopt. Done when a maintainer determines whether this is expected or a regression; close the issue when its sections say No findings.

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

Descrição

cron-convergence

Convergence that got worse

Written by the weekly cron workflows, one section per scope, replaced by each run of that scope. Convergence is reported, not tested (#360): each entry below is a solve that converged in the previous run of the scope and no longer does, or whose objective moved by more than the threshold of tools/cron/report.py.

Who: a maintainer looks; nothing fails and nothing changes automatically.

What to do: open the run, compare with the previous report on the results branch, and decide whether the change is expected (new initial guess, new solver version) or a regression to investigate. Details: README. This issue updates itself; close it when the sections say No findings.

cron-convergence

Run: https://github.com/control-toolbox/OptimalControlProblems.jl/actions/runs/42104098308

No findings.

cron-convergence

Run: https://github.com/control-toolbox/OptimalControlProblems.jl/actions/runs/42104112877

No findings.

cron-convergence

Run: https://github.com/control-toolbox/OptimalControlProblems.jl/actions/runs/42104106091

No findings.

cron-convergence

Run: https://github.com/control-toolbox/OptimalControlProblems.jl/actions/runs/42160705632

No findings.

Linguagem predominante
Julia
Estrelas
13
Forks
1
Merge médio
3h 24min
PRs com merge (30d)
34

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.