Was looking through the other open PR's related to speeding up the CI process across all of the platforms and I was finding that the vast majority of the time on most platforms is spent in the rust integ test phase and within that phase the vast majority of tests were running in milliseconds and only a few were running in times greater than 10s.

The biggest contributor to these times is the timeout integ tests because most of them rely on a sleep command to run to perform a timeout.

From my first investigation into these times it appears that the reason that cause behind these times being so large was to mitigate race conditions and because the timeout command initially was much slower than the GNU implementation. It appears that now this command is much faster and that when looking at these types of race conditions the difference between the sleep time and the timeout time being a factor of 20x should be more than enough to mitigate these factors. My personal take is that if these tests do begin to show flakiness it could likely be that the tests are doing their job and indicating that theres unexpected timing behavior that should be investigated.