Skip to content
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

[Internal] Normalize trailing slash on failing test by using path.resolve #392

Closed

Conversation

darrylhodgins
Copy link
Contributor

No description provided.

@darrylhodgins
Copy link
Contributor Author

Thought that might help, but there's some kind of permissions thing going on with Appveyor. Hmm…

@lukebatchelor
Copy link
Contributor

I was getting the same thing but only on 1 of 5 builds. As a workaround, I amended the previous commit and force pushed a couple of times and it worked eventually.

@jamiebuilds
Copy link
Contributor

There do seem to be valid errors in the AppVeyor results https://ci.appveyor.com/project/lerna/lerna/build/1.0.201/job/f6ngx7r1msgcotve#L1069

bclinkinbeard and others added 3 commits November 16, 2016 11:41
… package.json (lerna#393)

* Expect packages config to be an array of glob patterns to directories containing package.json

* Mention packages config in README

* Attempt to avoid test failures on Appveyor
@jamiebuilds jamiebuilds changed the title Normalize trailing slash on failing test by using path.resolve [Internal] Normalize trailing slash on failing test by using path.resolve Nov 16, 2016
@jamiebuilds
Copy link
Contributor

jamiebuilds commented Nov 16, 2016

I'm sorry dude... I don't know what is happening in AppVeyor.

@gigabo gigabo force-pushed the config-locations branch 7 times, most recently from 1c76b71 to af4a738 Compare December 14, 2016 19:50
@evocateur
Copy link
Member

I'm pretty sure we already have most, if not all of the changes from this PR.

@evocateur evocateur closed this Mar 17, 2017
@darrylhodgins darrylhodgins deleted the config-locations branch August 7, 2017 14:20
@lock
Copy link

lock bot commented Dec 27, 2018

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants