Read the o3-deep-research clocks from the committed feed in the checker tests - #102
Merged
Merged
Conversation
…er tests The regenerate step of feed-refresh runs npm test against the freshly regenerated feeds. Two checker assertions pinned the Azure shutdown (2026-12-26) and the publisher shutdown (2026-07-23) of o3-deep-research-2025-06-26 as literals, so the 2026-09-21 dispatch (run 35614410962) failed as soon as Azure moved that row to 2026-11-19 and legacy. The check step had already passed with the parser fixes from #101. The tests now read both dates from feeds/openai.json and keep the property they exist to prove: under --via azure-ai-foundry the finding carries the Azure clock, without --via it carries the publisher clock, and the Azure clock is the later of the two. Verified against the committed feeds and against a locally regenerated feed that carries the moved Azure date.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
feed-refreshdispatch after #101 (run 35614410962) got past the check step and then failed innpm testinside the regenerate step. Two checker assertions pinned the Azure shutdown (2026-12-26) and the publisher shutdown (2026-07-23) ofo3-deep-research-2025-06-26as literals. Azure moved that row to2026-11-19andlegacy, so the regenerated feed no longer matched the pins.The tests now read both dates from
feeds/openai.jsonand keep the property they exist to prove: under--via azure-ai-foundrythe finding carries the Azure clock, without--viait carries the publisher clock, and the Azure clock is the later of the two.Verification
node test/run.mjson the committed feedsnode test/run.mjson locally regenerated feeds (Azure row at 2026-11-19, legacy)npm testTest-only change. After merge,
feed-refreshgets dispatched on main again to open the feed PR and close #100.🤖 Generated with Claude Code