Yes. I've tried updating the rootfs image and it seems to no longer complain about gfortran being missing.¹
I just need to clean it up a bit and will push to this branch.

@arnavk23 it looks like it gets stuck. How long did that test set take locally? 2 days?

No, it was done in around 3 hours.

Did you run this same problem? All 6 succeeded? I don't see how because it had forward diff before and that is guaranteed to fail over the binaries

build_benchmark.sh -

# Check for CUTEst benchmarks and verify gfortran
if [[ "${1}" == *OptimizationCUTEst* ]]; then
	echo "--- :hammer: Setting up CUTEst environment"
	echo "Checking gfortran availability..."
	which gfortran || echo "gfortran not found in PATH"
	gfortran --version || echo "gfortran not working"
	export FC=gfortran
	export F77=gfortran
	export F90=gfortran
	echo "Fortran compiler environment variables set"
fi

Okay it has completely stalled with

[ Info: Problem 3/17: HS35
--
  | ┌ Warning: common maxiters argument is currently not used by Feasibility
  | │
  | │ Subject to:
  | │
  | │ Nonlinear
  | │ . Set number of iterations via optimizer specific keyword arguments.
  | └ @ OptimizationMOI /cache/julia-buildkite-plugin/depots/5b300254-1738-4989-ae0a-f4d2d937f953/packages/OptimizationMOI/aKPgG/src/OptimizationMOI.jl:85
  | [ Info: ✓ Solved HS35 with Ipopt - Status: Success
  | [ Info: Completed chunk, memory usage cleaned up
  | [ Info: Processing chunk 2/6: problems 4-6
  | [ Info: Problem 4/17: HS106
  | ┌ Warning: common maxiters argument is currently not used by Feasibility
  | │
  | │ Subject to:
  | │
  | │ Nonlinear
  | │ . Set number of iterations via optimizer specific keyword arguments.
  | └ @ OptimizationMOI /cache/julia-buildkite-plugin/depots/5b300254-1738-4989-ae0a-f4d2d937f953/packages/OptimizationMOI/aKPgG/src/OptimizationMOI.jl:85

and now it's 3 days at that same spot. I think it's safe to say it's not printing anything else. Here's what we can do. We can merge this as it's now at least a major step forward in that it is actually able to run again, but it's still the same problem that it originally had so it's not complete. At least this makes it easier to work on though.

@arnavk23 and you get 6 PDFs from that?

@ChrisRackauckas I was able to get with the original AutoForwardDiff code only.

@ChrisRackauckas I am still trying to see why this is stalling.

@ChrisRackauckas I was able to get with the original AutoForwardDiff code only.

I don't see how. It's not possible for forwarddiff the Fortran binaries, so you couldn't've been differentiating these examples.

@ChrisRackauckas I saw you are doing this on Julia 10.10, try it instead on Julia 10.9

SciML benchmarks only runs on LTS forward. Current LTS is v10.10. But that also won't change this, fundamentally it's impossible for ForwardDiff to differentiate a fortran binary, it's not even possible in theory.

@ChrisRackauckas , I meant the current one with FiniteDiff. Was looking through the code.

Can you show the PDFs built with it?

@ChrisRackauckas It is working, taking some time. Got unconstrained. Further it is your decision as to if I continue on this or not.
CUTEst_unconstrained.pdf

That one ran before, but the issue there is most of them give failures.