-
Notifications
You must be signed in to change notification settings - Fork 887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use America/Los_Angeles in tests instead of PST8PDT #7416
Conversation
Follow the PG upstream changes in light of the upcoming timezone updates. This should fix our regression tests on latest PG snapshots. postgres/postgres@2b94ee5
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7416 +/- ##
==========================================
+ Coverage 80.06% 82.56% +2.49%
==========================================
Files 190 229 +39
Lines 37181 42740 +5559
Branches 9450 10739 +1289
==========================================
+ Hits 29770 35287 +5517
- Misses 2997 3173 +176
+ Partials 4414 4280 -134 ☔ View full report in Codecov by Sentry. |
Setting the timezone in all the cagg files was a workaround for a problem with cagg refresh which has been fixed so we can probably remove the explicit timezone from the cagg test files again. |
Removed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume you grepped for PST8PDT
or set timezone
to find all instances?
Yep |
Follow the PG upstream changes in light of the upcoming timezone updates. This should fix our regression tests on latest PG snapshots. postgres/postgres@2b94ee5 (cherry picked from commit 6803dd8)
Follow the PG upstream changes in light of the upcoming timezone updates. This should fix our regression tests on latest PG snapshots. postgres/postgres@2b94ee5 (cherry picked from commit 6803dd8)
Follow the PG upstream changes in light of the upcoming timezone updates. This should fix our regression tests on latest PG snapshots.
postgres/postgres@2b94ee5
Example of the failing test on main: https://github.com/timescale/timescaledb/actions/runs/11666186287/job/32480586544
Disable-check: force-changelog-file
test