zatrazz added a comment. In D72449#1812130 <https://reviews.llvm.org/D72449#1812130>, @arichardson wrote:
> I was careful in the test to use `TZ=UTC` for all commands printing dates and > it works fine for me in UTC+1 and in the UK which is currently UTC. Does the > bot in question ignore the TZ variable? The issue is setting TZ=UTC still might use internal database with UTC offsets. For instance, on the buildbot that accused the regression, setting TZ=UTC make it use the tz database /usr/share/zoneinfo/UTC. At least on Linux with glibc one way to actually use UTC without transit changes are to set TZ=":", it won't try to access either the default '/etc/localtime'. However, I am not sure how portable it is and it might be in fact an glibc issue (https://sourceware.org/bugzilla/show_bug.cgi?id=24004). CHANGES SINCE LAST ACTION https://reviews.llvm.org/D72449/new/ https://reviews.llvm.org/D72449 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
