-
Notifications
You must be signed in to change notification settings - Fork 909
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
remove thread-safe wrapper #1315
base: dev
Are you sure you want to change the base?
Conversation
log:
|
#1299 log: windows (azure pipelines) : 96.496s linux (circleci) : 70.762s macos (circleci) : 84.500s |
So this should work now I think since we now self-exec to run the linker in a separate process. |
Some items failed on windows only.
|
This Windows failure may be a race condition in loader/goroot.go, which I've fixed here: #1316 Overall I think it should be fine to run these builds in parallel. The only possible issue is CGo, but at least on Windows, CGo is already serialized because of problems in the LLVM build. |
Do we need to remove only for windows to get this to pass Azure tests? |
I think the test passes by excluding windows. Alternatively, when #1316 is resolved, I think the windows test will pass. |
I would personally much rather fix the issue than work around it. The Windows issue looks like an actual bug, that's hopefully fixed with #1316. If that PR doesn't fix it, I'll look further into it. |
It's a little less, but it still seems to be an error.
|
I tested on Windows and found the underlying issue(s): #1325 |
@sago35 you should be able to rebase the |
I'm not sure why the test failed, but it might be a concurrency issue. |
@sago35 can you maybe try rebasing this on the dev branch? I think it will work now. |
|
@aykevl
build-linux log:
|
Huh, that are some weird errors. Maybe it's best to simply retry the build. |
Yet another iteration of this is included in #2412 (I lost track of how many PRs i had made to try to fix this in the past), which is stable now, so I think this PR may no longer be needed? |
This PR is for confirmation purposes only.
Although the following is written in the source code, it may be possible to run it parrallel in practice.
In my hand, the test has finished without any failure.
before : 47 sec
after : 8 sec