Skip to content

[Vulpix] Abort compilation after maxCompileTime #2318

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

Closed

Conversation

felixmulder
Copy link
Contributor

No description provided.

@DarkDimius
Copy link
Contributor

DarkDimius commented Apr 27, 2017

I think this is a very misleading change.
It doesn't stop the compilation, it stops waiting for it and starts a new one.

@DarkDimius
Copy link
Contributor

Additionally, it blocks the compilation thread and instead uses global future threadpool, ie the number of compilation threads is not controlled using previous means anymore

@felixmulder
Copy link
Contributor Author

Non-constructive feedback. Please rephrase.

@DarkDimius
Copy link
Contributor

While I agree that I could have phrased it differently, I find a sneaky way of putting such changes without documenting them very misleading, hence my reaction.

Constructive version of it was in the original #2125 PR.
The better way to do it would to have compilation slaves as separate VMs so that we are able to kill them.

@felixmulder
Copy link
Contributor Author

Fair enough 😃 let's do this properly then!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants