<_whitenotifier-e>
[scopehal] azonenberg 96fb51f - Removed all usage of deprecated GetInputLocation(), as well as non-Vulkan FlowGraphNode::Refresh(). Fixes 1054.
<_whitenotifier-e>
[scopehal-apps] azonenberg 0a06a81 - Mark newly created filters as dirty even if not adding to a plot, so measurements get correctly updated too. Fixes #997.
<d1b2>
<azonenberg> it parses out the few fields we care about from the json then invokes batch-launcher to kick off the build jobs
<d1b2>
<azonenberg> right now it's unidirectional, we do not report status back to github
<d1b2>
<azonenberg> so there's no pretty green check on the repo anymore, you have to open the dashboard to see results
<d1b2>
<azonenberg> i may eventually fix that but if we are thinking of migrating off github to codeberg or something it might make sense to delay until then
<d1b2>
<azonenberg> the migration to the new CI had to happen regardless to enable gpu/scope in the loop testing
<_whitenotifier-e>
[scopehal-apps] azonenberg b92b0a1 - Updated to latest scopehal
<d1b2>
<helaslo> Also if You will eventually tag the release will you be please be able to sign the tarball with GPG, and include the public key on the project page? Suse seems to prefer this: https://en.opensuse.org/openSUSE:Package_source_verification Also I think Fedora prefers a similar approach
<d1b2>
<azonenberg> Yeah release tags will go through an extra manual process to sign mac/windows binaries anyway
<d1b2>
<azonenberg> So we can do the same for the linux ones
<d1b2>
<azonenberg> i'll have to make a new gpg signing key for that purpose, i think the one i used to use for mail crypto is long expired and i want to use a separate one for this anyway
<d1b2>
<helaslo> Thanks, in the summer I plan to get ngscopeclient to Factory, I looked at the process in the past The nice thing about that is that we get daily CI runs around every external dependency update, so it will scream as soon as any dependency breaks the compilation/unit tests 😄
<d1b2>
<azonenberg> i mean running every ci build on arch is pretty good at that too :p
<d1b2>
<azonenberg> thats one of the reasons we have arch as a ci runner it's the canary in the coal mine for such problems
<d1b2>
<helaslo> I kinda like SUSE's approach to CI Test everything For the main OS they even "click" through the whole install process (and everything else) step by step and do some OCR to check for errors See: https://openqa.opensuse.org/tests/5993035 Despite being a rolling distro, it breaks only subtly and very-very rarely, and if that happens there is rollback
<d1b2>
<azonenberg> I want to eventually have the ngscopeclient gui scripted for testing
<d1b2>
<azonenberg> but we are a long ways from that being a thing
<d1b2>
<azonenberg> we dont even have 10% test coverage on the filters
<d1b2>
<azonenberg> and ~0% on drivers
<d1b2>
<helaslo> Maybe that can go together with the decoupling of scopehal?
<d1b2>
<helaslo> What is the plan for that? hardware-in-the-loop or mock devices with test cases?
<d1b2>
<azonenberg> Hardware in loop for thunderscope, ignore everything else to start
<d1b2>
<azonenberg> thunderscope we can easily get dev units and they dont take up much space or use much power
<d1b2>
<azonenberg> so it makes sense
<d1b2>
<azonenberg> other stuff, we may eventually want to make software mocks for but not sure yet
<d1b2>
<helaslo> Sounds good
<d1b2>
<azonenberg> but there is so much other refactoring and architecture cleanup needed before we think about that
<d1b2>
<helaslo> Wow the builds are a bit faster on the new CI (looking at the latest windows one with its 11 minutes 😄 )
<d1b2>
<azonenberg> and this is with no caching too
<d1b2>
<azonenberg> each build is from a clean image
<d1b2>
<azonenberg> (although i did bake some of the dependencies into the images so there's less downloads)
<d1b2>
<azonenberg> but they do an apt install/whatever at the start to grab every dep
<d1b2>
<helaslo> Maybe consider setting up a local cache for the linux repos? Just to minimize that part of the scripts I think most mirrors are http for this exact reason Can save a few minutes
<d1b2>
<azonenberg> the builders are also much beefier than github's, we have 8 vCPUs and 32GB RAM per runner (except the arm64 ones which have only 8GB due to capacity limits on the mac mini) and allow up to five to run simultaneously on the x86 box plus one on the mac
<d1b2>
<azonenberg> I have a local apt-cacher-ng instance I use for all of my personal boxen/VMs plus i believe the debian runners
<d1b2>
<azonenberg> i attempted to set it up for the ubuntu runners and had technical difficulties because of something weird canonical was doing and didnt have time to troubleshoot
<d1b2>
<azonenberg> the non-deb based distros and msys are currently running uncached
<d1b2>
<azonenberg> fixing that is a longer term todo
<_whitenotifier-e>
[scopehal-apps] azonenberg d218ccc - Updated to latest scopehal
<d1b2>
<azonenberg> ok i think that is basically all of the static analysis fixes that are not "we left X incomplete and didn't suppress the warning or mark the argument as unused because we want to be reminded to come back and finish the job"
<d1b2>
<azonenberg> (54 open cppcheck + clang-analyzer findings down from multiple thousands)