Does not panic upon division by zero when assigned to _. #551
Labels
Comments
dmitshur
added a commit
that referenced
this issue
Dec 13, 2016
There were 3 failing tests. One was a modified old test that wasn't previously run due to a build constraint (that has been removed in 1.8). It fails due to a compiler bug, see #551 that tracks it. Two were new tests that use unsupported packages/funcs (such as "unsafe", runtime.FuncForPC, runtime.Callers) and failed as a result.
dmitshur
added a commit
that referenced
this issue
Dec 13, 2016
There were 3 failing tests. One was a modified old test that wasn't previously run due to a build constraint (that has been removed in 1.8). It fails due to a compiler bug, see #551 that tracks it. Two were new tests that use unsupported packages/funcs (such as "unsafe", runtime.FuncForPC, runtime.Callers) and failed as a result.
dmitshur
added a commit
that referenced
this issue
Dec 14, 2016
There were 3 failing tests. One was a modified old test that wasn't previously run due to a build constraint (that has been removed in 1.8). It fails due to a compiler bug, see #551 that tracks it. Two were new tests that use unsupported packages/funcs (such as "unsafe", runtime.FuncForPC, runtime.Callers) and failed as a result.
dmitshur
added a commit
that referenced
this issue
Jan 5, 2017
There were 3 failing tests. One was a modified old test that wasn't previously run due to a build constraint (that has been removed in 1.8). It fails due to a compiler bug, see #551 that tracks it. Two were new tests that use unsupported packages/funcs (such as "unsafe", runtime.FuncForPC, runtime.Callers) and failed as a result.
|
Fixed by f347191. |
dmitshur
added a commit
that referenced
this issue
Feb 16, 2017
There were 3 failing tests. One was a modified old test that wasn't previously run due to a build constraint (that has been removed in 1.8). It fails due to a compiler bug, see #551 that tracks it. Two were new tests that use unsupported packages/funcs (such as "unsafe", runtime.FuncForPC, runtime.Callers) and failed as a result.
dmitshur
added a commit
that referenced
this issue
Feb 16, 2017
There were 3 failing tests. One was a modified old test that wasn't previously run due to a build constraint (that has been removed in 1.8). It fails due to a compiler bug, see #551 that tracks it. Two were new tests that use unsupported packages/funcs (such as "unsafe", runtime.FuncForPC, runtime.Callers) and failed as a result.
8 tasks
dmitshur
referenced
this issue
Feb 17, 2017
dmitshur
added a commit
that referenced
this issue
Jun 25, 2017
The fixedbugs/issue19182.go test requires GOMAXPROCS=2, otherwise it never terminates. Avoid running it, since GopherJS only supports GOMAXPROCS=1. The fixedbugs/issue19246.go case looks similar to #551. /cc @neelance Check knownFails table before potentially setting test.err to nil for skip errors. Otherwise the never-terminate skip tests get incorrectly classified as "unok" instead of "knfl".
dmitshur
added a commit
that referenced
this issue
Aug 25, 2017
The fixedbugs/issue19182.go test requires GOMAXPROCS=2, otherwise it never terminates. Avoid running it, since GopherJS only supports GOMAXPROCS=1. The fixedbugs/issue19246.go case looks similar to #551. /cc @neelance Check knownFails table before potentially setting test.err to nil for skip errors. Otherwise the never-terminate skip tests get incorrectly classified as "unok" instead of "knfl".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following program panics when compiled using
gc:It does not panic when compiled with GopherJS.
This is the same issue as golang/go#18024 upstream, and it was uncovered by me when working on go1.8 branch thanks to golang/go@c2bb52b causing
fixedbugs/issue8613.gotest to run as part ofTestGoRepositoryCompilerTests.Low priority, I'm reporting for tracking purposes.
The text was updated successfully, but these errors were encountered: