Open a-siva opened 3 weeks ago
Once we have a released dev SDK to depend on, I can update the CI jobs etc and push that here.
cc @a-siva @nshahan something seems to be broken with the dart compile js-dev
command on windows? I am not getting a lot of useful information from the GitHub logs though.
cc @a-siva @nshahan something seems to be broken with the
dart compile js-dev
command on windows? I am not getting a lot of useful information from the GitHub logs though.
Will investigate, looks like tests are waiting for temp directories to get deleted but they are in use, could be a test issue.
Will investigate, looks like tests are waiting for temp directories to get deleted but they are in use, could be a test issue.
I think that possibly the worker isn't shutting down like it normally would.
Note that we just send it a sigterm by calling Process.kill
. I don't know how the dart
tool deals with that, and if it can handle shutting down its sub-processes etc.
Note that we just send it a sigterm by calling
Process.kill
. I don't know how thedart
tool deals with that, and if it can handle shutting down its sub-processes etc.
It does not handle shutting down sub-processes, if that is the issue we should also see errors on other platforms (linux, mac)
It does not handle shutting down sub-processes, if that is the issue we should also see errors on other platforms (linux, mac)
Well, only windows won't allow deleting a directory because some sub-process has file handles in that directory still open. So it is possible that is the only reason we don't see the error on other platforms. If the process is left dangling though that is of course bad.
Use the 'dart compile js-dev' command for invoking DDC instead of reaching into the dart-sdk and using the snapshot which is an internal implementation detail of the dart sdk.