[MINOR] Disable org.apache.hudi.TestHoodieSparkSqlWriter#testInsertDatasetWithTimelineTimezoneUTC

[jonvex]

Change Logs

This test was causing following tests to get stuck. Something to do with the lock provider maybe. After investigating for a couple hours I wasn't able to discover anything. Created HUDI-7275 to track.

Impact

Possibly the cause of some CI OOMs

Risk level (write none, low medium or high below)

none

Documentation Update

N/A

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[hudi-bot]

CI report:

• 8c34c35 Azure: CANCELED

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[geserdugarov]

@jonvex @nsivabalan
I also saw this problem, but couldn't figure out how to quickly fix it.

The problem is that we have static AtomicReference lastInstantTime in HoodieInstantTimeGenerator.

If this test testInsertDatasetWithTimelineTimezoneUTC is run the first, then it would be passed ok. Otherwise, if any other test in the test class would initialize HoodieInstantTimeGenerator, then the value for lastInstantTime would stay in the heap and you couldn't do anything to clear it, for instance, in @AfterEach processing.