Summary: | sys-libs/uid_wrapper-1.2.9 fails tests (MUSL) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Gentoo's SAMBA Team <samba> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | matoro_gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=933018 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
1-LastTest.log |
Description
Agostino Sarubbo
2022-10-08 10:26:36 UTC
Created attachment 822811 [details]
build.log
build log and emerge --info
Created attachment 822814 [details]
1-LastTest.log
1-LastTest.log
Error(s) that match a know pattern: 15 - test_syscall (Failed) Somehow timezone-related, but the usual good old TZ=UTC has no effect. This seems to be somewhat unpredictable, on amd64 it is MUSL-specific, but it also appears under other platforms with glibc. For glibc, unaffected platforms: arm64, ppc64, loong For glibc, affected platforms: ia64, sparc, alpha, mips, hppa, riscv This note in the man page for gettimeofday(2) might be relevant: VERSIONS C library/kernel differences On some architectures, an implementation of gettimeofday() is provided in the vdso(7). The kernel accepts NULL for both tv and tz. The timezone argument is ignored by glibc and musl, and not passed to/from the kernel. Android’s bionic passes the timezone argument to/from the kernel, but Android does not update the kernel timezone based on the device timezone in Settings, so the kernel’s timezone is typically UTC. I tried looking for a pattern matching this in vdso(7), but did not find one. Also, given that the issue is present with MUSL under amd64, it's likely not a kernel issue. |