Check sanity of tests

[JurgenZach-NOAA]

[Short description explaining the high-level reason for the pull request]

Additions

-

Removals

-

Changes

-

Testing

1.

Screenshots

Notes

-

Todos

-

Checklist

• [ ] PR has an informative and human-readable title
• [ ] Changes are limited to a single goal (no scope creep)
• [ ] Code can be automatically merged (no conflicts)
• [ ] Code follows project standards (link if applicable)
• [ ] Passes all existing automated tests
• [ ] Any change in functionality is tested
• [ ] New functions are documented (with a description, list of inputs, and expected output)
• [ ] Placeholder code is flagged / future todos are captured in comments
• [ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
• [ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• [ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist

Target Environment support

• [ ] Windows
• [ ] Linux
• [ ] Browser

Accessibility

• [ ] Keyboard friendly
• [ ] Screen reader friendly

Other

• [ ] Is useable without CSS
• [ ] Is useable without JS
• [ ] Flexible from small to large screens
• [ ] No linting errors or warnings
• [ ] JavaScript tests are passing

[JurgenZach-NOAA]

There is an issue with the current master branch of t-route: when I'm trying to commit a fully rebased/up to date version with a dummy change, the builds fail. Please verify ASAP!

[JurgenZach-NOAA]

This is a temporary patch - the Python application/builds in git failed after pandas was updated to 2.2.1. Limited to up to 2.2.0 in requirements.txt

[jameshalgren]

@JoshCu