You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Install go-mutesting following the instructions in the repository's README.
Run the following command: go-mutesting ast/ast.go
Observe the output.
Expected Behavior:
The output should show the specific location of the code that was mutated, similar to what I saw when I first ran the tool.
Actual Behavior:
Instead of showing the mutated location, the tool outputs a diff of the entire file.
Initially, it was showing the correct specific mutations, but now it consistently outputs the whole file diff.
I haven't changed any configurations since the first successful run.
Additional Information:
No changes were made to the go-mutesting setup between the time it worked correctly and when the issue started.
I attempted re-running the tool and checked other files, but the same behavior persists.
Could you please help me investigate this issue? Any suggestions on how to restore the previous behavior or debug this?
Thank you!
ubuntu_5RzUS61maK.mp4
The text was updated successfully, but these errors were encountered:
Go version:
go1.23.0 linux/amd64
Steps to Reproduce:
go-mutesting ast/ast.go
Expected Behavior:
The output should show the specific location of the code that was mutated, similar to what I saw when I first ran the tool.
Actual Behavior:
Instead of showing the mutated location, the tool outputs a diff of the entire file.
Initially, it was showing the correct specific mutations, but now it consistently outputs the whole file diff.
I haven't changed any configurations since the first successful run.
Additional Information:
No changes were made to the go-mutesting setup between the time it worked correctly and when the issue started.
I attempted re-running the tool and checked other files, but the same behavior persists.
Could you please help me investigate this issue? Any suggestions on how to restore the previous behavior or debug this?
Thank you!
ubuntu_5RzUS61maK.mp4
The text was updated successfully, but these errors were encountered: