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

Possible init manifest bug #283

Closed
tro3 opened this issue Mar 4, 2017 · 1 comment
Closed

Possible init manifest bug #283

tro3 opened this issue Mar 4, 2017 · 1 comment
Labels

Comments

@tro3
Copy link
Contributor

tro3 commented Mar 4, 2017

An unexpected behavior found during adding integration tests. Test cases mentioned are in #265, which will make this hard to follow. I just want to log it here so it is not buried in the #265 discussion.

In the test cases init/case2 and init/case3, there are two code files, the first of which references the second and one of two fixed remote repos. That repo and the second code file each reference the second remote repo. In case2, only the second repo is previously imported, and init results in a manifest with only the second repo present. In case3, only the first repo is previously imported, yet both repos show up in the manifest. One or the other seems incorrect.

@tro3
Copy link
Contributor Author

tro3 commented Mar 11, 2017

Holding for upgraded init definition

@tro3 tro3 closed this as completed Mar 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants