From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Joe Conway <mail(at)joeconway(dot)com>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Christophe Pettus <christophe(dot)pettus(at)pgexperts(dot)com> |
Subject: | Re: CI, macports, darwin version problems |
Date: | 2024-07-23 10:31:07 |
Message-ID: | CA+hUKGJSd8DTW=i1kEmJq-r0AGubfySNVK=+EZnf_Tq9pX7tDw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 23, 2024 at 7:37 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> [2] https://cirrus-ci.com/task/5190473306865664
"Error: “disk.img” couldn’t be copied to
“3FA983DD-3078-4B28-A969-BCF86F8C9585” because there isn’t enough
space."
Could it be copying the whole image every time, in some way that would
get copy-on-write on the same file system, but having to copy
physically here? That is, instead of using some kind of chain of
overlay disk image files as seen elsewhere, is this Tart thing relying
on file system COW for that? Perhaps that is happening here[1] but I
don't immediately know how to find out where that Swift standard
library call turns into system calls...
[1] https://github.com/cirruslabs/tart/blob/main/Sources/tart/VMDirectory.swift#L119
From | Date | Subject | |
---|---|---|---|
Next Message | Nazir Bilal Yavuz | 2024-07-23 10:32:17 | Re: PG_TEST_EXTRA and meson |
Previous Message | Melih Mutlu | 2024-07-23 10:14:09 | Re: Parent/child context relation in pg_get_backend_memory_contexts() |