I've ran into issues while running `./gradlew chec...
# general
g
I've ran into issues while running
./gradlew check --continue
with Ubuntu 24.04.1 LTS on WSL2 (Windows 11). In a nutshell: numerous integration/e2e tests would fail due to timeouts. I'll setup the work environment on my Macbook Pro instead. Further details in reply
I've managed to increase the maximum number of open files to ~1M, and had allowed 4 CPUs + 32GB of RAM to WSL. I've peak at 32GB RAM usage but only 50% CPU usage. Still, the tests ran for over 6 hours and during all this time, the progress bar had stayed at 96%. I decided to shut it down since I believe the CI takes less than 2 hours to succesfully run all tests, so I believe my Windows+WSL setup will be a bottleneck here. Attached is logs of the tests. I do have a Macbook Pro 2019 w/ i9 + 32GB which I'll configure today and see what performance results I get. TL;DR: I think it'll be time for me to ditch Windows and entirely migrate to a Mac setup with M3 or M4 this year 😅
k
Unfortunately, I couldn’t get Venice to work on WSL2 and just moved my development to a Mac. Also, you don’t need to run every test locally. Just the ones you’re writing, and when you push your changes to GitHub there are jobs that will run every test for you.
👍 1
g
Yeah, that's what I thought, that the CI would run every test in any case Luckily my current office at home is already configured so I can easily switch between my PC and a macbook, so hopefully I get enough performance out of my current intel mac until I get a new one with a M3/M4 chip
Thanks for the insight @Koorous Vargha
k
No problem. It may take a little bit longer for builds to complete locally, but Felix is also on an Intel MacBook and makes it work.
👍 1
f
Yeah I’m due for an upgrade but have been lazy to get the paperwork done 😅 … the tests can all succeed when run individually, in my experience… but it is certainly true that there is some flakiness in many tests. The CI has automatic retries for all tests. Locally, how you run the test may or may not trigger the retries.
🙌 1
g
I actually found a great deal for a M3 Max on tuesday... and then spent 3 days configuring everything to my liking, learning the keybinds and everything. But, if it wasn't for the fact that it was a week of vacation for me, I would've never done it lol
k
Your story is incredibly relatable for me. When I initially started working on Venice, I tried to get it working in WSL2 but just couldn't get it to work. Also, my Dell XPS was on its last legs, so I decided to pull the trigger and get a Macbook M3 Pro.
❤️ 1
g
Honestly, the specs of the Pro would've been plenty for me, but the base and Pro models only go up to 2 external monitors and I'm just too used to having 3 (and the Max goes up to 5 which is kind of crazy)
f
It’s gotta be an odd number of monitors
Having a slit in the middle is not right
🍻 1
😅 1
g
Or... a vertical monitor, a horizontal one, and the laptop on one of those slanted aluminum things Which, I can't believe some people would actually prefer dealing with different orientations, resolutions AND sizes all at the same time, but oh well 😆
k
I've never lived with 3 external monitors before so I guess I don't know what I'm missing out on.
g
Probably not much. It's pretty much paying extra to not have to use hotkeys to quickly swap from window to window. I've very rarely had situations were having only 2 monitors would've been inconvenient. Even a single one, while using hotkeys, could probably be fine in most cases.
👍 1