-
Notifications
You must be signed in to change notification settings - Fork 5
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
TART_EXECUTOR_HOST_DIR breaking builds with Git LFS #92
Comments
It's probably this issue we don't have a workaround for 😔 cirruslabs/tart#567 (comment) |
Okay, sounds reasonable 🙃 might be worth a note in docs though 🤔 |
Hi @fkorotkov, sorry for reopening, but I got an idea of using a ramdisk |
@olejnjak do you mean pass a ramdisk from the host? Or use it inside the VM? |
I meant inside the VM, I assume passing it from the host would trigger the same issue with virtiofs, wouldn't it? |
Are you using AWS EBS by a chance? We've seen some reports where adding |
Nope our CI is running on self-hosted macs. |
Regarding the RAM disk, you can already have it with the following GitLab CI configuration, thanks to image: ghcr.io/cirruslabs/macos-sonoma-base:latest
job:
hooks:
pre_get_sources_script: |
# Preserve an already created builds directory as it might contain
# important files like "gitlab_runner_env" and "CI_SERVER_TLS_CA_FILE"
rsync -az "$CI_BUILDS_DIR/" "$CI_BUILDS_DIR.orig/"
# Create 10 GiB RAM disk (note that the size is in 512-byte blocks, not in bytes)
DISK=$(hdiutil attach -nomount ram://20971520 | tr -d '[:space:]')
diskutil erasevolume HFS+ RAMDISK "$DISK"
# Remount the created RAM disk to our builds directory
diskutil umount "$DISK"
diskutil mount -mountPoint "$CI_BUILDS_DIR" "$DISK"
# Restore builds directory contents
rsync -az "$CI_BUILDS_DIR.orig/" "$CI_BUILDS_DIR/"
rm -rf "$CI_BUILDS_DIR.orig"
script: |
pwd
mount Regarding the Also, in the future, please open a separate issue for such ideas: this will both allow us to track and for other users of GitLab Tart Executor to search them more easily. Thank you 🙌 |
Hi guys,
I wanted to utilize
TART_EXECUTOR_HOST_DIR
to see if we can manage to get some perf gains. But once set job fails when trying to fetch source code. It is the same when using--builds-dir
in config stage.All I get is this output
The mentioned log file contains this, which seem extremely weird:
With builds dir inside of the VM, everything is working fine.
Do you have experience with such issue? Thanks :-)
The text was updated successfully, but these errors were encountered: