00:49:36 <selsta> jeffro256: I can reproduce this locally, it's not a CI issue https://paste.debian.net/hidden/40a6b45f/
00:50:05 <m-relay> <j​effro256:monero.social> Yes I was able repro locally as well...
00:50:46 <m-relay> <j​effro256:monero.social> My bad, I'm looking at it right now. I think there were some merge changes that are confusing me w/ the frozen key image multisig changes
00:51:25 <selsta> no problem and ty for looking into it
01:53:43 <m-relay> <j​effro256:monero.social> Yup it was a bug that was introduced by merging two changes to the multisig tests. I guess I don't understand which code the CI build uses, does it run the tests as-if it were to be merged into master, or as it is in the PR branch?
01:53:52 <m-relay> <j​effro256:monero.social> I'm patching a fix btw
01:54:55 <m-relay> <j​effro256:monero.social> B/c the error lines in the Python logs *in the PR branch* don't match the code in the PR, but it matches the master code post-merge
02:25:14 <selsta> "does it run the tests as-if it were to be merged into master" <-- seems to be this which also makes sense
02:26:32 <m-relay> <j​effro256:monero.social> Okay, that makes sense now. There were two independent changes to the multisig tests that didn't conflict, but changed the results of each other
03:20:35 <selsta> please also open against release
03:25:23 <m-relay> <j​effro256:monero.social> Done
21:12:34 <geonic> soliciting dev comments to this CCS proposal: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/403