jeffro256: I can reproduce this locally, it's not a CI issue paste.debian.net/hidden/40a6b45f

<j​effro256:monero.social> Yes I was able repro locally as well...

<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

no problem and ty for looking into it

<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?

<j​effro256:monero.social> I'm patching a fix btw

<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

"does it run the tests as-if it were to be merged into master" <-- seems to be this which also makes sense

<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

please also open against release

<j​effro256:monero.social> Done

soliciting dev comments to this CCS proposal: repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/403