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
runtime: js-wasm build broken #29632
Comments
I think I have seen this happened a few times on js-wasm. Maybe the js-wasm trybot doesn't run all the tests? |
@cherrymui, indeed: addBuilder(BuildConfig{
Name: "js-wasm",
HostType: "host-js-wasm",
tryBot: explicitTrySet("go"),
ShouldRunDistTest: func(distTest string, isTry bool) bool {
if isTry {
if strings.HasPrefix(distTest, "test:") {
return false
}
if strings.Contains(distTest, "/internal/") ||
strings.Contains(distTest, "vendor/golang.org/x/arch") {
return false
}
switch distTest {
case "cmd/go", "nolibgcc:crypto/x509":
return false
}
return true
}
return true
}, We could shard the js-wasm builder out wider and enable more tests. /cc @dmitshur |
On Wasm, the instruction after the call of sigpanic doesn't increment the PC. Subtracting 1 in Frame.Next makes it pointing to the previous PC, which is the function entry in this case.
If I remember correctly, the stack trace of panic expects the PC of the panic is the call of sigpanic, so we don't advance the PC at that call. But runtime.Caller works differently... Maybe we can advance the PC by 2 at sigpanic, then it would work for both cases? |
Change https://golang.org/cl/157157 mentions this issue: |
(Moved this comment to #29636 (comment).) |
https://go-review.googlesource.com/c/go/+/156657 broke the js-wasm build:
https://build.golang.org/log/e8374fdb14499930386720c7e63a23237eb7128d
The TryBots passed on PS1 but post-cherry-pick it must've had conflicted with something else.
/cc @randall77 @aclements @cherrymui @neelance @tklauser
The text was updated successfully, but these errors were encountered: