add cuopt direct solver #3620

Iroy30 · 2025-06-04T18:31:12Z

Fixes #3626

Summary/Motivation:

Add cuOpt math optimization (includes LP and MILP) solver backend to Pyomo so users can solve pyomo models with cuOpt

Changes proposed in this PR:

Add cuopt_direct solver plugin

Legal Acknowledgement

By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution:

I agree my contributions are submitted under the BSD license.
I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

codecov · 2025-06-17T05:20:43Z

Codecov Report

Attention: Patch coverage is 23.24324% with 142 lines in your changes missing coverage. Please review.

Project coverage is 85.72%. Comparing base (10d6acc) to head (e2e9159).

Files with missing lines	Patch %	Lines
pyomo/solvers/plugins/solvers/cuopt_direct.py	23.24%	142 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3620      +/-   ##
==========================================
- Coverage   89.05%   85.72%   -3.34%     
==========================================
  Files         890      891       +1     
  Lines      102617   102802     +185     
==========================================
- Hits        91384    88122    -3262     
- Misses      11233    14680    +3447

Flag	Coverage Δ
builders	`26.65% <23.24%> (-0.01%)`	⬇️
default	`85.53% <23.24%> (?)`
expensive	`34.01% <23.24%> (?)`
linux	`?`
linux_other	`?`
osx	`?`
win	`?`
win_other	`?`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

mrmundt

We are working on making cuopt available in our testing infrastructure; can you please add tests to this PR?

mrmundt · 2025-07-01T15:57:07Z

@Iroy30 - We've been able to make cuopt available on our internal testing machines. Can you please add tests to this PR?

Iroy30 · 2025-07-02T12:38:58Z

@mrmundt Thanks! We have added tests by enabling testing cuopt with LP and MILP capabilities in tests/solvers.py. Let us know if:

There is any other testing that needs to be enabled.
For testing cuOpt backend in CI, it needs a GPU, is that something pyomo team intends to add or will it be disabled in github CI?

The following is the testing output I get relevant to cuOpt

Testing scenario generation
------------------------------
LP_block, cuopt, python
   ok: 
LP_block_kernel, cuopt, python
   ok: 
LP_compiled, cuopt, python
   ok: 
LP_compiled_dense_kernel, cuopt, python
   ok: 
LP_compiled_sparse_kernel, cuopt, python
   ok: 
LP_constant_objective1, cuopt, python
   ok: 
LP_constant_objective1_kernel, cuopt, python
   ok: 
LP_constant_objective2, cuopt, python
   ok: 
LP_constant_objective2_kernel, cuopt, python
   ok: 
LP_duals_maximize, cuopt, python
   ok: 
LP_duals_maximize_kernel, cuopt, python
   ok: 
LP_duals_minimize, cuopt, python
   ok: 
LP_duals_minimize_kernel, cuopt, python
   ok: 
LP_inactive_index, cuopt, python
   ok: 
LP_inactive_index_kernel, cuopt, python
   ok: 
LP_infeasible1, cuopt, python
   ok: 
LP_infeasible1_kernel, cuopt, python
   ok: 
LP_infeasible2, cuopt, python
   ok: 
LP_infeasible2_kernel, cuopt, python
   ok: 
LP_piecewise, cuopt, python
   ok: 
LP_piecewise_nosuffixes, cuopt, python
   ok: 
LP_simple, cuopt, python
   ok: 
LP_simple_kernel, cuopt, python
   ok: 
LP_trivial_constraints, cuopt, python
   ok: 
LP_trivial_constraints_kernel, cuopt, python
   ok: 
LP_unbounded, cuopt, python
   ok: 
LP_unbounded_kernel, cuopt, python
   ok: 
LP_unused_vars, cuopt, python
   ok: 
LP_unused_vars_kernel, cuopt, python
   ok: 
MILP_discrete_var_bounds, cuopt, python
   ok: 
MILP_discrete_var_bounds_kernel, cuopt, python
   ok: 
MILP_infeasible1, cuopt, python
   ok: 
MILP_infeasible1_kernel, cuopt, python
   ok: 
MILP_simple, cuopt, python
   ok: 
MILP_simple_kernel, cuopt, python
   ok: 
MILP_unbounded, cuopt, python
   ok: 
MILP_unbounded_kernel, cuopt, python
   ok: 
MILP_unused_vars, cuopt, python
   ok: 
MILP_unused_vars_kernel, cuopt, python
   ok:

pyomo/solvers/plugins/solvers/cuopt_direct.py

mrmundt · 2025-07-02T13:35:58Z

pyomo/solvers/plugins/solvers/cuopt_direct.py

+        t0 = time.time()
+        self.solution = cuopt.linear_programming.solver.Solve(self._solver_model)
+        t1 = time.time()


This is fine, but just so you're aware, we have this lovely little utility called TicTocTimer that you may want to consider using: https://pyomo.readthedocs.io/en/latest/api/pyomo.common.timing.TicTocTimer.html

whart222 · 2025-07-08T18:49:09Z

@mrmundt What do you think about including this solver interface in pyomo.contrib.solvers? Would it make sense to pull-in new solver interfaces there, since that's where the new solver API is evolving?

mrmundt · 2025-07-08T18:53:06Z

@mrmundt What do you think about including this solver interface in pyomo.contrib.solvers? Would it make sense to pull-in new solver interfaces there, since that's where the new solver API is evolving?

@whart222 - I am evenly split. Because we are still messing with what the new solver interfaces are going to actually do / how they will handle input and present output, I don't know if we want to put "new" solvers there or just "well-established" ones that we can robustly test / really know what they are supposed to do and return.

mrmundt · 2025-07-08T18:57:44Z

@Iroy30 - I forgot to post this last week, but all of the failures are of the variety:

self = <pyomo.solvers.tests.checks.test_no_solution_behavior.Test_LP_unbounded_kernel testMethod=test_cuopt_python>

    def return_test(self):
>       return failed_solve_test(self)

/tester/python/python39/pyomo/pyomo/solvers/tests/checks/test_no_solution_behavior.py:92: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/tester/python/python39/pyomo/pyomo/solvers/tests/checks/test_no_solution_behavior.py:61: in failed_solve_test
    opt, results = model_class.solve(
/tester/python/python39/pyomo/pyomo/solvers/tests/models/base.py:123: in solve
    results = opt.solve(
/tester/python/python39/pyomo/pyomo/opt/base/solvers.py:99: in solve
    self._solver_error('solve')
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <pyomo.opt.base.solvers.UnknownSolver object at 0x7f86ad9ab040>
method_name = 'solve'

        def _solver_error(self, method_name):
>           raise RuntimeError(
                """Attempting to use an unavailable solver.
    
    The SolverFactory was unable to create the solver "%s"
    and returned an UnknownSolver object.  This error is raised at the point
    where the UnknownSolver object was used as if it were valid (by calling
    method "%s").
    
    The original solver was created with the following parameters:
    \t"""
                % (self.type, method_name)
                + "\n\t".join("%s: %s" % i for i in sorted(self._kwds.items()))
                + "\n\t_args: %s" % (self._args,)
                + "\n\toptions: %s" % (self.options,)
            )
E           RuntimeError: Attempting to use an unavailable solver.
E           
E           The SolverFactory was unable to create the solver "cuopt"
E           and returned an UnknownSolver object.  This error is raised at the point
E           where the UnknownSolver object was used as if it were valid (by calling
E           method "solve").
E           
E           The original solver was created with the following parameters:
E           	executable: cuopt
E           	solver_io: python
E           	type: cuopt
E           	_args: ()
E           	options: {}

/tester/python/python39/pyomo/pyomo/opt/base/solvers.py:116: RuntimeError

mrmundt · 2025-07-08T19:11:11Z

@Iroy30 - Two more things:

Please run black -S -C on your files
Something in our testing environment isn't loading correctly. I'm looking into it.

Co-authored-by: Miranda Mundt <[email protected]>

mrmundt · 2025-07-10T15:07:25Z

pyomo/solvers/plugins/solvers/cuopt_direct.py

+            "Integers": "I",
+            "Reals": "C",
+            "Binary": "I",
+        }  # NonNegativeReals ?


I am fairly certain this is necessary. I got the tests running on our test machine, and I keep getting these errors:

__________________________________________________________ Test_LP_block.test_cuopt_direct_python_nonsymbolic_labels ___________________________________________________________ self = <pyomo.solvers.tests.checks.test_pickle.Test_LP_block testMethod=test_cuopt_direct_python_nonsymbolic_labels> def return_test(self): > return pickle_test(self) pyomo/solvers/tests/checks/test_pickle.py:141: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ pyomo/solvers/tests/checks/test_pickle.py:48: in pickle_test opt, status = model_class.solve( pyomo/solvers/tests/models/base.py:123: in solve results = opt.solve( pyomo/solvers/plugins/solvers/direct_solver.py:130: in solve self._presolve(*args, **kwds) pyomo/solvers/plugins/solvers/direct_solver.py:68: in _presolve self._set_instance(model, kwds) pyomo/solvers/plugins/solvers/cuopt_direct.py:140: in _set_instance self._add_block(model) pyomo/solvers/plugins/solvers/cuopt_direct.py:143: in _add_block self._add_var( _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <pyomo.solvers.plugins.solvers.cuopt_direct.CUOPTDirect object at 0x7f91e6fc5050>, variables = <generator object BlockData.component_data_objects at 0x7f91ec180a60> def _add_var(self, variables): # Map vriable to index and get var bounds var_type_dict = { "Integers": "I", "Reals": "C", "Binary": "I", } # NonNegativeReals ? self.var_name_dict = {} v_lb, v_ub, v_type = [], [], [] for i, v in enumerate(variables): > v_type.append(var_type_dict[str(v.domain)]) E KeyError: 'NonNegativeReals' pyomo/solvers/plugins/solvers/cuopt_direct.py:100: KeyError

I am also seeing errors like this:

pyomo/solvers/tests/checks/test_no_solution_behavior.py:92: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ pyomo/solvers/tests/checks/test_no_solution_behavior.py:61: in failed_solve_test opt, results = model_class.solve( pyomo/solvers/tests/models/base.py:123: in solve results = opt.solve( pyomo/solvers/plugins/solvers/direct_solver.py:130: in solve self._presolve(*args, **kwds) pyomo/solvers/plugins/solvers/direct_solver.py:68: in _presolve self._set_instance(model, kwds) pyomo/solvers/plugins/solvers/cuopt_direct.py:140: in _set_instance self._add_block(model) pyomo/solvers/plugins/solvers/cuopt_direct.py:143: in _add_block self._add_var( _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <pyomo.solvers.plugins.solvers.cuopt_direct.CUOPTDirect object at 0x7f05bc563e10> variables = <generator object _component_data_objects at 0x7f043a8d6890> def _add_var(self, variables): # Map vriable to index and get var bounds var_type_dict = { "Integers": "I", "Reals": "C", "Binary": "I", } # NonNegativeReals ? self.var_name_dict = {} v_lb, v_ub, v_type = [], [], [] for i, v in enumerate(variables): > v_type.append(var_type_dict[str(v.domain)]) E AttributeError: property 'domain' of 'variable' object has no getter pyomo/solvers/plugins/solvers/cuopt_direct.py:100: AttributeError

Plus some other errors:

self = <pyomo.solvers.tests.checks.test_pickle.Test_LP_duals_maximize testMethod=test_cuopt_direct_python_nonsymbolic_labels> def return_test(self): > return pickle_test(self) pyomo/solvers/tests/checks/test_pickle.py:141: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ pyomo/solvers/tests/checks/test_pickle.py:48: in pickle_test opt, status = model_class.solve( pyomo/solvers/tests/models/base.py:123: in solve results = opt.solve( pyomo/solvers/plugins/solvers/direct_solver.py:168: in solve result = self._postsolve() pyomo/solvers/plugins/solvers/cuopt_direct.py:246: in _postsolve self._load_rc() _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <pyomo.solvers.plugins.solvers.cuopt_direct.CUOPTDirect object at 0x7f909a5f4dd0> vars_to_load = KeysView(<pyomo.common.collections.component_map.ComponentMap object at 0x7f9099137af0>) def _load_rc(self, vars_to_load=None): if not hasattr(self._pyomo_model, "rc"): self._pyomo_model.rc = Suffix(direction=Suffix.IMPORT) rc = self._pyomo_model.rc var_map = self._pyomo_var_to_ndx_map if vars_to_load is None: vars_to_load = var_map.keys() > reduced_costs = self.solution.get_reduced_costs() E AttributeError: 'Solution' object has no attribute 'get_reduced_costs' pyomo/solvers/plugins/solvers/cuopt_direct.py:261: AttributeError

________________________________________________________ Test_LP_unbounded.test_cuopt_direct_python_nonsymbolic_labels _________________________________________________________ self = <pyomo.solvers.tests.checks.test_pickle.Test_LP_unbounded testMethod=test_cuopt_direct_python_nonsymbolic_labels> def return_test(self): > return pickle_test(self) pyomo/solvers/tests/checks/test_pickle.py:141: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ pyomo/solvers/tests/checks/test_pickle.py:48: in pickle_test opt, status = model_class.solve( pyomo/solvers/tests/models/base.py:123: in solve results = opt.solve( pyomo/solvers/plugins/solvers/direct_solver.py:168: in solve result = self._postsolve() _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <pyomo.solvers.plugins.solvers.cuopt_direct.CUOPTDirect object at 0x7f909927cbd0> def _postsolve(self): extract_duals = False extract_slacks = False extract_reduced_costs = False for suffix in self._suffixes: flag = False if re.match(suffix, "rc"): extract_reduced_costs = True flag = True if not flag: raise RuntimeError( "***The cuopt_direct solver plugin cannot extract solution suffix=" + suffix ) solution = self.solution status = solution.get_termination_status() self.results = SolverResults() soln = Solution() self.results.solver.name = "CUOPT" self.results.solver.wallclock_time = self._wallclock_time prob_type = solution.problem_category if status in [1]: self.results.solver.status = SolverStatus.ok self.results.solver.termination_condition = TerminationCondition.optimal soln.status = SolutionStatus.optimal elif status in [3]: self.results.solver.status = SolverStatus.warning self.results.solver.termination_condition = TerminationCondition.unbounded soln.status = SolutionStatus.unbounded elif status in [8]: self.results.solver.status = SolverStatus.ok self.results.solver.termination_condition = TerminationCondition.feasible soln.status = SolutionStatus.feasible elif status in [2]: self.results.solver.status = SolverStatus.warning self.results.solver.termination_condition = TerminationCondition.infeasible soln.status = SolutionStatus.infeasible elif status in [4]: self.results.solver.status = SolverStatus.aborted self.results.solver.termination_condition = ( TerminationCondition.maxIterations ) soln.status = SolutionStatus.stoppedByLimit elif status in [5]: self.results.solver.status = SolverStatus.aborted self.results.solver.termination_condition = ( TerminationCondition.maxTimeLimit ) soln.status = SolutionStatus.stoppedByLimit elif status in [7]: self.results.solver.status = SolverStatus.ok self.results.solver.termination_condition = TerminationCondition.other soln.status = SolutionStatus.other else: self.results.solver.status = SolverStatus.error self.results.solver.termination_condition = TerminationCondition.error soln.status = SolutionStatus.error if self._solver_model.maximize: self.results.problem.sense = maximize else: self.results.problem.sense = minimize self.results.problem.upper_bound = None self.results.problem.lower_bound = None try: self.results.problem.upper_bound = solution.get_primal_objective() self.results.problem.lower_bound = solution.get_primal_objective() except Exception as e: pass var_map = self._pyomo_var_to_ndx_map primal_solution = solution.get_primal_solution().tolist() for i, pyomo_var in enumerate(var_map.keys()): > pyomo_var.set_value(primal_solution[i], skip_validation=True) E IndexError: list index out of range pyomo/solvers/plugins/solvers/cuopt_direct.py:243: IndexError ----------------------------------------------------------------------------- Captured stdout call ----------------------------------------------------------------------------- Setting parameter log_file to Error in solve_lp: {"CUOPT_ERROR_TYPE": "ValidationError", "msg": "A_offsets must be set before calling the solver."}

mrmundt · 2025-07-10T15:10:36Z

Hi @Iroy30 - I got the tests running - the name in the solvers.py file was the culprit. That being said, there are quite a few errors (mentioned in the comment above).

It would be a good idea for you to create a test_cuopt.py file in pyomo/solvers/tests/checks and incorporate unit tests, small tests for basic functionality, little models that you know the answer for, etc.

Iroy30 · 2025-07-10T16:42:40Z

I am looking at the "Attempting to use an unavailable solver" error currently. The rest should be fixed.

Something in our testing environment isn't loading correctly. I'm looking into it.

Is this resolved?

mrmundt · 2025-07-10T16:44:34Z

I am looking at the "Attempting to use an unavailable solver" error currently. The rest should be fixed.

Something in our testing environment isn't loading correctly. I'm looking into it.

Is this resolved?

Yes, I fixed that. Please look at the other errors I posted in different comments above.

Iroy30 · 2025-07-16T02:37:10Z

we are investigating certain Termination condition mismatches on our end

add cuopt direct solver

90adbf4

blnicho requested a review from whart222 June 10, 2025 18:46

blnicho mentioned this pull request Jun 13, 2025

Support NVIDIA cuOpt solver #3626

Open

jsiirola added the AT: PRE-TEST INSPECTED label Jun 17, 2025

pyomo-autotest removed the AT: PRE-TEST INSPECTED label Jun 17, 2025

mrmundt reviewed Jun 17, 2025

View reviewed changes

Iroy30 added 2 commits July 2, 2025 05:29

add tests with lp amd milp capabilities

b4b1502

Merge remote-tracking branch 'origin/main'

6f64094

Iroy30 force-pushed the add_cuopt_direct_solver_plugin branch from 5dbf9dd to 6f64094 Compare July 2, 2025 12:33

mrmundt reviewed Jul 2, 2025

View reviewed changes

mrmundt added the AT: PRE-TEST INSPECTED label Jul 2, 2025

pyomo-autotest removed the AT: PRE-TEST INSPECTED label Jul 2, 2025

mrmundt added the AT: RETEST label Jul 9, 2025

pyomo-autotest removed the AT: RETEST label Jul 9, 2025

Iroy30 and others added 2 commits July 9, 2025 13:15

Merge branch 'main' into add_cuopt_direct_solver_plugin

d9e42ad

Update pyomo/solvers/plugins/solvers/cuopt_direct.py

e2e9159

Co-authored-by: Miranda Mundt <[email protected]>

mrmundt added the AT: PRE-TEST INSPECTED label Jul 9, 2025

pyomo-autotest removed the AT: PRE-TEST INSPECTED label Jul 9, 2025

mrmundt added the AT: RETEST label Jul 9, 2025

pyomo-autotest removed the AT: RETEST label Jul 9, 2025

Iroy30 added 3 commits July 9, 2025 16:47

Merge remote-tracking branch 'origin'

d4a5d07

formatting

61e19bf

pyomo/solvers/plugins/solvers/cuopt_direct.py

432d8c0

Solver name incorrect - change to cuopt_direct

5d8ec53

mrmundt reviewed Jul 10, 2025

View reviewed changes

mrmundt added the AT: PRE-TEST INSPECTED label Jul 10, 2025

pyomo-autotest removed the AT: PRE-TEST INSPECTED label Jul 10, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

add cuopt direct solver #3620

add cuopt direct solver #3620

Iroy30 commented Jun 4, 2025 •

edited by blnicho

Loading

Uh oh!

codecov bot commented Jun 17, 2025 •

edited

Loading

Uh oh!

mrmundt left a comment

Uh oh!

mrmundt commented Jul 1, 2025

Uh oh!

Iroy30 commented Jul 2, 2025

Uh oh!

Uh oh!

Uh oh!

mrmundt Jul 2, 2025

Uh oh!

whart222 commented Jul 8, 2025

Uh oh!

mrmundt commented Jul 8, 2025

Uh oh!

mrmundt commented Jul 8, 2025

Uh oh!

mrmundt commented Jul 8, 2025

Uh oh!

mrmundt Jul 10, 2025

Uh oh!

mrmundt commented Jul 10, 2025

Uh oh!

Iroy30 commented Jul 10, 2025 •

edited

Loading

Uh oh!

mrmundt commented Jul 10, 2025

Uh oh!

Iroy30 commented Jul 16, 2025

Uh oh!

Uh oh!

add cuopt direct solver #3620

Are you sure you want to change the base?

add cuopt direct solver #3620

Conversation

Iroy30 commented Jun 4, 2025 • edited by blnicho Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Fixes #3626

Summary/Motivation:

Changes proposed in this PR:

Legal Acknowledgement

Uh oh!

codecov bot commented Jun 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

mrmundt left a comment

Choose a reason for hiding this comment

Uh oh!

mrmundt commented Jul 1, 2025

Uh oh!

Iroy30 commented Jul 2, 2025

Uh oh!

Uh oh!

Uh oh!

mrmundt Jul 2, 2025

Choose a reason for hiding this comment

Uh oh!

whart222 commented Jul 8, 2025

Uh oh!

mrmundt commented Jul 8, 2025

Uh oh!

mrmundt commented Jul 8, 2025

Uh oh!

mrmundt commented Jul 8, 2025

Uh oh!

mrmundt Jul 10, 2025

Choose a reason for hiding this comment

Uh oh!

mrmundt commented Jul 10, 2025

Uh oh!

Iroy30 commented Jul 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mrmundt commented Jul 10, 2025

Uh oh!

Iroy30 commented Jul 16, 2025

Uh oh!

Uh oh!

Iroy30 commented Jun 4, 2025 •

edited by blnicho

Loading

codecov bot commented Jun 17, 2025 •

edited

Loading

Iroy30 commented Jul 10, 2025 •

edited

Loading