Request for Support: Integration of Cirruslabs/Tart with Nektos/Act #2105

triggered96 · 2023-11-27T10:39:27Z

Dear Nektos/Act Team,

I hope this message finds you well. I am writing to bring your attention to the incredible capabilities of Cirruslabs/Tart, a virtualization toolset designed for building, running, and managing macOS and Linux virtual machines (VMs) on Apple Silicon. This tool, crafted by CI engineers, offers exceptional advantages for automation needs.

Key Advantages of Tart:

Near-Native Performance: Tart utilizes Apple's Virtualization.Framework, ensuring near-native performance.
OCI-Compatible Registry Support: It enables the seamless push/pull of virtual machines from any OCI-compatible container registry.
Automated VM Creation: Tart provides a Packer Plugin for streamlined and automated VM creation.
CI System Integration: It easily integrates with any CI system for enhanced automation workflows.
Cirrus Runners Service: Tart powers the Cirrus Runners service, offering a substantial performance boost (2-3 times) over standard GitHub-hosted runners at a more cost-effective rate.
Given the success of the gitlab-tart-executor in supporting GitLab, I am reaching out to kindly request support for Tart in the context of Nektos/Act. The integration of Tart with Nektos/Act would open up new possibilities for users seeking a powerful and efficient virtualization solution within their CI/CD pipelines.

Cirruslabs/tart
Nektos/act

Your consideration of this request is highly appreciated, and I believe that the collaboration between Nektos/Act and Cirruslabs/Tart could greatly benefit the developer community.

Thank you for your time and consideration. I am happy to provide any additional information or assistance needed.

fkorotkov · 2023-11-27T16:16:00Z

Tart maintainer here. 👋 We'll be great to see something like the following to be supported.

name: Tests
jobs:
  test:
    runs-on: ghcr.io/cirruslabs/macos-sonoma-xcode:latest

We are willing to help in any capacity if act community feels Tart support will be useful for running macOS actions locally.

ChristopherHX · 2023-11-27T21:27:31Z

Me from my part are unable to develop for the apple m-series platform. Assuming there is no simulator of tart for macOS 14 intel / linux intel or arm64 / windows intel.
We will see if other act maintainer / the owner would comment here.

name: Tests
jobs:
  test:
    runs-on: macos-latest
    ....

via

act -P macos-latest=tart://ghcr.io/cirruslabs/macos-sonoma-xcode:latest

Might be more act style. The problem with -P macos-latest=ghcr.io/cirruslabs/macos-sonoma-xcode:latest is act would need to inspect the oci manifest to detect which tool to use.

Oh runs-on: ghcr.io/cirruslabs/macos-sonoma-xcode:latest is possible via the autoscaler of tart for GitHub Actions, I didn't see much runtime labels before.

This means runtime label should be added to act? Currently act has a fall through to "skip unsupported platform"

Wouldn't this still require to check if the runtime label could be run with tart?

The most trivial way of using tart with current act is the following

name: Tests
jobs:
  test:
    runs-on: macos-latest
    ....

via the act command running in the tart vm

act -P macos-latest=-self-hosted

For example you could mount your project workspace into tart and run act inside tart.

I'm grateful that cirruslabs provided me access to an apple m-series ci at no fee, however I still don't have any developing system for the macOS m-series platform. Would mean for me to need to borrow the personal macbook of my brother

triggered96 · 2023-11-27T21:39:07Z

Self-host is indeed the less invasive approach at present, but its isolation is not good. It is easy to damage the host environment. The reason why I recommend integrating tart is because the container started by tart can have a good isolation environment, and tart starts very quickly, almost starting in 3 seconds. Currently only github and gitlab are supported, but I hope I can also add support for act.

ChristopherHX · 2023-11-27T22:02:31Z

Self-host is indeed the less invasive approach at present, but its isolation is not good

Yeah that's true. I meant to run act inside of tart to use the VM as the host environment. As long you don't delete your own workspace inside of the tart vm.

What kind of communication channels does tart support?

stdin / stdout redirection of tart run together with an cli program to run? like docker, ssh
- or do we need to connect via ssh
- This can be used to tranfer every job into a separate tart vm and allow to send cancellation via stdin
- Then I would need to know the required cli commands
Can tart access the ip addr of the host? I think act --help shows the ip I mean here, the outbound ip used to connect to external ip addresses. Obviously the spawned act inside the vm could replace the ip with a different one using the command of the docs.
I think it is needed to bind mount the workspace of act into every job, mounting it readonly is enough.

Doing this without mounting the act binary into the tart vm, would mean a lot of new logic for an executor. However then we don't have the problem to share state between jobs. It's a challenge.

I guess an ssh executor with some cli commands before and after the job could also make this work, then I'm at least able to help you.

I'm not familar with tart, nor can I run it to figure it out myself.

triggered96 · 2023-11-27T22:18:24Z

Self-host is indeed the less invasive approach at present, but its isolation is not good

Yeah that's true. I meant to run act inside of tart to use the VM as the host environment. As long you don't delete your own workspace inside of the tart vm.

What kind of communication channels does tart support?

stdin / stdout redirection of tart run together with an cli program to run? like docker, ssh

or do we need to connect via ssh

This can be used to tranfer every job into a separate tart vm and allow to send cancellation via stdin

Then I would need to know the required cli commands

Can tart access the ip addr of the host? I think act --help shows the ip I mean here, the outbound ip used to connect to external ip addresses. Obviously the spawned act inside the vm could replace the ip with a different one using the command of the docs.

I think it is needed to bind mount the workspace of act into every job, mounting it readonly is enough.

Doing this without mounting the act binary into the tart vm, would mean a lot of new logic for an executor. However then we don't have the problem to share state between jobs. It's a challenge.

I guess an ssh executor with some cli commands before and after the job could also make this work, then I'm at least able to help you.

I'm not familar with tart, nor can I run it to figure it out myself.

I think tart should be used as an external binary mode, similar to docker, instead of integrating tart source code into act. tart has a command mode similar to docker. You can also mount directories and log in via ssh. Please refer to https://github.com/cirruslabs/gitlab-tart-executor and https://tart.run/quick-start/

$ tart -h
USAGE: tart <subcommand>

OPTIONS:
  --version               Show the version.
  -h, --help              Show help information.

SUBCOMMANDS:
  create                  Create a VM
  clone                   Clone a VM
  run                     Run a VM
  set                     Modify VM's configuration
  get                     Get a VM's configuration
  list                    List created VMs
  login                   Login to a registry
  logout                  Logout from a registry
  ip                      Get VM's IP address
  pull                    Pull a VM from a registry
  push                    Push a VM to a registry
  import                  Import VM from a compressed .tvm file
  export                  Export VM to a compressed .tvm file
  prune                   Prune OCI and IPSW caches or local VMs
  rename                  Rename a VM
  stop                    Stop a VM
  delete                  Delete a VM
  suspend                 Suspend a VM

  See 'tart help <subcommand>' for detailed help.

Try running a Tart VM on your Apple Silicon device running macOS 13.0 (Ventura) or later (will download a 25 GB image):

brew install cirruslabs/cli/tart
tart clone ghcr.io/cirruslabs/macos-sonoma-base:latest sonoma-base
tart run sonoma-base

Manual installation from a release archive
SSH access¶
If the guest VM is running and configured to accept incoming SSH connections you can conveniently connect to it like so:

ssh admin@$(tart ip sonoma-base)

Running scripts inside Tart virtual machines

We recommend using Cirrus CLI to run scripts and/or retrieve artifacts from within Tart virtual machines. Alternatively, you can use plain ssh connection and tart ip command:

brew install cirruslabs/cli/sshpass
sshpass -p admin ssh -o "StrictHostKeyChecking no" admin@$(tart ip sonoma-base) "uname -a"
sshpass -p admin ssh -o "StrictHostKeyChecking no" admin@$(tart ip sonoma-base) < script.sh

Mounting directories¶
To mount a directory, run the VM with the --dir argument:

tart run --dir=project:~/src/project vm

Here, the project specifies a mount name, whereas the ~/src/project is a path to the host's directory to expose to the VM.

It is also possible to mount directories in read-only mode by adding a third parameter, ro:

tart run --dir=project:~/src/project:ro vm

To mount multiple directories, repeat the --dir argument for each directory:

tart run --dir=www1:~/project1/www --dir=www2:~/project2/www

Note that the first parameter in each --dir argument must be unique, otherwise only the last --dir argument using that name will be used.

Note: to use the directory mounting feature, the host needs to run macOS 13.0 (Ventura) or newer.

Accessing mounted directories in macOS guests¶
All shared directories are automatically mounted to /Volumes/My Shared Files directory.

The directory we've mounted above will be accessible from the /Volumes/My Shared Files/project path inside a guest VM.

Note: to use the directory mounting feature, the guest VM needs to run macOS 13.0 (Ventura) or newer.

Changing mount location
Accessing mounted directories in Linux guests¶
To be able to access the shared directories from the Linux guest, you need to manually mount the virtual filesystem first:

mount -t virtiofs com.apple.virtio-fs.automount /mnt/shared
The directory we've mounted above will be accessible from the /mnt/shared/project path inside a guest VM.

ChristopherHX · 2023-11-27T22:31:23Z

I guess copying this file into act is the easiest

https://github.com/cirruslabs/gitlab-tart-executor/blob/main/internal/tart/vm.go

I fear /Volumes/My Shared Files can cause issues in act, because not every code might behave correctly with spaces in paths.

triggered96 · 2023-11-27T22:34:59Z

I have it running fine on gitlab, no problems with /Volumes/My Shared Files. I'm sure of this.

I have it running fine on gitlab, no problems with/Volumes/My Shared Files. I'm sure of this.

triggered96 · 2023-11-27T22:43:01Z

"Tart and Docker are indeed very similar. Apart from the initial image retrieval over the network, the key distinction lies in the speed of container startup. Testing on my machine revealed that starting a new Tart container takes around 3 seconds. With such speed, I can build the desired project in a new container environment. One major advantage of containers is their isolation, ensuring that each build runs in a new and clean container environment. This aligns with the original intention of Act, and this is made possible by Apple's disk read speed."

Running with gitlab-runner 16.6.0 (3046fee8)
  on macOS-runner 7GL9LSi9, system ID: s_d58ff559ed4b

Preparing the "custom" executor
00:10
Using Custom executor...
2023/11/22 11:46:56 Pulling the latest version of macos-ventura-base...
2023/11/22 11:46:56 Cloning and configuring a new VM...
2023/11/22 11:46:56 Waiting for the VM to boot and be SSH-able...
2023/11/22 11:47:06 Was able to SSH!
2023/11/22 11:47:06 VM is ready.

Preparing environment
00:02
Running on admins-Virtual-Machine.local...

Getting source from Git repository
00:01
Fetching changes with git depth set to 20...
Initialized empty Git repository in /private/tmp/builds/triggered/actions-demo/.git/
Created fresh repository.
Checking out 4cb43aeb as detached HEAD (ref is master)...
Skipping Git submodules setup

Executing "step_script" stage of the job script
00:01
WARNING: Starting with version 17.0 the 'build_script' stage will be replaced with 'step_script': https://gitlab.com/groups/gitlab-org/-/epics/6112
$ uname -a
Darwin admins-Virtual-Machine.local 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:19 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_VMAPPLE arm64
Job succeeded

ChristopherHX · 2023-11-28T15:19:00Z

I have it running fine on gitlab, no problems with /Volumes/My Shared Files. I'm sure of this.

I have it running fine on gitlab, no problems with/Volumes/My Shared Files. I'm sure of this.

For example a step like (syntax construct may not exist in gitlab, act partially implements actions)

- run: somescript
  shell: bash -e {0}

May end up internally as

bash -e /Volumes/My Shared Files/path/to/script.sh

If you run that in a terminal window you will see what I mean.

This kind of problem might exits in more places..

Most will probably work most of the time...

I can probably try to create a poc but someone else need to test that on am m1..

triggered96 · 2023-11-28T21:48:30Z

I have it running fine on gitlab, no problems with /Volumes/My Shared Files. I'm sure of this.

I have it running fine on gitlab, no problems with/Volumes/My Shared Files. I'm sure of this.

For example a step like (syntax construct may not exist in gitlab, act partially implements actions)
- run: somescript
  shell: bash -e {0}
May end up internally as
bash -e /Volumes/My Shared Files/path/to/script.sh
If you run that in a terminal window you will see what I mean.

This kind of problem might exits in more places..

Most will probably work most of the time...

I can probably try to create a poc but someone else need to test that on am m1..

$ tart run  macos-ventura-base --dir .cache/

Last login: Tue Nov 28 21:43:30 on console
admin@admins-Virtual-Machine ~ % /Volumes/My\ Shared\ Files/act 
zsh: permission denied: /Volumes/My Shared Files/act
admin@admins-Virtual-Machine ~ % cd /Volumes/My\ Shared\ Files/act 
admin@admins-Virtual-Machine act % cat > shell.sh
echo "Hello" 
^C
admin@admins-Virtual-Machine act % bash -e /Volumes/My\ Shared\ Files/act/shell.sh
Hello
admin@admins-Virtual-Machine act %

Just add \ before the space to solve the problem

triggered96 · 2023-12-01T09:34:17Z

I have it running fine on gitlab, no problems with /Volumes/My Shared Files. I'm sure of this.

I have it running fine on gitlab, no problems with/Volumes/My Shared Files. I'm sure of this.

For example a step like (syntax construct may not exist in gitlab, act partially implements actions)
- run: somescript
  shell: bash -e {0}
May end up internally as
bash -e /Volumes/My Shared Files/path/to/script.sh
If you run that in a terminal window you will see what I mean.

This kind of problem might exits in more places..

Most will probably work most of the time...

I can probably try to create a poc but someone else need to test that on am m1..

https://github.com/cirruslabs/cirrus-cli/tree/master/internal/executor/instance/persistentworker/isolation/tart
https://github.com/cirruslabs/cirrus-cli/blob/master/internal/executor/instance/persistentworker/isolation/tart/tart.go

ChristopherHX · 2023-12-04T20:47:07Z

I have created a branch with some code from the gitlab executor, I will continue at a later point of time. It's much easier with the hardware so you can actually run code, nothing to test at the moment.

We need to mount the HostEnviroment scratch space
We need to add a path translation mapping, due to mount path restrictions
We might need to map tarts mount path of the vm path back to the host filesystem, due to filesystem mounting and the code expects that we can directly copy into the container filesystem using the destination path inside the container.

I would be glad about a tart cli stub for macOS / Linux so testing doesn't require a real mac. AFAIK tart in tart is not possible so cirrus ci is not an option for tests with tart.

oilrich25 · 2023-12-05T08:08:22Z

I have created a branch with some code from the gitlab executor, I will continue at a later point of time. It's much easier with the hardware so you can actually run code, nothing to test at the moment.

We need to mount the HostEnviroment scratch space

We need to add a path translation mapping, due to mount path restrictions

We might need to map tarts mount path of the vm path back to the host filesystem, due to filesystem mounting and the code expects that we can directly copy into the container filesystem using the destination path inside the container.

I would be glad about a tart cli stub for macOS / Linux so testing doesn't require a real mac. AFAIK tart in tart is not possible so cirrus ci is not an option for tests with tart.

great. I have also been paying attention to tart. I have an m2 macmini and I can provide you with any testing needs.

oilrich25 · 2023-12-05T09:58:05Z

I have installed tart. How do you currently use act to test tart?

ChristopherHX · 2023-12-05T13:08:18Z

How do you currently use act to test tart?

I haven't tested anything with tart yet. If you are using my downstream go based runner projects you probably only need to write a small python / powershell script.

nektos/act itself is different, because it doesn't have any rpc concept to run the step runner in a different environment.

great. I have also been paying attention to tart. I have an m2 macmini and I can provide you with any testing needs.

remote ssh access would help me to get this working, due to the nature of tart it have to be outside of a VM. I'm not yet at the point to want to buy hardware to add support.

oilrich25 · 2023-12-05T14:15:58Z

How do you currently use act to test tart?

I haven't tested anything with tart yet. If you are using my downstream go based runner projects you probably only need to write a small python / powershell script.

nektos/act itself is different, because it doesn't have any rpc concept to run the step runner in a different environment.

great. I have also been paying attention to tart. I have an m2 macmini and I can provide you with any testing needs.

remote ssh access would help me to get this working, due to the nature of tart it have to be outside of a VM. I'm not yet at the point to want to buy hardware to add support.

I saw act added pkg https://github.com/nektos/act/commit/e50d11a4e68ab0697efdbe2df2449a557700da29 for tart.
If act is used, a ~/.actrc file should be provided.

# ~/.actrc
-P macos-latest=tart://ghcr.io/cirruslabs/macos-sonoma-xcode:latest

As for finding hardware, you can rent Amazon macOS service, which provides M2 hardware. Details https://aws.amazon.com/ec2/instance-types/mac/.
Or I will test the application you provided, and if there are any problems, I will respond to you immediately😁

oilrich25 · 2023-12-10T09:54:12Z

If it is a shared file system, it has been tested by me. The following method was found to be feasible.

oilrich25deMac-mini:Desktop oilrich25$ tart list
Source Name               Size State  
local  macos-ventura-base 20   stopped

oilrich25deMac-mini:Desktop oilrich25$ tart clone macos-ventura-base vm

oilrich25deMac-mini:Desktop oilrich25$ tart run --dir=_work:/Users/oilrich25/Desktop/gitea-actions-runner/actions-runner/_work vm

It is recommended to make a soft link ln -s /Volumes/My\ Shared\ Files/_work /private/tmp/_work

oilrich25deMac-mini:Desktop oilrich25$ sshpass -p admin ssh -o "StrictHostKeyChecking no" admin@$(tart ip vm) "ln -s /Volumes/My\ Shared\ Files/_work /private/tmp/_work"
oilrich25deMac-mini:Desktop oilrich25$ sshpass -p admin ssh -o "StrictHostKeyChecking no" admin@$(tart ip vm) "cd /private/tmp/_work/simple-go-action/simple-go-action/"
oilrich25deMac-mini:Desktop oilrich25$ sshpass -p admin ssh -o "StrictHostKeyChecking no" admin@$(tart ip vm) "cd /private/tmp/_work/simple-go-action/simple-go-action/ && pwd"
/private/tmp/_work/simple-go-action/simple-go-action

oilrich25deMac-mini:Desktop oilrich25$ sshpass -p admin ssh -o "StrictHostKeyChecking no" admin@$(tart ip vm) "cd /private/tmp/_work/simple-go-action/simple-go-action/ && ls"
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE.txt
README.md
build-image.sh
image
shell.sh

oilrich25deMac-mini:Desktop oilrich25$ sshpass -p admin ssh -o "StrictHostKeyChecking no" admin@$(tart ip vm) "cd /private/tmp/_work/simple-go-action/simple-go-action/ && ./shell.sh"
/private/tmp/_work/simple-go-action/simple-go-action

ChristopherHX · 2024-08-23T18:54:50Z

Long ago, I'm now working on this with a test system for this weekend.

[.github/workflows/test.yml] Running: .github/workflows/test.yml
| Initialize Workflow Run 23
| Updated Workflow Name: .github/workflows/test.yml
[.github/workflows/test.yml / _] Running: _
| Evaluate if
| Evaluating: success()
| Evaluating success:
| => true
| Result: true
| Prepare Job for execution
| Evaluate job name
| Evaluate job continueOnError
| Evaluate job timeoutMinutes
| Evaluate job cancelTimeoutMinutes
| Evaluate runs-on
| Queued Job: _ for queue tart
| Read Job from Queue: _ assigned to Runner Name:golang_55f70448-2af4-4749-b392-367bd3ccb510 Labels:tart
| Send Job to Runner: _ for queue tart assigned to Runner Name:golang_55f70448-2af4-4749-b392-367bd3ccb510 Labels:tart
[.github/workflows/test.yml / _] Running: Set up Worker
| Runner Name: golang_55f70448-2af4-4749-b392-367bd3ccb510
| Runner OSDescription: github-act-runner darwin/arm64
| Runner Version: 0.8.0
[.github/workflows/test.yml / _] Succeeded: Set up Worker
[.github/workflows/test.yml / _] Running: Set up Job
| Initialize translating the job request to nektos/act
| Starting nektos/act
[.github/workflows/test.yml / _] Succeeded: Set up Job
[.github/workflows/test.yml / _] Running: uname -a
| ⭐ Run Main uname -a
| Darwin admins-Virtual-Machine.local 23.6.0 Darwin Kernel Version 23.6.0: Fri Jul  5 17:54:05 PDT 2024; root:xnu-10063.141.1~2/RELEASE_ARM64_VMAPPLE arm64
|   ✅  Success - Main uname -a
| Stopping and removing Container... (waiting for 1m0s)
| 🏁  Job succeeded
[.github/workflows/test.yml / _] Succeeded: uname -a
[.github/workflows/test.yml / _] Job Completed with Status: Succeeded
[.github/workflows/test.yml] Workflow 23 Completed with Status: Succeeded
All Workflows finished successfully�+�d�

worker script of github-act-runner run --worker-args bash,/path/to/tart-worker.sh

/opt/homebrew/bin/tart clone ghcr.io/cirruslabs/macos-sonoma-base:latest sonoma-base
/opt/homebrew/bin/tart run --dir=gh-act-runner:/path/to/act/runner/folder:ro sonoma-base&
VMPID=$!
/opt/homebrew/bin/sshpass -p admin ssh -o "StrictHostKeyChecking no" "admin@$(/opt/homebrew/bin/tart ip sonoma-base)" "/Volumes/My\\ Shared\\ Files/gh-act-runner/github-act-runner worker"
kill -SIGINT "$VMPID"
/opt/homebrew/bin/tart delete sonoma-base

ChristopherHX · 2024-08-23T23:19:22Z

....https://github.com/nektos/act/tree/act-tart updated.....
Known issue code copied from gitlab leaks process handles of tart, so I have to usually run "pkill tart".

I have no idea if the gitlab runner has not such an issue after 3+ runs, but maybe they fixed it or whatever

ChristopherHX · 2024-08-24T11:06:44Z

m1@276d2df0-3de9-43e0-a4e9-9d971e5e59d6 act % PATH=$PATH:/opt/homebrew/bin ./act -W w.yml -P "macos-14=tart://ghcr.io/cirruslabs/macos-sonoma-base:latest"
WARN[0000] Couldn't get a valid docker connection: no DOCKER_HOST and an invalid container socket '' 
WARN  ⚠ You are using Apple M-series chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠  
INFO[0000] deleted cache: &{ID:1 Key:macos Version:1a4929ccabb1b13c496b484824788895cebb7024a81d64d4ba0fd8c2e60c2fe0 Size:255 Complete:true UsedAt:1724497124 CreatedAt:1724497124}  module=artifactcache
INFO[0000] deleted cache: &{ID:2 Key:macos Version:1a4929ccabb1b13c496b484824788895cebb7024a81d64d4ba0fd8c2e60c2fe0 Size:256 Complete:true UsedAt:1724497168 CreatedAt:1724497168}  module=artifactcache
2024/08/24 13:05:36 Pulling the latest version of ghcr.io/cirruslabs/macos-sonoma-base:latest...
2024/08/24 13:05:37 Cloning and configuring a new VM...
2024/08/24 13:05:37 CreateNewVM
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
ln -sf '/Volumes/My Shared Files/act' /private/tmp/act
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env PATH=/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/usr/local/share/dotnet:~/.dotnet/tools:/opt/homebrew/Cellar/go/1.23.0/libexec/bin:/Users/m1/.vscode-server/cli/servers/Stable-fee1edb8d6d72a0ddff41e5f71a671c23ed924b9/server/bin/remote-cli:/opt/homebrew/bin node --no-warnings -e console.log\(process.execPath\)
exit $?
[w.yml/_]   ☁  git clone 'https://github.com/actions/github-script' # ref=v6
[w.yml/_]   ☁  git clone 'https://github.com/actions/cache' # ref=v4
[w.yml/_] ⭐ Run Main uname -a
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env CI=true GITHUB_ACTION_REPOSITORY='' GITHUB_ACTIONS=true GITHUB_REPOSITORY=nektos/act GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json ImageOS=macos14 RUNNER_OS=macOS GITHUB_HEAD_REF='' GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache ACTIONS_CACHE_URL=http://51.159.121.48:49777/ ACT=true GITHUB_JOB=_ GITHUB_REPOSITORY_OWNER=nektos GITHUB_WORKFLOW=w.yml GITHUB_REF=refs/heads/act-tart GITHUB_ACTION_PATH='' GITHUB_ACTOR=nektos/act GITHUB_API_URL=https://api.github.com GITHUB_GRAPHQL_URL=https://api.github.com/graphql GITHUB_RUN_NUMBER=1 GITHUB_EVENT_NAME=push GITHUB_WORKSPACE=/private/tmp/act//hostexecutor GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33 GITHUB_REF_NAME=act-tart GITHUB_REF_TYPE=branch GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt RUNNER_TEMP=/private/tmp/act//tmp RUNNER_TRACKING_ID='' GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md GITHUB_SERVER_URL=https://github.com RUNNER_ARCH=arm64 GITHUB_RUN_ID=1 GITHUB_ACTION=0 GITHUB_ACTION_REF='' GITHUB_RETENTION_DAYS=0 RUNNER_PERFLOG=/dev/null GITHUB_BASE_REF='' GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt bash --noprofile --norc -e -o pipefail /private/tmp/act//act/workflow/0
exit $?
| Darwin admins-Virtual-Machine.local 23.6.0 Darwin Kernel Version 23.6.0: Fri Jul  5 17:54:05 PDT 2024; root:xnu-10063.141.1~2/RELEASE_ARM64_VMAPPLE arm64
[w.yml/_]   ✅  Success - Main uname -a
[w.yml/_] ⭐ Run Main echo "$TEST"
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env GITHUB_ACTION_REPOSITORY='' GITHUB_ACTION_REF='' GITHUB_EVENT_NAME=push RUNNER_PERFLOG=/dev/null GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md GITHUB_ACTIONS=true GITHUB_ACTOR=nektos/act GITHUB_REF_NAME=act-tart GITHUB_REF_TYPE=branch GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt TEST='my test env' GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt GITHUB_WORKSPACE=/private/tmp/act//hostexecutor GITHUB_REF=refs/heads/act-tart RUNNER_TRACKING_ID='' GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache RUNNER_ARCH=arm64 RUNNER_TEMP=/private/tmp/act//tmp ACTIONS_CACHE_URL=http://51.159.121.48:49777/ ACT=true GITHUB_RETENTION_DAYS=0 ImageOS=macos14 RUNNER_OS=macOS CI=true GITHUB_WORKFLOW=w.yml GITHUB_RUN_ID=1 GITHUB_ACTION=1 GITHUB_JOB=_ GITHUB_HEAD_REF='' GITHUB_SERVER_URL=https://github.com GITHUB_RUN_NUMBER=1 GITHUB_ACTION_PATH='' GITHUB_REPOSITORY=nektos/act GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33 GITHUB_REPOSITORY_OWNER=nektos GITHUB_BASE_REF='' GITHUB_API_URL=https://api.github.com GITHUB_GRAPHQL_URL=https://api.github.com/graphql GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt bash --noprofile --norc -e -o pipefail /private/tmp/act//act/workflow/1
exit $?
| my test env
[w.yml/_]   ✅  Success - Main echo "$TEST"
[w.yml/_] ⭐ Run Main echo "$TEST"
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env CI=true GITHUB_ACTIONS=true GITHUB_REF=refs/heads/act-tart GITHUB_REF_NAME=act-tart ACTIONS_CACHE_URL=http://51.159.121.48:49777/ GITHUB_WORKFLOW=w.yml GITHUB_RUN_ID=1 GITHUB_ACTION_PATH='' GITHUB_ACTION_REF='' GITHUB_REPOSITORY=nektos/act GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33 RUNNER_PERFLOG=/dev/null GITHUB_API_URL=https://api.github.com GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt GITHUB_RUN_NUMBER=1 GITHUB_ACTION_REPOSITORY='' GITHUB_ACTOR=nektos/act GITHUB_BASE_REF='' GITHUB_GRAPHQL_URL=https://api.github.com/graphql GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json GITHUB_REPOSITORY_OWNER=nektos RUNNER_TRACKING_ID='' ImageOS=macos14 GITHUB_JOB=_ GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt ACT=true GITHUB_EVENT_NAME=push GITHUB_HEAD_REF='' GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt RUNNER_TEMP=/private/tmp/act//tmp GITHUB_ACTION=2 GITHUB_WORKSPACE=/private/tmp/act//hostexecutor GITHUB_REF_TYPE=branch TEST='my test env
echo '\''test'\''
another line
' GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache RUNNER_OS=macOS RUNNER_ARCH=arm64 GITHUB_RETENTION_DAYS=0 GITHUB_SERVER_URL=https://github.com bash --noprofile --norc -e -o pipefail /private/tmp/act//act/workflow/2
exit $?
| my test env
| echo 'test'
| another line
| 
[w.yml/_]   ✅  Success - Main echo "$TEST"
[w.yml/_] ⭐ Run Main actions/github-script@v6
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env RUNNER_OS=macOS GITHUB_RUN_NUMBER=1 GITHUB_ACTION_REPOSITORY=actions/github-script GITHUB_API_URL=https://api.github.com ACT=true GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt GITHUB_SERVER_URL=https://github.com CI=true GITHUB_ACTOR=nektos/act GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33 INPUT_PREVIEWS='' RUNNER_ARCH=arm64 GITHUB_WORKFLOW=w.yml GITHUB_REF_NAME=act-tart GITHUB_GRAPHQL_URL=https://api.github.com/graphql INPUT_RESULT-ENCODING=json INPUT_RETRIES=0 INPUT_DEBUG=false ACTIONS_CACHE_URL=http://51.159.121.48:49777/ GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json GITHUB_REPOSITORY_OWNER=nektos GITHUB_RETENTION_DAYS=0 INPUT_SCRIPT='console.log("Hello World")' INPUT_GITHUB-TOKEN=what GITHUB_ACTION=3 GITHUB_REF_TYPE=branch GITHUB_BASE_REF='' GITHUB_HEAD_REF='' GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt INPUT_USER-AGENT=actions/github-script GITHUB_WORKSPACE=/private/tmp/act//hostexecutor GITHUB_RUN_ID=1 GITHUB_ACTION_PATH='' GITHUB_REF=refs/heads/act-tart RUNNER_TRACKING_ID='' RUNNER_TEMP=/private/tmp/act//tmp GITHUB_ACTION_REF=v6 GITHUB_ACTIONS=true GITHUB_REPOSITORY=nektos/act GITHUB_EVENT_NAME=push GITHUB_JOB=_ RUNNER_PERFLOG=/dev/null ImageOS=macos14 RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md INPUT_RETRY-EXEMPT-STATUS-CODES=400,401,403,404,422 GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt node /private/tmp/act/act/actions/actions-github-script@v6/dist/index.js
exit $?
| Hello World
[w.yml/_]   ✅  Success - Main actions/github-script@v6
[w.yml/_] ⭐ Run Main Test
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env GITHUB_REPOSITORY=nektos/act GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33 GITHUB_REF=refs/heads/act-tart GITHUB_BASE_REF='' ImageOS=macos14 GITHUB_ACTION_PATH='' GITHUB_WORKFLOW=w.yml GITHUB_ACTION_REF='' GITHUB_WORKSPACE=/private/tmp/act//hostexecutor GITHUB_API_URL=https://api.github.com GITHUB_GRAPHQL_URL=https://api.github.com/graphql GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt ACTIONS_CACHE_URL=http://51.159.121.48:49777/ GITHUB_ACTION_REPOSITORY='' GITHUB_REF_TYPE=branch GITHUB_RUN_ID=1 RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json RUNNER_TEMP=/private/tmp/act//tmp GITHUB_RUN_NUMBER=1 GITHUB_EVENT_NAME=push GITHUB_REPOSITORY_OWNER=nektos RUNNER_PERFLOG=/dev/null GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt ACT=true CI=true GITHUB_RETENTION_DAYS=0 GITHUB_SERVER_URL=https://github.com RUNNER_ARCH=arm64 GITHUB_ACTIONS=true GITHUB_ACTOR=nektos/act GITHUB_REF_NAME=act-tart GITHUB_JOB=_ GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md RUNNER_OS=macOS RUNNER_TRACKING_ID='' GITHUB_HEAD_REF='' GITHUB_ACTION=4 bash --noprofile --norc -e -o pipefail /private/tmp/act//act/workflow/4
exit $?
| GITHUB_JOB=_
| GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json
| RUNNER_OS=macOS
| GITHUB_BASE_REF=
| SHELL=/bin/zsh
| GITHUB_REF_NAME=act-tart
| GITHUB_REPOSITORY_OWNER=nektos
| GITHUB_ACTION_PATH=
| HOMEBREW_REPOSITORY=/opt/homebrew
| TMPDIR=/var/folders/0n/_7v_bpwd1w71f8l0b0kjw5br0000gn/T/
| SSH_CLIENT=192.168.64.1 49786 22
| GITHUB_ACTIONS=true
| RUNNER_ARCH=arm64
| GITHUB_RUN_NUMBER=1
| RUNNER_PERFLOG=/dev/null
| GITHUB_WORKFLOW=w.yml
| GITHUB_REF=refs/heads/act-tart
| RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache
| GITHUB_ACTION_REPOSITORY=
| USER=admin
| GITHUB_EVENT_NAME=push
| GITHUB_REF_TYPE=branch
| GITHUB_API_URL=https://api.github.com
| GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33
| RUNNER_TEMP=/private/tmp/act//tmp
| GITHUB_SERVER_URL=https://github.com
| HOMEBREW_NO_AUTO_UPDATE=1
| GITHUB_HEAD_REF=
| GITHUB_GRAPHQL_URL=https://api.github.com/graphql
| PATH=/opt/homebrew/opt/node@20/bin:/Users/admin/.rbenv/shims:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin
| GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt
| _=/usr/bin/env
| GITHUB_RETENTION_DAYS=0
| PWD=/private/tmp/act/hostexecutor
| ACT=true
| LANG=en_US.UTF-8
| ImageOS=macos14
| RBENV_SHELL=zsh
| GITHUB_ACTOR=nektos/act
| SHLVL=2
| HOME=/Users/admin
| RUNNER_TRACKING_ID=
| GITHUB_WORKSPACE=/private/tmp/act//hostexecutor
| CI=true
| GITHUB_ACTION_REF=
| HOMEBREW_PREFIX=/opt/homebrew
| GITHUB_RUN_ID=1
| LOGNAME=admin
| ACTIONS_CACHE_URL=http://51.159.121.48:49777/
| HOMEBREW_NO_INSTALL_CLEANUP=1
| GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt
| SSH_CONNECTION=192.168.64.1 49786 192.168.64.31 22
| GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt
| INFOPATH=/opt/homebrew/share/info:
| HOMEBREW_CELLAR=/opt/homebrew/Cellar
| GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md
| GITHUB_REPOSITORY=nektos/act
| GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt
| GITHUB_ACTION=4
[w.yml/_]   ✅  Success - Main Test
[w.yml/_] ⭐ Run Main Test
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt CI=true GITHUB_EVENT_NAME=push GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json GITHUB_REF_NAME=act-tart GITHUB_API_URL=https://api.github.com GITHUB_GRAPHQL_URL=https://api.github.com/graphql GITHUB_REPOSITORY_OWNER=nektos RUNNER_TEMP=/private/tmp/act//tmp GITHUB_ACTION_REPOSITORY='' GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33 ImageOS=macos14 RUNNER_ARCH=arm64 GITHUB_RUN_NUMBER=1 GITHUB_WORKSPACE=/private/tmp/act//hostexecutor GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md RUNNER_OS=macOS GITHUB_WORKFLOW=w.yml GITHUB_ACTION_REF='' GITHUB_JOB=_ GITHUB_RETENTION_DAYS=0 GITHUB_BASE_REF='' RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache ACT=true GITHUB_ACTION=5 GITHUB_ACTOR=nektos/act GITHUB_REPOSITORY=nektos/act GITHUB_SERVER_URL=https://github.com ACTIONS_CACHE_URL=http://51.159.121.48:49777/ GITHUB_ACTIONS=true RUNNER_PERFLOG=/dev/null RUNNER_TRACKING_ID='' GITHUB_HEAD_REF='' GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt GITHUB_RUN_ID=1 GITHUB_ACTION_PATH='' GITHUB_REF=refs/heads/act-tart GITHUB_REF_TYPE=branch GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt bash --noprofile --norc -e -o pipefail /private/tmp/act//act/workflow/5
exit $?
[w.yml/_]   ✅  Success - Main Test
[w.yml/_] ⭐ Run Main actions/cache/save@v4
run --no-graphics --dir act:/Users/m1/.cache/act/5da0b87c5c3c3270 act-w-yml-b7eb8ae462c6ac172b4f3ac76b97ada7efd7d52f35e57f453f6514db00bb4467
cd /private/tmp/act//hostexecutor
env RUNNER_TRACKING_ID='' GITHUB_RUN_ID=1 GITHUB_ACTOR=nektos/act GITHUB_REPOSITORY=nektos/act GITHUB_STATE=/private/tmp/act/act/workflow/statecmd.txt RUNNER_TEMP=/private/tmp/act//tmp GITHUB_ACTIONS=true GITHUB_OUTPUT=/private/tmp/act/act/workflow/outputcmd.txt ImageOS=macos14 INPUT_UPLOAD-CHUNK-SIZE='' INPUT_ENABLECROSSOSARCHIVE=false RUNNER_OS=macOS GITHUB_ACTION_REF=v4 GITHUB_SHA=2941e252646ee6a3155e2916a7fae4b88f76aa33 GITHUB_WORKSPACE=/private/tmp/act//hostexecutor RUNNER_PERFLOG=/dev/null GITHUB_HEAD_REF='' GITHUB_API_URL=https://api.github.com GITHUB_GRAPHQL_URL=https://api.github.com/graphql CI=true GITHUB_ACTION=cache GITHUB_EVENT_NAME=push INPUT_PATH=file GITHUB_ACTION_PATH='' GITHUB_EVENT_PATH=/private/tmp/act//act/workflow/event.json GITHUB_REF=refs/heads/act-tart GITHUB_JOB=_ GITHUB_REPOSITORY_OWNER=nektos GITHUB_RETENTION_DAYS=0 GITHUB_BASE_REF='' ACT=true RUNNER_TOOL_CACHE=/Users/m1/.cache/act/tool_cache GITHUB_RUN_NUMBER=1 GITHUB_ACTION_REPOSITORY=actions/cache GITHUB_REF_NAME=act-tart GITHUB_REF_TYPE=branch GITHUB_SERVER_URL=https://github.com INPUT_KEY=macOS RUNNER_ARCH=arm64 ACTIONS_CACHE_URL=http://51.159.121.48:49777/ GITHUB_WORKFLOW=w.yml GITHUB_PATH=/private/tmp/act/act/workflow/pathcmd.txt GITHUB_ENV=/private/tmp/act/act/workflow/envs.txt GITHUB_STEP_SUMMARY=/private/tmp/act/act/workflow/SUMMARY.md node /private/tmp/act/act/actions/actions-cache-save@v4/dist/save-only/index.js
exit $?
[w.yml/_]   💬  ::debug::Checking zstd --quiet --version
[w.yml/_]   💬  ::debug::1.5.6
[w.yml/_]   💬  ::debug::zstd version: 1.5.6
[w.yml/_]   💬  ::debug::implicitDescendants 'false'
[w.yml/_]   💬  ::debug::followSymbolicLinks 'true'
[w.yml/_]   💬  ::debug::implicitDescendants 'false'
[w.yml/_]   💬  ::debug::omitBrokenSymbolicLinks 'true'
[w.yml/_]   💬  ::debug::Search path '/Volumes/My Shared Files/act/hostexecutor/file'
[w.yml/_]   💬  ::debug::Matched: ../../../../Volumes/My Shared Files/act/hostexecutor/file
[w.yml/_]   💬  ::debug::Cache Paths:
[w.yml/_]   💬  ::debug::["../../../../Volumes/My Shared Files/act/hostexecutor/file"]
[w.yml/_]   💬  ::debug::Archive Path: /private/tmp/act/tmp/ab4705ff-fa7f-4cef-9999-e530cb185c63/cache.tzst
| [command]/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /private/tmp/act//hostexecutor --files-from manifest.txt --use-compress-program zstdmt
[w.yml/_]   💬  ::debug::File Size: 255
[w.yml/_]   💬  ::debug::Reserving Cache
[w.yml/_]   💬  ::debug::Resource Url: http://51.159.121.48:49777/_apis/artifactcache/caches
[w.yml/_]   💬  ::debug::Saving Cache (ID: 6)
[w.yml/_]   💬  ::debug::Upload cache
[w.yml/_]   💬  ::debug::Resource Url: http://51.159.121.48:49777/_apis/artifactcache/caches/6
[w.yml/_]   💬  ::debug::Upload concurrency: 4
[w.yml/_]   💬  ::debug::Upload chunk size: 33554432
[w.yml/_]   💬  ::debug::Awaiting all uploads
[w.yml/_]   💬  ::debug::Uploading chunk of size 255 bytes at offset 0 with content range: bytes 0-254/*
[w.yml/_]   💬  ::debug::Commiting cache
| Cache Size: ~0 MB (255 B)
[w.yml/_]   💬  ::debug::Resource Url: http://51.159.121.48:49777/_apis/artifactcache/caches/6
| Cache saved successfully
| Cache saved with key: macOS
[w.yml/_]   ✅  Success - Main actions/cache/save@v4
[w.yml/_] Cleaning up container for job _
2024/08/24 13:05:58 Stop VM?
2024/08/24 13:05:58 Stop VM REAL?
2024/08/24 13:05:58 send sigint?
2024/08/24 13:05:58 wait?
Stopping VM...
Stopping VM...
2024/08/24 13:05:58 wait done?
Stopping VM...
Stopping VM...
Stopping VM...
Stopping VM...
Stopping VM...
Stopping VM...
Stopping VM...
2024/08/24 13:05:58 Remove VM?
[w.yml/_] 🏁  Job succeeded

triggered96 added the kind/feature-request New feature or request label Nov 27, 2023

fkorotkov mentioned this issue Nov 27, 2023

Request for Cirruslabs/tart Support in Nektos/act cirruslabs/tart#667

Closed

oilrich25 mentioned this issue Dec 7, 2023

Prepare for adding tart to runner.server [Insider information of gitlab-tart-executor parameters executed through Debug on M2 has been provided] ChristopherHX/runner.server#282

Open

ChristopherHX linked a pull request Aug 24, 2024 that will close this issue

feat: tart macOS vm's as job container #2434

Open

ChristopherHX added the backlog Those issues are on the roadmap label Sep 26, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Request for Support: Integration of Cirruslabs/Tart with Nektos/Act #2105

Request for Support: Integration of Cirruslabs/Tart with Nektos/Act #2105

Request for Support: Integration of Cirruslabs/Tart with Nektos/Act #2105

Request for Support: Integration of Cirruslabs/Tart with Nektos/Act #2105

Comments