8000 Upgrade development dependencies by nulltoken · Pull Request #1138 · libgit2/libgit2sharp · GitHub
[go: up one dir, main page]

Skip to content

Upgrade development dependencies #1138

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

Merged
merged 2 commits into from
Jul 4, 2015
Merged

Upgrade development dependencies #1138

merged 2 commits into from
Jul 4, 2015

Conversation

nulltoken
Copy link
Member

No description provided.

@nulltoken nulltoken force-pushed the ntk/nuget_deps branch 7 times, most recently from 8e56dae to 2e5e030 Compare July 4, 2015 12:11
@nulltoken
Copy link
Member Author

🎉 Finally! It's passing....

This mainly upgrades to test runners to xUnit 2.0 and fixes some shadow-copy related issues that I've discovered while working on this.

/cc @carlosmn @bording @Therzok

@Therzok
Copy link
Member
Therzok commented Jul 4, 2015

👍

nulltoken added a commit that referenced this pull request Jul 4, 2015
Upgrade development dependencies
@nulltoken nulltoken merged commit 126351e into vNext Jul 4, 2015
@nulltoken nulltoken deleted the ntk/nuget_deps branch July 4, 2015 14:27
@@ -56,8 +56,10 @@ private static void SetUpTestEnvironment()
{
IsFileSystemCaseSensitive = IsFileSystemCaseSensitiveInternal();

string initialAssemblyParentFolder = Directory.GetParent(new Uri(Assembly.GetExecutingAssembly().EscapedCodeBase).LocalPath).FullName;
Copy link
Member Author

Choose a reason for hiding this comment

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

/cc @cmn @bording @Therzok This change somehow bit me in the back. During the last hour I've randomly seen passing/failing build runs on Travis due to this. Any idea? 🙏

Latest failure is at https://travis-ci.org/libgit2/libgit2sharp/jobs/69555887

Copy link
Member

Choose a reason for hiding this comment

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

There are so many parts here that have changed in a short period of time, I'm not sure where to start!

@nulltoken In addition to the xunit 2.0 changes here, I see that you've also bumped up to a NativeBinaries package that includes the changes I made there recently, and it also has a new libgit2 version along with my changes.

Any idea when the failures started? Before or after the new NativeBinaries update?

Copy link
Member

Choose a reason for hiding this comment

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

The problems come from the fixture not being able to find the resources path. It ends up deleting two components from the path, which indicates that it's taking the source dir path instead of where the dll is located as the first path.

Copy link
Member Author

Choose a reason for hiding this comment

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

This started strangely with this very PR. Before the merge, everything was green. Once merge vNext failed on Travis/Mac with the same mangled path error. I restarted the build and... It passed. In the native binaries PR, I've tried to change the way the assembly location was identified. This seemed to be working.... Until this one. It looks like everything is related to xUnit shadow copying. IIRC you introduced this because of an issue I cannot remember of.

Copy link
Member

Choose a reason for hiding this comment

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

Ok, I think I've figured out what's going on here. PR with more details coming soon!

Copy link
Member Author

Choose a reason for hiding this comment

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

❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0