Moved SNOPT time limit test to larger problem

[sseraj]

Purpose

The HS071 case runs too quickly to reliably test the SNOPT time limit option. I moved the test to the TP109 instead and decreased the time.

Expected time until merged

ASAP because the buildbot is failing

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

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

[marcomangano]

Nice, I had no problems when testing locally and I wanted to be consistent with other informs tests, but this is safer. Thanks!

[codecov]

Codecov Report

Merging #334 (e8a8cd2) into main (aa83d79) will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #334      +/-   ##
==========================================
+ Coverage   84.25%   84.34%   +0.08%     
==========================================
  Files          22       22              
  Lines        3347     3347              
==========================================
+ Hits         2820     2823       +3     
+ Misses        527      524       -3     

see 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more