-
Notifications
You must be signed in to change notification settings - Fork 18k
test: all codegen tests are skipped #48247
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
Comments
cc @mdempsky |
Change https://golang.org/cl/348390 mentions this issue: |
Change https://golang.org/cl/348391 mentions this issue: |
Change https://golang.org/cl/348392 mentions this issue: |
Once the three CLs above are merged I believe the codegen tests can be re-enabled with the patch in the issue description. |
This test is not executed by default (see #48247) and does not actually pass. It was added in CL 346689. The code generation changes made in that CL only change how instructions are assembled, they do not actually affect the output of the compiler. This test is unfortunately therefore invalid and will never pass. Updates #48247. Change-Id: I0c807e4a111336e5a097fe4e3af2805f9932a87f Reviewed-on: https://go-review.googlesource.com/c/go/+/348390 Trust: Michael Munday <[email protected]> Run-TryBot: Michael Munday <[email protected]> Reviewed-by: Cherry Mui <[email protected]> TryBot-Result: Go Bot <[email protected]>
The codegen tests are currently skipped (see #48247) and the bitfield tests do not actually compile due to a duplicate function name (sbfiz5) added in CL 267602. Renaming the function fixes the issue. Updates #48247. Change-Id: I626fd5ef13732dc358e73ace9ddcc4cbb6ae5b21 Reviewed-on: https://go-review.googlesource.com/c/go/+/348391 Trust: Michael Munday <[email protected]> Run-TryBot: Michael Munday <[email protected]> TryBot-Result: Go Bot <[email protected]> Reviewed-by: Cherry Mui <[email protected]>
The codegen tests are currently skipped (see #48247). The test added in CL 346050 did not compile because it was in the main package but did not contain a main function. Changing the package to 'codegen' fixes the issue. Updates #48247. Change-Id: I0a0eaca8e6a7d7b335606d2c76a204ac0c12e6d5 Reviewed-on: https://go-review.googlesource.com/c/go/+/348392 Trust: Michael Munday <[email protected]> Run-TryBot: Michael Munday <[email protected]> Reviewed-by: Cherry Mui <[email protected]> TryBot-Result: Go Bot <[email protected]>
Thanks, I forgot that AsmCheck was skipped for -G=3. I'll send a fix. |
Change https://golang.org/cl/348671 mentions this issue: |
Change https://golang.org/cl/348670 mentions this issue: |
This ensures that diagnostics for files within $GOROOT continue to be reported using their full filepath, rather than the abbreviated filepath. Notably, this is necessary for test/run.go, which has tests that expect to see the full filepath. Updates #48247. Change-Id: I440e2c6dd6109ca059d81cee49e476bba805d703 Reviewed-on: https://go-review.googlesource.com/c/go/+/348670 Trust: Matthew Dempsky <[email protected]> Run-TryBot: Matthew Dempsky <[email protected]> Reviewed-by: Robert Griesemer <[email protected]> TryBot-Result: Go Bot <[email protected]>
Apologies if this is a duplicate issue, I couldn't find an appropriate one. I was surprised by this behaviour so I wanted to make sure it was flagged even if it is behaving as expected during the register ABI transition.
I think this behaviour was introduced by CL 320609. The issue can be worked around (albeit with a test failure on amd64) by applying the following patch:
Is it worth skipping any failing tests explicitly and then re-enabling the rest? Most of the tests pass fine.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Not tried.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Tests executing.
What did you see instead?
Tests skipped:
The text was updated successfully, but these errors were encountered: