Retrigger v7 outputs for 6 cancelled folders (batch 4: optimization/PINN/NN)#1561
Closed
ChrisRackauckas-Claude wants to merge 1 commit into
Closed
Conversation
Continuation of the v7-stack-output retrigger campaign. These six folders (optimization + PINN + neural networks family) had their Manifest.toml regenerated in PR SciML#1551 but were cancelled by the 24h queue-wait timeout: - GlobalOptimization - OptimizationCUTEst - OptimizationFrameworks - PINNErrorsVsTime - PINNOptimizers - NeuralNetworks No-op apart from a comment line in each Project.toml. Note: OptimizationCUTEst overlaps with the work on open PR SciML#1555, which migrates these benchmarks to the Optimization.jl interface. If SciML#1555 lands first, this retrigger is unnecessary for CUTEst. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
2 tasks
Contributor
Author
|
Superseded — closing this 'trigger comment' PR in favor of clean per-folder PRs with real content changes (compat bumps, manifest regens, or actual benchmark fixes) instead of the hack |
ChrisRackauckas-Claude
pushed a commit
to ChrisRackauckas-Claude/SciMLBenchmarks.jl
that referenced
this pull request
May 22, 2026
amdci3-1 corrupts its workspace under rapid dispatch — when 2+ jobs arrive within seconds, all but one die with errors like: ##[error]Missing file at path: ..._runner_file_commands/set_output_... ##[error]Can't find action.yml under .../_actions/actions/checkout/v6 ##[error]The operation was canceled. Single jobs on the runner run cleanly; the bug is purely concurrency-on-the-same-runner. Reproduced 3 times now: 1. Original 25374549824 v7 run: 3 jobs cancelled-mid-checkout in seconds 2. 2026-05-16 07:58 UTC burst: 6 jobs from PRs SciML#1559/SciML#1560/SciML#1561 dispatched to amdci3-1, all but one corrupted (StiffODE — which had been cleanly running for 16h — also got cancelled in the cascade) 3. 2026-05-16 08:31 UTC burst: all 5 single-folder PRs SciML#1563-SciML#1567 dispatched simultaneously, all 5 corrupted within seconds Splitting into per-folder PRs (per Chris's direction) doesn't help when multiple PRs are opened together — cross-PR dispatch hits the same race. Fix: job-level concurrency with a constant group + cancel-in-progress:false makes every matrix entry across every Benchmarks workflow run queue behind any other in-flight matrix entry. detect-changes / manual-matrix / publish jobs are unaffected (they're separate GHA jobs). Adds max-parallel: 1 to the matrix as defense-in-depth — within a single run, matrix entries already serialize via the concurrency group, but max-parallel makes it explicit. Throughput cost: even with two healthy runners (amdci1-1 + amdci3-1), only one benchmark job runs at a time. Acceptable given the alternative is a ~60% job-loss rate. Can be relaxed once the runner bug is fixed — e.g. parameterize the concurrency group by matrix.runner to allow one job per runner. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Re-queues six more cancelled folders from the v7 stack rollout (optimization, PINN, neural networks family). Builds on #1558, #1559, #1560:
benchmarks/GlobalOptimizationbenchmarks/OptimizationCUTEstbenchmarks/OptimizationFrameworksbenchmarks/PINNErrorsVsTimebenchmarks/PINNOptimizersbenchmarks/NeuralNetworksMechanism: one-line comment appended to each Project.toml.
Coordination note
OptimizationCUTEstoverlaps with the work in open PR #1555 (Optimization.jl interface alignment, currently with failing CI). If #1555 lands first, this retrigger for CUTEst is redundant.Note for review
Please ignore until reviewed by @ChrisRackauckas.