supabase / storage / 38543049882

86%

push

github

test: avoid timestamp precision loss in archive ordering assertion (#1505)

## What kind of change does this PR introduce?

Test flake fix

## What is the current behavior?

The test converts pg timestamps to js dates, discarding microseconds.
Two correctly ordered writes within the same millisecond can therefore
compare equal.

## What is the new behavior?

Compare timestamps directly in pg to preserve full precision.

## Additional context

Related to
https://github.com/supabase/storage/actions/runs/38537002214/job/115762588654

7624 of 9460 branches covered (80.59%)

Branch coverage included in aggregate %.

13300 of 15055 relevant lines covered (88.34%)

855.32 hits per line