When comparing traces, I found that the tracks could not match after step 103 in the buggy trace. This is likely because the 'writeJSONString' method was renamed as 'writeJSONStringWithFastJsonConfig', however, Tregression considers them as different methods, as shown in the figure. Therefore, after step 103, the tracks cannot match until the execution of this method exits. The tracks start matching again from step 773 in the buggy trace.
I use tegression and microbat's master branch. This is the project I use: https://pan.baidu.com/s/1pJWqJnUGUpDX1Uh9cCmYZw password：1111
When comparing traces, I found that the tracks could not match after step 103 in the buggy trace. This is likely because the 'writeJSONString' method was renamed as 'writeJSONStringWithFastJsonConfig', however, Tregression considers them as different methods, as shown in the figure. Therefore, after step 103, the tracks cannot match until the execution of this method exits. The tracks start matching again from step 773 in the buggy trace.
I use tegression and microbat's master branch. This is the project I use: https://pan.baidu.com/s/1pJWqJnUGUpDX1Uh9cCmYZw password：1111