-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TestAugment fails on all architectures other than amd64 #80
Comments
Thanks for the report, I've been working on it past weekend. I was focusing on i386 but I'll make it skip on other CPU architectures too. |
@anthonyfok is there any way I can confirm this is good enough before I tag a new release? |
@maruel Wow, that was very quick! Thank you so much!
I'd be happy to test it with Debian infrastructure by including 15e67c5 and other related commits as debian/patches/*.patch, and upload a 2.2.2-2 to Debian and see how it goes. I'll report the results in a day or two (or three). :-) |
Ok thanks, keep me updated and I'll make another commit to skip any test case I would have missed in the first time, then I'll do a v2.3.0 release. |
Here is the test result with panicparse 2.2.2+git20220620.15e67c5-1:
This following patch --- a/stack/source_test.go
+++ b/stack/source_test.go
@@ -606,9 +606,9 @@ func TestAugment(t *testing.T) {
func f(v float64) {
panic("ooh")
}`,
true,
- goarchList{"386"},
+ goarchList{"386", "arm", "mipsle"},
Stack{
Calls: []Call{
newCallSrc(
"main.f", was applied to panicparse 2.2.2+git20220620.15e67c5-2 which built and tested successfully on all relevant architectures, see https://buildd.debian.org/status/package.php?p=panicparse Many thanks! |
Thanks for the update. I'll wait for you to confirm that the tests pass unmodified and I'll release v2.3.0. |
It's good to go: 2.2.2+git20220621.c95a0e4-1 gives green light on all relevant architectures at https://buildd.debian.org/status/package.php?p=panicparse Thanks for fixing the issue! |
All tests TestAugment passes on the amd64 architecture, but some of the tests would fail on all other architectures.
For example, with the recent Debian builds of panicparse 2.2.2-1:
IIRC, the mapping from Debian architecture names to GOARCH are as follows:
GOARCH=arm
GOARCH=386
GOARCH=mips64le
GOARCH=mipsle
GOARCH=ppc64le
Screen capture of overview of Debian build status for panicparse (https://buildd.debian.org/status/package.php?p=panicparse):
Thanks!
The text was updated successfully, but these errors were encountered: