Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

Fix devserver on windows #327

Closed
wants to merge 19 commits into from

Conversation

devversion
Copy link
Contributor

@devversion devversion commented Nov 24, 2018

No description provided.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

examples/devserver/index.html Outdated Show resolved Hide resolved
devserver/devserver/devserver.go Outdated Show resolved Hide resolved
Copy link
Contributor

@filipesilva filipesilva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM, just failing some tests.

devserver/main.go Outdated Show resolved Hide resolved
@devversion
Copy link
Contributor Author

devversion commented Nov 26, 2018

@alexeagle @gregmagolan @filipesilva This one is ready now. Can you please have a look? thanks!

@devversion devversion changed the title Testing with devserver on windows Fix devserver on windows Nov 27, 2018
@filipesilva
Copy link
Contributor

@googlebot I am ok with my commits being contributed to this project.

Copy link
Contributor

@filipesilva filipesilva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, great work @devversion!

Copy link
Contributor

@alexeagle alexeagle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you minimize the Delta in Go code? This runs in Google3 also. We'll need another reviewer for that part

@devversion
Copy link
Contributor Author

devversion commented Nov 27, 2018

@alexeagle Unfortunately I don't think that I can reduce the diff here. Especially because the Go code is the breaking part for the runfiles on Windows.

The go code currently just assumes that all runfiles are relative to the resolved root directory. This is not the case on Windows, and therefore we now resolve through the Bazel runfile utilities from Go.

Can you elaborate what specific part runs inside of Google3? the whole devserver or just the individual parts like concatjs? I've made concatjs on its own backwards compatible, so it still runs the realFileSystem respecting the passed root directory if no custom file system has been specified.

@alexeagle alexeagle requested a review from evmar December 12, 2018 23:16
@devversion devversion force-pushed the wip/devserver-windows branch 7 times, most recently from 4ea44e3 to 3d38e11 Compare December 22, 2018 16:50
@devversion
Copy link
Contributor Author

The failure of ci/circleci: test is unrelated. Other PRs seem to run into similar flakiness. Probably because of the resources Bazel acquires in the CircleCI containers.

@devversion
Copy link
Contributor Author

@alexeagle If you find some time, could you start the tests again? 😄 (Waiting for a project member to verify this pull request.)

Copy link
Contributor

@evmar evmar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had two minor comments, but I don't think I'm a good reviewer for this anyway so don't let me stop you.

devserver/concatjs/concatjs.go Outdated Show resolved Hide resolved
devserver/concatjs/concatjs.go Outdated Show resolved Hide resolved
@evmar evmar self-requested a review January 8, 2019 20:50
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@alexeagle alexeagle closed this in 4155687 Jan 18, 2019
@alexeagle
Copy link
Contributor

Note, we didn't merge the whole change, still needs another PR to enable the test on windows, by removing:
https://github.com/bazelbuild/rules_typescript/blob/master/.bazelci/presubmit.yml#L54

alexeagle pushed a commit to alexeagle/rules_nodejs that referenced this pull request Oct 17, 2020
Both bazelbuild/rules_typescript#327 and bazelbuild/rules_typescript#378 have circleci `test` jobs being killed:
```
Server terminated abruptly (error code: 14, error message: '', log file: '/home/circleci/.cache/bazel/_bazel_circleci/cced162ff126e466524550c57f0d7df5/server/jvm.out')
```

According to the note in https://github.com/bazelbuild/rules_typescript/blob/3671b8d5b6f5731e191098b6d5243c44f474c0da/.circleci/bazel.rc#L32-L38 this means the memory limit should be reduced.

Closes bazel-contrib#380

PiperOrigin-RevId: 228881108
alexeagle pushed a commit to alexeagle/rules_nodejs that referenced this pull request Oct 18, 2020
Both bazelbuild/rules_typescript#327 and bazelbuild/rules_typescript#378 have circleci `test` jobs being killed:
```
Server terminated abruptly (error code: 14, error message: '', log file: '/home/circleci/.cache/bazel/_bazel_circleci/cced162ff126e466524550c57f0d7df5/server/jvm.out')
```

According to the note in https://github.com/bazelbuild/rules_typescript/blob/845b16ca5f8202df3c3f845df2e9629e85217397/.circleci/bazel.rc#L32-L38 this means the memory limit should be reduced.

Closes bazel-contrib#380

PiperOrigin-RevId: 228881108
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants