test: explicitly use UTC timezone in tests - #1343

no API key found — this repo is configured to use deepseek/deepseek-v4-pro, which needs DEEPSEEK_API_KEY, but the runner has no key for it.

To fix: add the key as a GitHub Actions secret (referenced from your workflow's env: block) or as a Pullfrog secret in the console — or switch this repo to a different model (free models need no key).

Open repo secrets → · Configure model → · Setup docs → · Ask in Discord →

  ^{｜ Rerun failed job ➔ ｜ View workflow run ｜ via Pullfrog ｜ Using DeepSeek Pro (free via Pullfrog for OSS) ｜ 𝕏}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

This PR was auto-closed. Only contributors approved with lgtm can open PRs. Open an issue first.

Maintainers review auto-closed issues and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md may not be reopened or receive a reply.

If a maintainer replies lgtmi, your future issues will stay open. If a maintainer replies lgtm, your future issues and PRs will stay open.

See CONTRIBUTING.md.

@coderabbitai review it

#!/bin/bash
# Get the PR diff
gh pr view 1343 --repo ccusage/ccusage --json title,body,files,additions,deletions,commits
echo "---DIFF---"
gh pr diff 1343 --repo ccusage/ccusage

#!/bin/bash
# Check if snapshot files exist and whether they were changed in this PR
fd -e snap . rust/ | head -30
echo "---"
# Check git diff for snapshot files
gh pr diff 1343 --repo ccusage/ccusage -- "*.snap" 2>/dev/null | head -100

#!/bin/bash
# Check the relevant snapshot files
cat rust/crates/ccusage/src/adapter/opencode/snapshots/ccusage__adapter__opencode__parser__tests__snapshots_message_to_entry_variants_and_model_candidates.snap

echo "=== main.rs codex snapshot ==="
# Find snapshot for builds_codex_daily_json_report
fd -e snap . rust/crates/ccusage/src/ | xargs grep -l "builds_codex" 2>/dev/null
# Check the parse_tz function
rg -n "fn parse_tz" rust/

#!/bin/bash
# Check parse_tz implementation
sed -n '215,240p' rust/crates/ccusage/src/date_utils.rs

echo "==="
# Check the builds_codex_daily_json_report test in main.rs
rg -n "builds_codex_daily_json_report" rust/ -A 50 | head -60

@ryoppippi: The fix is correct and well-implemented. Here's a detailed review:

Review Summary ✅

The root cause is clear: format_date_tz falls back to JiffTimeZone::system() when no timezone is provided. In PDT (UTC−7), the test timestamp "2026-01-02T00:00:01.000Z" maps to the previous day (2026-01-01), causing assertions like report["daily"][0]["date"] == "2026-01-02" to fail.

rust/crates/ccusage/src/adapter/opencode/parser.rs

let tz = crate::parse_tz(Some("UTC"));

✅ Parsing the timezone once and reusing tz.as_ref() for both message_value_to_entry calls is clean and efficient.
✅ tz.as_ref() is the correct pattern to convert Option<JiffTimeZone> → Option<&JiffTimeZone> without moving.

rust/crates/ccusage/src/main.rs

Some("UTC"),  // was: None

✅ Passing Some("UTC") directly matches the Option<&str> parameter type of report_json.
✅ The test snapshot for this is assertion-based (not file-based), so no snapshot update is needed.

Minor observation (out of scope for this PR)

The prices_codex_versioned_models_like_typescript_adapter test immediately below (line 568) also uses a midnight-UTC timestamp ("2026-01-02T00:00:01.000Z"). If it asserts on a date field and passes None for timezone, it may have the same latent issue. Worth checking in a follow-up.

Overall: the fix is minimal, correct, and directly addresses the stated problem. The changes are well-scoped with no unnecessary modifications.

[approve]

Historical audit: this pull request was auto-closed by the legacy contributor gate. That closure did not assess technical importance.

Audit result: resolved. A later merged change or the current main implementation covers this request. This PR is kept for history and does not need to be revived.