Skip to content
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

Closed
anthonyfok opened this issue Jun 20, 2022 · 7 comments
Closed

TestAugment fails on all architectures other than amd64 #80

anthonyfok opened this issue Jun 20, 2022 · 7 comments
Assignees

Comments

@anthonyfok
Copy link

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:

Test Architectures on which the test failed
TestAugment/0-local_function_doesn't_interfere arm64, armel, armhf, ppc64el, riscv64
TestAugment/1-func armel, armhf
TestAugment/12-string arm64, armel, armhf, ppc64el, riscv64
TestAugment/13-string_and_int arm64, armel, armhf, ppc64el, riscv64
TestAugment/16-error_unnamed arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, riscv64, s390x
TestAugment/24-argument_offsets_partially_too_large armel, armhf, i386, mipsel
TestAugment/25-argument_offsets_entirely_too_large armel, armhf, i386, mipsel

IIRC, the mapping from Debian architecture names to GOARCH are as follows:

  • armel and armhf ⇒ GOARCH=arm
  • i386 ⇒ GOARCH=386
  • mips64el ⇒ GOARCH=mips64le
  • mipsel ⇒ GOARCH=mipsle
  • ppc64el ⇒ GOARCH=ppc64le

Screen capture of overview of Debian build status for panicparse (https://buildd.debian.org/status/package.php?p=panicparse):

image

Thanks!

@maruel
Copy link
Owner

maruel commented Jun 20, 2022

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.

@maruel maruel self-assigned this Jun 20, 2022
@maruel maruel closed this as completed in 15e67c5 Jun 20, 2022
@maruel
Copy link
Owner

maruel commented Jun 20, 2022

@anthonyfok is there any way I can confirm this is good enough before I tag a new release?

@anthonyfok
Copy link
Author

@maruel Wow, that was very quick! Thank you so much!

is there any way I can confirm this is good enough before I tag a new release?

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). :-)

@maruel maruel reopened this Jun 20, 2022
@maruel
Copy link
Owner

maruel commented Jun 20, 2022

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.

@anthonyfok
Copy link
Author

Here is the test result with panicparse 2.2.2+git20220620.15e67c5-1:

image

Test Architectures on which the test needs to be skipped
TestAugment/18-float64 armel, armhf, i386, mipsel (GOARCH 386, arm, mipsle)

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!

@maruel maruel closed this as completed in c95a0e4 Jun 21, 2022
@maruel
Copy link
Owner

maruel commented Jun 21, 2022

Thanks for the update. I'll wait for you to confirm that the tests pass unmodified and I'll release v2.3.0.

@anthonyfok
Copy link
Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants