-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Compilation: write CACHEDIR.TAG #24121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I can't tell whether the
|
It's probably related, and likely coming from |
Thanks for the hint, that helps a bit. Sadly, I can't seem to repro locally (the compilation goes past the failed CI steps), my cmake invocation is something along the lines of At the very least, I'll push a commit later to make these "unimplemented" a little more helpful (hopefully it's not part of the cached build?). |
In ziglang#24121 the CI unhelpfully fails with: unimplemented Aborted Change the panic function to a macro to report caller name and line: wasi_snapshot_preview1_fd_write:767: test
I've mucked around a bit: if i check out ziglang/zig-bootstrap@7493858, apply ziglang/zig-bootstrap@773262e, build with the host version:
It goes further than the CI but fails when linking:
Is it because I'm using the host version? I'm still waiting on So, to be honest I'm not quite sure what I'm chasing since this step seems to build for me? Some guidance would be appreciated if it's an issue on my side and not the CI's. In the meantime I've pushed an additional commit so I can actually tell which function isn't implemented (so I can at least cross reference against git history). |
In ziglang#24121 the CI unhelpfully fails with: unimplemented Aborted Change the panic function to a macro to report caller name and line: wasi_snapshot_preview1_fd_write:767: test
…_open This occurred in ziglang#24121 because the global and local CACHEDIR.TAG are both /cache/CACHEDIR.TAG.
7b033ec
to
0736ebf
Compare
Okay, my bad, I somehow missed the |
…_open This occurred in ziglang#24121 because the global and local CACHEDIR.TAG are both /cache/CACHEDIR.TAG.
691639b
to
27f4b7c
Compare
…_open This occurred in ziglang#24121 because the global and local CACHEDIR.TAG are both /cache/CACHEDIR.TAG.
@@ -399,6 +399,49 @@ static void DirEntry_unlink(uint32_t de) { | |||
des[de].host_path = NULL; | |||
} | |||
|
|||
static enum wasi_errno FileDescriptor_open(uint32_t de, uint32_t oflags, uint64_t fs_rights_base, uint32_t fdflags, FILE **stream) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's kind of hard to review the logic change here when it's combined with a refactor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack, I've separated the refactor commit from the logic change. It feels a bit artificial because it's a one line change that has no reason to be here once the new & existing entry flows are unified, but if it helps the review.
I dusted off an old macOS but I can't repro the CI failure (I hope I'm not being dense again):
|
This occurred in ziglang#24121 because the global and local CACHEDIR.TAG are both /cache/CACHEDIR.TAG.
27f4b7c
to
bddd42d
Compare
This occurred in ziglang#24121 because the global and local CACHEDIR.TAG are both /cache/CACHEDIR.TAG.
bddd42d
to
e6c6d85
Compare
In ziglang#24121 the CI unhelpfully fails with: unimplemented Aborted Change the panic function to a macro to report caller name and line: wasi_snapshot_preview1_fd_write:767: test
So that opening an existing or new file can share the same code path (but opening an existing file isn't yet used elsewhere so this commit should behave the same). Timestamping is left to DirEntry_create, I believe it behaves the same.
This occurred in ziglang#24121 because the global and local CACHEDIR.TAG are both /cache/CACHEDIR.TAG.
Write a CACHEDIR.TAG file in the global and local cache directories. See ziglang#8210 for context and ziglang#14875 for a previous attempt. Co-authored-by: Manlio Perillo <[email protected]>
Thanks for rerunning the CI. It passed (but I can't explain it). |
e6c6d85
to
698d21e
Compare
This was previously attempted in #14875 but it was asked to make the file creation an asynchronous task like the others in
performAllTheWork
.For context, see #8210. In my case it's motivated by the fact that my little project's
.zig-cache
is already 40+GB (I haven't checked why) and I'd like the backup utility to avoid backing up the intermediate artifacts. In #8210 it was also asked to tagzig-out
but from a quick glance this might not be as simple because that's also the install prefix but also doesn't appear as large.