On 9/30/23 01:57, Tom Lane wrote:
> Thomas Munro writes:
>> Does the image lack a /etc/localtime file/link, but perhaps one of you
>> did something to create it?
>
> Hah! I thought it had to be some sort of locale effect, but I failed
> to think of that as a contributor :-(. My installation doe
Thomas Munro writes:
> This came up with the CI image:
> https://www.postgresql.org/message-id/flat/20230731191510.pebqeiuo2sbmlcfh%40awork3.anarazel.de
BTW, after re-reading that thread, I think the significant
difference is that these FreeBSD images don't force you to
select a timezone during s
Thomas Munro writes:
> Does the image lack a /etc/localtime file/link, but perhaps one of you
> did something to create it?
Hah! I thought it had to be some sort of locale effect, but I failed
to think of that as a contributor :-(. My installation does have
/etc/localtime, and removing it dupli
Does the image lack a /etc/localtime file/link, but perhaps one of you
did something to create it?
This came up with the CI image:
https://www.postgresql.org/message-id/flat/20230731191510.pebqeiuo2sbmlcfh%40awork3.anarazel.de
Also mentioned at: https://wiki.tcl-lang.org/page/clock+scan
Tomas Vondra writes:
> On 9/27/23 15:38, Tom Lane wrote:
>> Tomas Vondra writes:
>>> Hmm, yeah. Which FreeBSD image did you install? armv7 or aarch64?
>> https://download.freebsd.org/releases/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-BETA3-arm64-aarch64-RPI.img.xz
> Thanks, that's the image I'
On 9/27/23 15:38, Tom Lane wrote:
> Tomas Vondra writes:
>> On 9/26/23 23:50, Tom Lane wrote:
>>> Huh. I'm baffled as to what's up there. Is it possible that this is
>>> actually a hardware-based difference? I didn't think there was much
>>> difference between Pi 3B and Pi 4, but we're running
Tomas Vondra writes:
> On 9/26/23 23:50, Tom Lane wrote:
>> Huh. I'm baffled as to what's up there. Is it possible that this is
>> actually a hardware-based difference? I didn't think there was much
>> difference between Pi 3B and Pi 4, but we're running out of other
>> explanations.
> Hmm, ye
On 9/26/23 23:50, Tom Lane wrote:
> Tomas Vondra writes:
>> Hmmm, I got to install BETA2 yesterday, but I still se the tcl failure:
>
> Huh. I'm baffled as to what's up there. Is it possible that this is
> actually a hardware-based difference? I didn't think there was much
> difference betwe
Tomas Vondra writes:
> Hmmm, I got to install BETA2 yesterday, but I still se the tcl failure:
Huh. I'm baffled as to what's up there. Is it possible that this is
actually a hardware-based difference? I didn't think there was much
difference between Pi 3B and Pi 4, but we're running out of oth
On 9/20/23 20:09, Tomas Vondra wrote:
> On 9/20/23 19:59, Tomas Vondra wrote:
>>
>>
>> On 9/20/23 01:24, Tom Lane wrote:
>>> Tomas Vondra writes:
bsd@freebsd:~ $ tclsh8.6
% clock scan "1/26/2010"
time value too large/small to represent
>>>
>>> In hopes of replicating this, I trie
On 9/20/23 19:59, Tomas Vondra wrote:
>
>
> On 9/20/23 01:24, Tom Lane wrote:
>> Tomas Vondra writes:
>>> bsd@freebsd:~ $ tclsh8.6
>>> % clock scan "1/26/2010"
>>> time value too large/small to represent
>>
>> In hopes of replicating this, I tried installing FreeBSD 14-BETA2
>> aarch64 on my Pi
On 9/20/23 01:24, Tom Lane wrote:
> Tomas Vondra writes:
>> bsd@freebsd:~ $ tclsh8.6
>> % clock scan "1/26/2010"
>> time value too large/small to represent
>
> In hopes of replicating this, I tried installing FreeBSD 14-BETA2
> aarch64 on my Pi 3B. This test case works fine:
>
> $ tclsh8.6
>
Tomas Vondra writes:
> bsd@freebsd:~ $ tclsh8.6
> % clock scan "1/26/2010"
> time value too large/small to represent
In hopes of replicating this, I tried installing FreeBSD 14-BETA2
aarch64 on my Pi 3B. This test case works fine:
$ tclsh8.6
% clock scan "1/26/2010"
1264482000
$ tclsh8.7
% clo
On 9/19/23 18:45, Tom Lane wrote:
> Tomas Vondra writes:
>> I have no experience with tcl, but I tried this in the two tclsh
>> versions installed no the system (8.6 and 8.7):
>
>> bsd@freebsd:~ $ tclsh8.7
>> % clock scan "1/26/2010"
>> time value too large/small to represent
>
>> bsd@freebsd
Tomas Vondra writes:
> I have no experience with tcl, but I tried this in the two tclsh
> versions installed no the system (8.6 and 8.7):
> bsd@freebsd:~ $ tclsh8.7
> % clock scan "1/26/2010"
> time value too large/small to represent
> bsd@freebsd:~ $ tclsh8.6
> % clock scan "1/26/2010"
> time v
On 9/18/23 20:52, Tom Lane wrote:
> Tomas Vondra writes:
>> it seems dikkop is unhappy again, this time because of some OpenSSL
>> stuff. I'm not sure it's our problem - it might be issues with the other
>> packages, or maybe something FreeBSD specific, not sure.
>> ...
>> Both 11 and 12 failed
On 9/19/23 04:25, Thomas Munro wrote:
> On Tue, Sep 19, 2023 at 2:04 PM Michael Paquier wrote:
>> On Mon, Sep 18, 2023 at 03:11:27PM +0200, Tomas Vondra wrote:
>>> Both 11 and 12 failed with a weird openssl segfaults in plpython tests,
>>> see [2] and [3]. And 13 is stuck in some openssl stuff in
On Tue, Sep 19, 2023 at 2:04 PM Michael Paquier wrote:
> On Mon, Sep 18, 2023 at 03:11:27PM +0200, Tomas Vondra wrote:
> > Both 11 and 12 failed with a weird openssl segfaults in plpython tests,
> > see [2] and [3]. And 13 is stuck in some openssl stuff in plpython
> > tests, with 100% CPU usage (
On Mon, Sep 18, 2023 at 03:11:27PM +0200, Tomas Vondra wrote:
> Both 11 and 12 failed with a weird openssl segfaults in plpython tests,
> see [2] and [3]. And 13 is stuck in some openssl stuff in plpython
> tests, with 100% CPU usage (for ~30h now):
>
> #0 0x850e86c0 in OPENSSL_sk_insert
IDK, but I tried installing tcl87 as you showed in packages.txt, and
REL_11_STABLE said:
checking for tclsh... no
checking for tcl... no
checking for tclsh8.6... no
checking for tclsh86... no
checking for tclsh8.5... no
checking for tclsh85... no
checking for tclsh8.4... no
checking for tclsh84...
Tomas Vondra writes:
> it seems dikkop is unhappy again, this time because of some OpenSSL
> stuff. I'm not sure it's our problem - it might be issues with the other
> packages, or maybe something FreeBSD specific, not sure.
> ...
> Both 11 and 12 failed with a weird openssl segfaults in plpython
Hi,
it seems dikkop is unhappy again, this time because of some OpenSSL
stuff. I'm not sure it's our problem - it might be issues with the other
packages, or maybe something FreeBSD specific, not sure.
We did some investigation of an unrelated issue on dikkop about a month
ago [1], so it wasn't d
22 matches
Mail list logo
