Decreased time limit for SNOPT informs test

[sseraj]

Purpose

Our Mac runner is fast and sometimes does not run into the time limit for the SNOPT test where we want the optimization to time out. I decreased the time limit to hopefully address this.

Expected time until merged

2-3 days

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

The test still works on my workstation, but I didn't test this on the Mac runner.

Checklist

• I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• I have run unit and regression tests which pass locally with my changes
• I have added new tests that prove my fix is effective or that my feature works
• I have added necessary documentation

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8d43112) 73.35% compared to head (9ff2f03) 73.35%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #376   +/-   ##
=======================================
  Coverage   73.35%   73.35%           
=======================================
  Files          22       22           
  Lines        3318     3318           
=======================================
  Hits         2434     2434           
  Misses        884      884           

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

[lamkina]

Simple enough solution since we are only testing if it produces the correct informs from SNOPT. LGTM.