go: all: test failures with `_assert(): stream.sputn` on ios-arm64-corellium
#!watchflakes
post <- log ~ `_assert\(\): stream\.sputn`
Issue created automatically to collect these failures.
Example (log):
--- FAIL: TestLargeReloc (6.78s)
link_test.go:1094: build failed: exit status 1. output:
# command-line-arguments
/tmp/workdir-host-ios-arm64-corellium-ios/go/pkg/tool/ios_arm64/link: running /var/root/bin/clangwrap failed: exit status 1
../ldid.cpp(534): _assert(): stream.sputn(static_cast<const char *>(data) + total, writ) == writ
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
link_test.go:1101: build failed: exit status 1. output:
# command-line-arguments
/tmp/workdir-host-ios-arm64-corellium-ios/go/pkg/tool/ios_arm64/link: running /var/root/bin/clangwrap failed: exit status 1
../ldid.cpp(534): _assert(): stream.sputn(static_cast<const char *>(data) + total, writ) == writ
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 16 (6 by maintainers)
Even if the Go toolchain is invoking the system linker incorrectly, it should be erroring out cleanly, but this is clearly an internal assert failing. It could also be something wrong with the platform because it’s a write call that’s failing.