Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

[DO NOT MERGE] Testing subrepo by branch #13378

Closed
wants to merge 3 commits into from

Conversation

KellenSunderland
Copy link
Contributor

[DO NOT MERGE] Testing subrepo by branch

@stu1130
Copy link
Contributor

stu1130 commented Nov 23, 2018

@mxnet-label-bot add [pr-work-in-progress]
Thanks for your contribution @KellenSunderland

@marcoabreu marcoabreu added the pr-work-in-progress PR is still work in progress label Nov 23, 2018
.gitmodules Outdated
[submodule "3rdparty/tvm"]
path = 3rdparty/tvm
url = https://github.com/dmlc/tvm
[submodule "3rdparty/onnx-tensorrt"]
path = 3rdparty/onnx-tensorrt
url = https://github.com/onnx/onnx-tensorrt.git
[submodule "nvidia_cub"]
path = nvidia_cub
Copy link
Contributor

Choose a reason for hiding this comment

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

Should be 3rdparty/nvidia_cub (or just leave it as cub). THat's probably why Ci is failing :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

doh.

@marcoabreu
Copy link
Contributor

I know you don't intend to merge this, but do you mind explaining why we rename the folders instead of just updating the repository link? Is there any technical reason or is the idea to just separate the old and the new version?

@KellenSunderland
Copy link
Contributor Author

KellenSunderland commented Nov 23, 2018

@marcoabreu Yeah it's a good question. It's actually explained really well in the main PR that prompted me to open this pr: #13322

Basically what I'm testing in this PR is to see if there's any way we can avoid taking down everyone's build and CI whenever there's a force push in a submodule. So far it seems like even if we track a branch it hard codes some sha1 somewhere, so I'm not sure if it's possible.

BTW, real test of this PR will be that once it builds I'll add a third dummy submodule, and then I'll force push to it in a branch to see what happens.

@marcoabreu
Copy link
Contributor

Anton submitted a patch to make CI resilient against submodule problems. That should be fine now.

But yeah it's a good point about developers. In the end, they have to update the submodules anyway. Hmmm, hard choice

@marcoabreu
Copy link
Contributor

Gotcha, thanks for the explanation. I'm really curious :)

@vandanavk
Copy link
Contributor

@mxnet-label-bot add [Build]

@roywei
Copy link
Member

roywei commented Dec 11, 2018

@KellenSunderland ping for update. Is this PR still needed? Thanks

@KellenSunderland
Copy link
Contributor Author

PR not needed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pr-work-in-progress PR is still work in progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants