IRC logs for #farmOS, 2024-09-24 (GMT)

2024-09-23
2024-09-25
TimeNickMessage
[00:47:40]* whatstheword has joined #farmos
[04:54:18]* TormiTabor[m] has joined #farmos
[09:03:49]<mstenta[m]>symbioquine paul121 https://github.com/farmOS/farmOS/pull/879
[09:04:14]<mstenta[m]>This is blocking v3.3.0 release.
[09:04:33]<mstenta[m]>If the PR tests pass I'm going to merge it.
[09:04:40]<mstenta[m]>(two previous attempts passed)
[09:06:23]<symbioquine[m]>Do you know how to see the previous runs in the GH UI?
[09:06:32]<symbioquine[m]>(Curious about timing and console log messages...)
[09:07:07]<mstenta[m]>Which previous runs are you interested in? This is the first time it's running in this PR, but I have a bunch of other branch test runs...
[09:07:10]<symbioquine[m]>I can get to the current run (I think) at https://github.com/farmOS/farmOS/actions/runs/11014354888
[09:07:22]<symbioquine[m]>but presumably that's the third time you've re-run it right?
[09:07:32]<symbioquine[m]>oh, I see
[09:07:43]<mstenta[m]>https://github.com/mstenta/farmOS/actions
[09:07:50]<mstenta[m]>(are you able to see those? or are they private to me?)
[09:07:52]<symbioquine[m]>> I have a bunch of other branch test runs...
[09:07:53]<symbioquine[m]>Those are the ones I was looking for
[09:09:10]<mstenta[m]>The fact that it passed twice already is very promising, considering that a) the existing failure would happen >50% of the time, and b) the new failure was happening 100% of the time.
[09:09:23]<symbioquine[m]>Yeah
[09:09:34]<symbioquine[m]>Could be just lucky though 😅
[09:09:37]<mstenta[m]>Yea
[09:09:49]<mstenta[m]>This is the only thing holding up the v3.3.0 release right now
[09:10:01]<mstenta[m]>> the new failure was happening 100% of the time
[09:21:59]<mstenta[m]>Actually have three more runs going in parallel now:
[09:22:08]<mstenta[m]>https://github.com/farmOS/farmOS/actions/runs/11014346790
[09:22:09]<mstenta[m]>https://github.com/farmOS/farmOS/actions/runs/11014354888
[09:22:14]<mstenta[m]>https://github.com/mstenta/farmOS/actions/runs/11014354531
[09:22:22]<mstenta[m]>(just from force-pushing the PR)
[09:23:25]<mstenta[m]>We'll have results in ~10 minutes.
[09:37:43]<mstenta[m]>All passed.
[09:38:01]<symbioquine[m]>Cool!
[09:38:49]<symbioquine[m]>Seems promising as far as avoiding those intermittent failures entirely - at the cost of taking a bit longer (for a given non-failing test), I think
[09:39:22]<mstenta[m]>Yep!
[09:39:26]<mstenta[m]>I'll take it!!!
[09:40:05]<mstenta[m]>Especially now that we're building ARM images, I can just accept that tests take longer 😅
[09:40:18]<mstenta[m]>Good reason to take breaks
[09:40:32]<mstenta[m]>https://xkcd.com/303/
[09:44:24]<mstenta[m]>symbioquine: I suppose we can actually remove `--processes=auto`? 🤔
[09:44:44]<symbioquine[m]>I suspect so
[09:45:06]<mstenta[m]>I think we added that specifically so that we could set it to 1 for sqlite
[09:45:18]<symbioquine[m]>Yeah, that's my recollection too
[09:48:34]<mstenta[m]>I'll push one commit to my fork just to make sure that doesn't break anything. Then I'll tag 3.3.0.
[09:49:43]<symbioquine[m]>Quickest & lowest risk strategy at this point is to leave the `--processes=auto` part in and do that cleanup after the release
[09:50:07]<symbioquine[m]>Should be a no-op, but you've already tested more extensively with that still there.
[09:50:45]<mstenta[m]>Yea... already running a test... I'm getting breakfast so I can wait :-)
[09:51:09]<mstenta[m]>https://github.com/mstenta/farmOS/actions/runs/11015179629
[10:34:00]<mstenta[m]>Tagged 3.3.0
[10:34:09]<mstenta[m]>Here is a PR for the 3.3.0 blog post: https://github.com/farmOS/farmOS-community-blog/pull/29
[10:34:37]<mstenta[m]>(Hastily drafted by a slightly burnt-out @mstenta yesterday afternoon... open to improvements!)
[10:35:03]<mstenta[m]>(Or two approvals and it's out the door! 🚢)
[10:36:12]<mstenta[m]>botlfarm: I'll release 1.0.0-alpha1 of the Grazing Plan module today too! So we'll have something to share on tomorrow's call.
[10:37:09]<symbioquine[m]>mstenta[m]: Let's at least wait until the workflow runs complete - so all the release artifacts are fully published first.
[10:38:39]<symbioquine[m]>(Though I guess it's a good sign that the 3.x-dev docker images got published 😄 https://hub.docker.com/r/farmos/farmos/tags)
[10:39:42]<mstenta[m]>Oh awesome!!!!!!
[10:48:07]<symbioquine[m]>Left a bit of feedback/comments
[10:54:44]<mstenta[m]>That GitHub feature for applying suggestions is pretty nifty :-)
[11:03:40]* botlfarm[m] has joined #farmos
[11:03:43]<botlfarm[m]><mstenta[m]> "botlfarm: I'll release 1.0.0-..." <- Excelent! looking foward to it.
[11:08:14]<mstenta[m]>Both the 3.x and 3.3.0 tests failed (one with SQLite3 and one with MariaDB). But both were a familiar error that happens from time to time.
[11:08:19]<mstenta[m]>ACTION sent a code block: https://matrix.org/oftc/media/v1/media/download/AXy0LmlViU1vRO3ud87DdQ5C...
[11:08:38]<mstenta[m]>Re-running them now... that usually resolves it.
[11:09:23]<mstenta[m]>paul121: It reminds me of this... https://github.com/farmOS/farmOS/issues/514
[11:10:36]<mstenta[m]>We're still pinning selenium/standalone-chrome at a (now very) old version: https://github.com/farmOS/farmOS/blob/db7c88a4e632d9ec05ce9cb63a6255fb25...
[11:10:46]<mstenta[m]>So I wonder if that's related to these occassional "page crash" errors
[11:50:33]<mstenta[m]>3.3.0 has been released! 🎉
[11:51:21]<mstenta[m]>I also just release 3.0.0-alpha3 of the Crop Plan module (https://www.drupal.org/project/farm_crop_plan/releases/3.0.0-alpha3) and 1.0.0-alpha1 of the Grazing plan module (https://www.drupal.org/project/farm_grazing_plan/releases/1.0.0-alpha1) (cc botlfarm)
[11:51:24]* aislinnpearson[m] has joined #farmos
[11:51:24]<aislinnpearson[m]>Congratulations Mike!!
[11:51:28]<aislinnpearson[m]>(and Team)
[12:18:48]<symbioquine[m]>Does anybody with an M1/M2/etc Mac feel like testing the arm64v8 3.3.0 Docker image and see if it is faster for you than whatever you've been running (presumably the amd64 image via QEMU)? https://github.com/farmOS/farmOS-community-blog/pull/29#discussion_r1773...
[12:19:13]<symbioquine[m]> * Does anybody with an M1/M2/etc Mac feel like testing the arm64v8 3.3.0 Docker image and see if it is faster for you than whatever you've been running (presumably the amd64 image via QEMU)? Trying to validate this assertion: https://github.com/farmOS/farmOS-community-blog/pull/29#discussion_r1773...
[12:21:37]<symbioquine[m]>I think the command should be docker run --rm -p 80:80 --platform linux/arm64/v8 farmos/farmos:3.3.0
[12:22:42]<symbioquine[m]>(Just to be sure you're running the 3.3.0 tag and the linux/arm64/v8 build. Normal usage shouldn't require those specifiers. i.e. docker run --rm -p 80:80 farmos/farmos)
[12:23:25]<symbioquine[m]> * Does anybody with an M1/M2/etc Mac feel like testing the arm64v8 3.3.0 Docker image and see if it is faster for you than whatever you've been running (presumably the amd64 image via Docker-Desktop/QEMU)? Trying to validate this assertion: https://github.com/farmOS/farmOS-community-blog/pull/29#discussion_r1773...
[12:37:50]<FarmerEd[m]>I know images I'd built previously ran on Mac, Raspberry Pi's and other hosted ARM servers.
[12:38:57]<FarmerEd[m]>I can check the current build on an ARM VPS that I'm using if that is any use?
[14:05:44]<farmBOT>@farmOS@fosstodon.org => #farmOS 3.3.0 has been released! https://github.com/farmOS/farmOS/releases/3.3.0 => https://fosstodon.org/@farmOS/113193186818828594
[16:42:07]<symbioquine[m]><FarmerEd[m]> "I know images I'd built previous..." <- Good datapoint
[16:43:05]<symbioquine[m]><FarmerEd[m]> "I can check the current build on..." <- I'd be curious, but mostly I was trying to validate the claim we're trying to make in that blog post.