[SERVER-81595] resmoke incorrectly reports datetimes using 'Z' suffix even when local timepoint is not from UTC Created: 29/Sep/23  Updated: 25/Jan/24

Status: Backlog
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: [DO NOT ASSIGN] Backlog - DevProd Correctness
Resolution: Unresolved Votes: 0
Labels: FY2025Q1, resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-54723 Shorten resmoke log prefixes Closed
Assigned Teams:
Correctness
Operating System: ALL
Participants:

 Description   

The changes from 8022d88 as part of SERVER-54723 removed the ability for resmoke to report timepoints as relative offsets from UTC when the host machine isn't configured to have its timezone set to Etc/UTC. Instead resmoke always reports the local timepoint with a 'Z' suffix implying Zulu time incorrectly. This behavior is confusing because not all Evergreen hosts have their timezone set to Etc/UTC and leads to situations where the hour numbers in the datetime don't match up resmoke in the task logs and the MongoDB Server processes.

Steps to reproduce

$ sudo timedatectl set-timezone Etc/UTC
$ python buildscripts/resmoke.py run --suite core -n | grep 'Tests that would be run in suite'
[executor] 20:34:58.318Z Tests that would be run in suite core
$ sudo timedatectl set-timezone America/New_York
$ python buildscripts/resmoke.py run --suite core -n | grep 'Tests that would be run in suite'
[executor] 16:35:13.482Z Tests that would be run in suite core


Generated at Thu Feb 08 06:46:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.