Fix integration tests

[kadero]

resolves #3952

Description

This PR aims to handle properly the datetime column in the integration test TestSnapshotHardDelete.test__postgres__snapshot_hard_delete.

The timestamp we extract from PG is in UTC and offset naive. We just need to make it offset aware to enable the comparaison.
astimezone(pytz.UTC) to .replace(tzinfo=pytz.UTC)

The fix was tested locally by launching the test under multiple Timezone:

# EDT
sudo timedatectl set-timezone America/New_York && timedatectl && python -m pytest -m profile_postgres test/integration/004_simple_snapshot_test/test_simple_snapshot.py::TestSnapshotHardDelete::test__postgres__snapshot_hard_delete

# PDT
sudo timedatectl set-timezone America/Los_Angeles && timedatectl && python -m pytest -m profile_postgres test/integration/004_simple_snapshot_test/test_simple_snapshot.py::TestSnapshotHardDelete::test__postgres__snapshot_hard_delete

# CEST
sudo timedatectl set-timezone Europe/Paris && timedatectl && python -m pytest -m profile_postgres test/integration/004_simple_snapshot_test/test_simple_snapshot.py::TestSnapshotHardDelete::test__postgres__snapshot_hard_delete

# NZDT
sudo timedatectl set-timezone Pacific/Auckland && timedatectl && python -m pytest -m profile_postgres test/integration/004_simple_snapshot_test/test_simple_snapshot.py::TestSnapshotHardDelete::test__postgres__snapshot_hard_delete

# IST
sudo timedatectl set-timezone Asia/Kolkata && timedatectl && python -m pytest -m profile_postgres test/integration/004_simple_snapshot_test/test_simple_snapshot.py::TestSnapshotHardDelete::test__postgres__snapshot_hard_delete

Checklist

• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

[cla-bot]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, don't hesitate to ping @drewbanin.

CLA has not been signed by users: @kadero

[kadero]

CLA signed ✔️

[jtcohen6]

Closing and reopening to trigger adapter tests

[jtcohen6]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[jtcohen6]

@kadero Thanks for this! There must have been something else going on in the previous issue (perhaps a non-UTC timestamp setting in Postgres?).

Since this is just a change to the integration test, this doesn't require a changelog entry, but if you're up for it, I'd still encourage you to add yourself to the list of Contributors there.

[kadero]

@kadero Thanks for this! There must have been something else going on in the previous issue (perhaps a non-UTC timestamp setting in Postgres?).

Yes probably, I not 100% sure of the root cause in the previous issue 😕

Since this is just a change to the integration test, this doesn't require a changelog entry, but if you're up for it, I'd still encourage you to add yourself to the list of Contributors there.

Done under ## dbt 0.21.0 (Release TBD) ✔️

Many thanks for your assist @jtcohen6 🙏

[jtcohen6]

Thanks for this @kadero! I just bumped up your contributor note to be under 1.0.0 :)