Skip to content

et stamp is causing tree failures due to flaky date-time #172318

@matanlurey

Description

@matanlurey

Example failure:

test root: Directory: '/b/s/w/ir/x/t/engine_tool_testOCMGCH'
00:01 �[32m+214�[0m�[31m -2�[0m: test/entry_point_test.dart: The entry points under bin/ work�[0m
00:01 �[32m+214�[0m�[31m -2�[0m: test/commands/stamp_command_test.dart: creates stamp writes to engine_stamp.json �[1m�[31m[E]�[0m�[0m
  Expected: '{"build_date":"2025-06-27T12:30:00.000","build_time_ms":1751052600000,"git_revision":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","git_revision_date":"2025-06-27T17:11:53-07:00","content_hash":"1111111111111111111111111111111111111111"}'
    Actual: '{"build_date":"2025-06-27T12:30:00.000","build_time_ms":1751027400000,"git_revision":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","git_revision_date":"2025-06-27T17:11:53-07:00","content_hash":"1111111111111111111111111111111111111111"}'
     Which: is different.
            Expected: ... _ms":1751052600000," ...
              Actual: ... _ms":1751027400000," ...
                                    ^
             Differ at offset 61
  
  package:matcher                              expect
  test/commands/stamp_command_test.dart 150:7  main.<fn>.<fn>

Metadata

Metadata

Assignees

Labels

P0Critical issues such as a build break or regressionc: flakeTests that sometimes, but not always, incorrectly passfyi-infraFor the attention of Infrastructure teamteam-engineOwned by Engine team

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions