SPIKE: review TILT test {suite, tool} .

[jonathanpberger]

Is TILT sufficient to protect this initial wave up updates? Or do we need to bring in ICT or write custom tests? This spike is to get familiar enough w TILT to make that determination.

---

@kakucodes and @pharr117 to review TILT test {suite, tool}. PLEASE RECORD THIS!! Maybe we can use Descript on the video?

Tasks

Beta Give feedback

1. review the tool
2. spike on adding dev config / containers in vs code to get this up and running and scalable #59
   +0
   

[jonathanpberger]

@mdulin2 sez:

Beware:

• TILT sometimes barfs on ARM machines, and
• Use the proper flags to only run the machines you want otherwise RAM will bomb out

[jonathanpberger]

@jtieri sez "please add me to the cal invite, I'll join if I can"

[jonathanpberger]

@mdulin2 sez:

I run it on EC2 (rather than my macbook) bc 1. it's hefty, and 2. not sure it runs on mac. The guides are really good: https://github.com/wormhole-foundation/wormhole/blob/main/DEVELOP.md

[kakucodes]

https://strangeloveventures.slack.com/archives/C057DTCM76G/p1721247560445929 more info here

Joel and I spent an hour trying to get our bearings wrt Tilt testing in wormhole and the cliffnotes are:
The containers seem to potentially only run on windows (though we didn't leave feeling very confident in the single redis container we got deployed)
might make sense to check with nikhil that it is win only (as max had suggested)
might make sense at some point in time to get someone from the wormhole to pair with us and get the team primed
Tests are written in TS and can be found in __tests__  directories all around the repo
The Tiltfile in the root directory seems to be the main one
When calling tilt up you can pass --algorand=false to reduce the number of chain containers spun up
Tiltfile@L57 for the list of flags
Running tilt requires a running kubernetes cluster with a wormhole namespace established

[kakucodes]

https://ro.am/recordings/play/01a1df75-92de-46d4-ae95-d6ddeaf1bdfe?pwd=o2uJk.KDxGWP3DyupxSdYtF_0aEZBF

[pharr117]

I will be taking a look at the Tilt setup to answer a few of the major questions that came up in the call above

[jonathanpberger]

@pharr117 is still trying to build TILT on his machine (lots of virtualization software required to run TILT).

• is the KVM driver required? tried using docker driver for minicube, ran into issues (probably resolvable)
• HMW make this more feasible for mac? Can we just use the docker driver on minicube? (@nik-suri: I believe you can. IIRC, that's what I use on mac)
• there's some answers here to investigate: build guardiand on an ARM mac M1 machine wormhole-foundation/wormhole#4031 (comment)
• this PR seems to be helping: node: devcontainer support wormhole-foundation/wormhole#4032

[jonathanpberger]

@nik-suri also, this will definitely run on ubuntu and red hat

[jtieri]

@pharr117 has TILT mostly working (about 2/3 of the way there), it sounds like we need to setup a call to see if we can overcome the issues for the folks on macbooks with ARM CPUs.

[beckettsean]

Discussed with Justin, Joel, Marc, Peter, and Sean. Created #61 to track solution.

[pharr117]

Tilt review of Tilt is done, here is what I had to use to get it running on my machine:

1. Arch 6.6.41-1-MANJARO on x86
   • This is the main differentiating factor between the team's machines, since I am on Arch x86 I had no issues building and compiling the required software for Tilt to run
2. Minikube for k8s: minikube start --cpus=8 --memory=8G --disk-size=50g --driver=docker --kubernetes-version=v1.22.3 * The kvm2 driver works as well and probably provides more performant virtualization, but was more of a pain to build on Arch
   • When running with default Kubernetes of v1.30.0 (no specification of the option chooses this version), we ran into what the wormhole team called a Kubernetes bug in networking. They suggested to use the same k8s version as their CI environment which fixed this issue
3. Run tilt up, it will allow access in the browser to watch the container outputs for easier test grokking
4. Run tilt up --stream=true to stream the container logs to STDOUT instead

The basic gist of the tilt up tests from what I found is that it:

1. Builds and deploys a container for eth-devnet with expected contracts, testing the config as it goes
2. Builds and deploys a guardian chain and connects it to the eth devnet
3. Runs tests for behavior between the (1) and (2)

[jtieri]

We have reviewed everything and now we know we need to create a testing env in the cloud, see #61. Closing