Issue Summary

The s_evergreen script is stalling indefinitely with no input or output for multiple users when run on a dev VM. The issue appears to be related to a recent change (WT-17682) that deprecated static API keys, causing the script to wait for browser authentication. However, this authentication prompt is hidden, leaving users unaware of what is happening.

Context

• Multiple users report that s_evergreen hangs with no feedback, sometimes for several minutes or longer.
• The script now requires browser authentication due to API key deprecation, but this requirement is not surfaced to the user.
• On dev VMs, the authentication flow is unclear and potentially broken.
• The output of s_evergreen is redirected into temp files by s_all, which may further obscure any prompts or errors, causing the script to appear stalled.
• Reference to recent change: WT-17682
• Related discussion: [https://mongodb.enterprise.slack.com/archives/CUDFJEN8J/p1781565846013649|clang-format thread]

Proposed Solution

• Improve s_evergreen to provide clear user feedback when authentication is required, especially on dev VMs.
• Ensure that authentication prompts are visible and not swallowed by temp file redirection.
• Document the new authentication flow and provide guidance for running s_evergreen on dev VMs.
• Investigate and fix the script's output handling to prevent indefinite stalling.

Original Slack thread: https://mongodb.slack.com/archives/C0520RCK0C9/p1781581854408169
This ticket was generated by AI from a Slack thread.