Share the GPU smoke test between OptimalControl and OptimalControlScalarized

Aperta
  • Qualcosa non va?
#445 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ocots ci sta già lavorando.

Dal 10/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Context

Follow-up of #441, to be done once its phase C (shared OptimalControl / OptimalControlScalarized runners in test/common/optimalcontrol_tests.jl) is merged.

The two GPU smoke files differ only by the backend and the configuration group:

  • test/suite/GPU/test_smoke_optimalcontrol.jl (GPU_CONFIGS.OptimalControl, entry function test_smoke_optimalcontrol)
  • test/suite/GPU/test_smoke_scalarized.jl (GPU_CONFIGS.OptimalControlScalarized, entry function test_smoke_scalarized)

Everything else is identical: the CUDA_FUNCTIONAL branch with the visible skip (TST6), the solve with SMOKE_GRID and SMOKE_MAX_ITER, and the finite-objective check.

Goal

Factor the GPU smoke test into one shared implementation parameterized by the backend, as #441 does for test_problem, test_smoke and test_convergence, without changing the behavior on a CPU runner or on a GPU runner.

Proposed approach

  • In test/common/optimalcontrol_tests.jl, or in a new test/common/gpu_tests.jl if the module must not load Main.TestCapabilities in CPU environments, add test_smoke_gpu(backend). The configurations come from getfield(Main.TestConfigs.GPU_CONFIGS, Main.TestStatus.modeling(backend)).
  • Keep the two test files, each as a thin wrapper with its own module and entry function (TST1), so that the report names (test_smoke_optimalcontrol <label>, test_smoke_scalarized <label>) do not change.
  • Keep TST6: no early return in a @testset, Test.@test_skip without a functional device, and test_contract.jl still fails loudly on a kkt or occidata runner without a device.
  • Check that tools/ci/scope.py (Repository.includers) still finds the includers of the new shared file; GPU is an opt-in environment, so it never enters the automatic scope. Add a case to tools/ci/test/test_scope.py if a new file is created.
  • Update test/README.md ("GPU tests") if the layout changes.

Out of scope

  • The GPU configurations and the solvers (GPU_CONFIGS in test/common/configs.jl).
  • Running the GPU tests in CI: they need the run ci kkt-runner or run ci occidata-runner label, and a runner with a device.

Checks

  • On a CPU machine: Pkg.test(; test_args=["GPU"]) reports the same tests as Broken (skipped) as before.
  • On a GPU runner: the same solves run and the same lines appear in the report.
Lingua principale
Julia
Stelle
13
Fork
1
Merge medio
3h 36m
PR unite (30g)
57

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di control-toolbox/OptimalControlProblems.jl

Tutte le issue di control-toolbox/OptimalControlProblems.jl

Issue simili

Altre issue su Julia

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.