Skip to content
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

Merged
merged 7 commits into from
Nov 6, 2024

Conversation

akuzm
Copy link
Member

@akuzm akuzm commented Nov 5, 2024

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

Copy link

codecov bot commented Nov 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.56%. Comparing base (59f50f2) to head (f8b6ba7).
Report is 576 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

@svenklemm
Copy link
Member

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.

@akuzm
Copy link
Member Author

akuzm commented Nov 6, 2024

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.

@akuzm akuzm added the force-auto-backport Automatically backport this PR or fix of this issue, even if it's not marked as "bug" label Nov 6, 2024
@akuzm akuzm enabled auto-merge (squash) November 6, 2024 13:20
@akuzm akuzm added this to the TimescaleDB 2.17.2 milestone Nov 6, 2024
Copy link
Contributor

@erimatnor erimatnor left a 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?

@akuzm
Copy link
Member Author

akuzm commented Nov 6, 2024

I assume you grepped for PST8PDT or set timezone to find all instances?

Yep

@akuzm akuzm merged commit 6803dd8 into timescale:main Nov 6, 2024
52 of 53 checks passed
@akuzm akuzm deleted the timezone branch November 6, 2024 16:55
github-actions bot pushed a commit that referenced this pull request Nov 6, 2024
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)
timescale-automation pushed a commit that referenced this pull request Nov 6, 2024
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported-2.17.x force-auto-backport Automatically backport this PR or fix of this issue, even if it's not marked as "bug"
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants