PHPUnit D11 CI job fails since #2885413: Drupal 10 vs 11 have different integer ranges for timestamps

Added some more detail.

The first step is determining which upstream (Drupal core 11.x) change caused these failures, because that's crucial in understanding how we need to evolve XB's codebase.

I think it's due to Timestamp field items are affected by 2038 bug → .
Tried changing timestamp values in tests. works for Next Major version.

If i change the value of minimum of 64bit from -9223372036854775807 to -9223372036854775808 then the tests that were passing initially also fails, but that's the true range of the 64bit.

@utkarsh_33, I got these values from this Drupal Core commit.

https://git.drupalcode.org/project/drupal/-/commit/42c849c8acd8398116d70...

Ok I read the issue summary and it described from -9223372036854775808 so i updated that accordingly.

Also even if we change those values back to 9223372036854775807 FieldForComponentSuggesterTest still fails.So i think we need to figure out the reason for the failure.I tried debugging that but didn't find any.

if we change the back value to -9223372036854775807. All the PHPUnit next major passes. Fails for the current version.

👍

Interesting challenge. This is tricky. 😬

Nice job narrowing this down! Crediting y'all. 😊

This stopped failing!

• #2885413 was committed on Aug 24: #2885413-157: Timestamp field items are affected by 2038 bug →
• Then a follow-up commit happened on Aug 28: #2885413-164: Timestamp field items are affected by 2038 bug → that changed the behavior
• … and again later that day: #2885413-170: Timestamp field items are affected by 2038 bug →
• … and then it was reverted: #2885413-177: Timestamp field items are affected by 2038 bug → .

So, postponing that on the upstream issue landing.

Until #3473822: [later phase] Support Drupal's `timestamp` field type + widget? → lands, this problem won't re-occur. Closing for now.