Hello, I spotted this during an Ubuntu rebuild, and the issue came just because the time went ahead of some weeks. Check the log:
./absl/synchronization/internal/kernel_timeout_test.cc:133: Failure
Expected: (absl::TimeFromTimespec(t.MakeClockAbsoluteTimespec(0))) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558739919+00:00
[ FAILED ] KernelTimeout.InfiniteFuture (0 ms)
[ RUN ] KernelTimeout.DefaultConstructor
./absl/synchronization/internal/kernel_timeout_test.cc:155: Failure
Expected: (absl::TimeFromTimespec(t.MakeAbsTimespec())) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558756116+00:00
./absl/synchronization/internal/kernel_timeout_test.cc:158: Failure
Expected: (absl::TimeFromTimespec(t.MakeClockAbsoluteTimespec(0))) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558764469+00:00
[ FAILED ] KernelTimeout.DefaultConstructor (0 ms)
[ RUN ] KernelTimeout.TimeMaxNanos
./absl/synchronization/internal/kernel_timeout_test.cc:180: Failure
Expected: (absl::TimeFromTimespec(t.MakeAbsTimespec())) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558787379+00:00
./absl/synchronization/internal/kernel_timeout_test.cc:183: Failure
Expected: (absl::TimeFromTimespec(t.MakeClockAbsoluteTimespec(0))) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558795373+00:00
[ FAILED ] KernelTimeout.TimeMaxNanos (0 ms)
[ RUN ] KernelTimeout.Never
./absl/synchronization/internal/kernel_timeout_test.cc:205: Failure
Expected: (absl::TimeFromTimespec(t.MakeAbsTimespec())) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558806091+00:00
./absl/synchronization/internal/kernel_timeout_test.cc:208: Failure
Expected: (absl::TimeFromTimespec(t.MakeClockAbsoluteTimespec(0))) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558813909+00:00
[ FAILED ] KernelTimeout.Never (0 ms)
[ RUN ] KernelTimeout.InfinitePast
[ OK ] KernelTimeout.InfinitePast (0 ms)
[ DISABLED ] KernelTimeout.DISABLED_FiniteDurations
[ DISABLED ] KernelTimeout.DISABLED_NegativeDurations
[ RUN ] KernelTimeout.InfiniteDuration
./absl/synchronization/internal/kernel_timeout_test.cc:339: Failure
Expected: (absl::TimeFromTimespec(t.MakeAbsTimespec())) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558830917+00:00
./absl/synchronization/internal/kernel_timeout_test.cc:342: Failure
Expected: (absl::TimeFromTimespec(t.MakeClockAbsoluteTimespec(0))) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558841506+00:00
[ FAILED ] KernelTimeout.InfiniteDuration (0 ms)
[ RUN ] KernelTimeout.DurationMaxNanos
./absl/synchronization/internal/kernel_timeout_test.cc:364: Failure
Expected: (absl::TimeFromTimespec(t.MakeAbsTimespec())) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558854004+00:00
./absl/synchronization/internal/kernel_timeout_test.cc:367: Failure
Expected: (absl::TimeFromTimespec(t.MakeClockAbsoluteTimespec(0))) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.558862107+00:00
[ FAILED ] KernelTimeout.DurationMaxNanos (0 ms)
[ RUN ] KernelTimeout.OverflowNanos
./absl/synchronization/internal/kernel_timeout_test.cc:389: Failure
Expected: (absl::TimeFromTimespec(t.MakeAbsTimespec())) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.55887547+00:00
./absl/synchronization/internal/kernel_timeout_test.cc:392: Failure
Expected: (absl::TimeFromTimespec(t.MakeClockAbsoluteTimespec(0))) > (absl::Now() + absl::Hours(100000)), actual: 2038-01-19T03:14:07.999999999+00:00 vs 2038-01-27T03:31:10.55888362+00:00
[ FAILED ] KernelTimeout.OverflowNanos (0 ms)
[----------] 8 tests from KernelTimeout (0 ms total)
[----------] Global test environment tear-down
Of course i386 isn't going after 2038 so the test must be ignored on 32bit time_t
diff -Nru abseil-20260526.0/debian/changelog abseil-20260526.0/debian/changelog
--- abseil-20260526.0/debian/changelog 2026-07-19 13:18:20.000000000 +0200
+++ abseil-20260526.0/debian/changelog 2026-08-31 13:18:21.000000000 +0200
@@ -1,3 +1,9 @@
+abseil (20260526.0-2ubuntu1) stonking; urgency=medium
+
+ * Fix and ignore time-bomb test on i386, going after 2038
+
+ -- Gianfranco Costamagna <locutusofborg@debian.org> Mon, 31 Aug 2026 13:18:21 +0200
+
abseil (20260526.0-2) unstable; urgency=medium
* Don't use <bmi2intrin.h> directly; include <immintrin.h>.
diff -Nru abseil-20260526.0/debian/rules abseil-20260526.0/debian/rules
--- abseil-20260526.0/debian/rules 2026-07-14 00:24:45.000000000 +0200
+++ abseil-20260526.0/debian/rules 2026-08-31 10:40:30.000000000 +0200
@@ -67,6 +67,9 @@
else ifneq (,$(filter x32,$(DEB_HOST_ARCH)))
TEST_EXCLUSIONS += absl_hash_instantiated_test
+
+else ifneq (,$(filter i386,$(DEB_HOST_ARCH)))
+ TEST_EXCLUSIONS += absl_kernel_timeout_internal_test
endif
ifneq (,$(TEST_EXCLUSIONS))
This might be a good patch, please check and commit, I would prefer to not commit by myself
G.