In BF-45929, we saw that a primary detected that it had stalled due to this check after the nemesis agent set the clock forward on the primary to simulate clock skew. The default for paliStallThresholdMillis is 120000. Meanwhile, nemesis can set the clock forward up to 256 seconds.

To eliminate flakiness in the environment, set the paliStallThresholdMillis to above the value of nemesis' clock skew value.

Note: This means we lose test coverage for the case of clock skew in production happening in production > paliStallThresholdMillis. However, my personal viewpoint is that this is not a particularly valuable case to test right now, and we should focus on stability. We can revisit this case at a later point if necessary.