go: runtime: failure in `TestRaiseException` on windows-amd64-2012
--- FAIL: TestRaiseException (0.02s)
crash_test.go:106: C:\Users\gopher\AppData\Local\Temp\1\go-build1560626842\testprog.exe RaiseException exit status: exit status 2989
syscall_windows_test.go:636: No stack trace:
FAIL
FAIL runtime 68.703s
greplogs --dashboard -md -l -e 'FAIL: TestRaiseException'
2021-11-18T02:19:50-f1cc529/windows-amd64-2012
The test dates from 2014. I can find only one such faillure in the logs, and it is very recent — marking as release-blocker until we can determine whether this is a regression (CC @bufflig).
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 43 (37 by maintainers)
Commits related to this issue
- testing: skip flaky TestRaiseException on windows-amd64-2012 This is in relation to #49681 Change-Id: I32ad8b506cf8fb0a94b15c3cc8b1eaf5af728c59 Reviewed-on: https://go-review.googlesource.com/c/go/+... — committed to golang/go by bufflig 2 years ago
- testing: skip flaky TestRaiseException on windows-amd64-2012 This is in relation to #49681 Change-Id: I32ad8b506cf8fb0a94b15c3cc8b1eaf5af728c59 Reviewed-on: https://go-review.googlesource.com/c/go/+... — committed to jproberts/go by bufflig 2 years ago
- runtime: skip TestVectoredHandlerExceptionInNonGoThread windows-amd-2012 builder seems to have some problems handling exception thrown in external C code which is affecting TestVectoredHandlerExcepti... — committed to golang/go by qmuntal 2 years ago
- runtime: skip TestVectoredHandlerExceptionInNonGoThread windows-amd-2012 builder seems to have some problems handling exception thrown in external C code which is affecting TestVectoredHandlerExcepti... — committed to TroutSoftware/go by qmuntal 2 years ago
- testing: skip flaky TestRaiseException on windows-amd64-2012-* Modify skip rule for TestRaiseException to trigger on both the base builder (windows-amd64-2012) and the newcc canary builder (windows-a... — committed to golang/go by thanm 2 years ago
- testing: skip TestVectoredHandlerExceptionInNonGoThread on windows-amd64-2012-* Modify skip rule for TestVectoredHandlerExceptionInNonGoThread to trigger on both the base builder (windows-amd64-2012)... — committed to golang/go by thanm 2 years ago
- testing: skip flaky TestRaiseException on windows-amd64-2012-* Modify skip rule for TestRaiseException to trigger on both the base builder (windows-amd64-2012) and the newcc canary builder (windows-a... — committed to felixge/go by thanm 2 years ago
- testing: skip TestVectoredHandlerExceptionInNonGoThread on windows-amd64-2012-* Modify skip rule for TestVectoredHandlerExceptionInNonGoThread to trigger on both the base builder (windows-amd64-2012)... — committed to felixge/go by thanm 2 years ago
Ah, right - I see how my idea/thought would not work. Thanks!
@hanchaoqun Yea, I was wondering if dumping the stack trace directly when !isgoexception was possible. I don’t really know the reason we’re using both exceptionhandlers and continuehandlers, but I assume there’s a reason. Anyone has any knowledge of the history behind that?
@bcmills - I did add skipping the test case as flaky, should we remove the release blocker tag?