CI: bump build and test timeouts to 60 minutes

[dconnolly]

Motivation

We've started running the CI workflow on #main post-merge again. Several job steps are running into timeouts on #main. We're also fiddling with the cargo env vars to avoid running out of space on the GitHub runners.

Solution

To give some margins to trying all these tweaks, this change bumps the timeouts on the build and test jobs/steps to one hour.

Review

Anyone can review, but @oxarbitrage @teor2345 . Medium urgent as we have timeouts on CI runs on #main.

Related Issues

#1756

Follow Up Work

[oxarbitrage]

Hmm, i think the test builds will almost always need more time as they build everything and later run the tests. I will say 60 minutes there is fine. In the build only job we can go with 50 minutes and in the without features 45 mins ?

We can increase this values if needed but some difference between the timeouts could help us spot certain rare problems.

[dconnolly]

Hmm, i think the test builds will almost always need more time as they build everything and later run the tests. I will say 60 minutes there is fine. In the build only job we can go with 50 minutes and in the without features 45 mins ?

We can increase this values if needed but some difference between the timeouts could help us spot certain rare problems.

Since we're experimenting with flags, and to have some more consistent expectations of how long jobs take, I rounded up to 60mins for now, but am amenable to changing them again later. I would rather the top margin be large with room to experiment rather than too low. The GitHub job max is like 6 hours or something.

[oxarbitrage]

Ok, fair, approving.