I also note that the old build was using golang 1.21, and the FTBFS was introduced after upgrading unstable to golang 1.22.
Shengjing, I believe you handled the recent update of the golang toolchain from 1.21 to 1.22. Have you seen similar "mysterious" test failures that resulted from using a newer golang compiler?
I am considering just disabling this test, as the rest of the testsuite seem to pass, but I'm getting nervous that this wouldn't just paper over a real issue.