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

Updating Ix-Async to System Interactive and nuget #7623

Merged
merged 10 commits into from
Aug 9, 2016

Conversation

apolcyn
Copy link
Contributor

@apolcyn apolcyn commented Aug 3, 2016

This updates from Ix-Async to System.Interactive.Async, using an updated nuget client.

Unfortunately it seems like the runtime node sections of some test projects need to be in order to workaround some issues with nuget. This is meant to replace #7519

@apolcyn apolcyn force-pushed the sys_inter_with_nuget branch from b4e01c4 to 2717aea Compare August 3, 2016 20:45
@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 3, 2016

No success yet in removing the workaround of removing the runtime nodes in some of the test project project.jsons. Currently planning on going back to make coreclr builds work in a separate PR.

It also seems like dotnet cli has much better support on mac and linux than nuget does, so I think that tests and builds should use that, but this looks like it will require a lot more changes, so planning to do them in a separate PR. #7629

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 3, 2016

test this please

1 similar comment
@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 3, 2016

test this please

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 3, 2016

I think test failures now are flakes.

test this please

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 4, 2016

Most of these failures seem like flakes or issues with dependencies, but some failures in unit tests here look are intermittent, hopefully not due too the async library change...

test this please

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 4, 2016

have not been able to reproduce the error in unit tests on jenkins so far.

test this please

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 4, 2016

test this please

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 5, 2016

failures here now seem to be unrelated build issues. the error on csharp tests seems to be a recurring compiler error of third_party/zlib/gzlib.c, happening mac-node-1.

@@ -35,7 +35,8 @@ setlocal
cd /d %~dp0\..\..

@rem Location of nuget.exe
set NUGET=C:\nuget\nuget.exe
@rem TODO: change this before submitting. This is only for migrating nuget
set NUGET=C:\nuget_temp\nuget.exe
Copy link
Member

Choose a reason for hiding this comment

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

Should this be changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes this should be changed, changing this now

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 8, 2016

test this please

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 8, 2016

Haven't been able to reproduce the failing csharp unit test seen on jenkins. Interop builds seem to be failing in general, but csharp basic tests are passing here.

@apolcyn
Copy link
Contributor Author

apolcyn commented Aug 8, 2016

Have not been able to reproduce the error in unit tests yet. Filed an issue for it here: #7667

@nicolasnoble nicolasnoble merged commit 10776b9 into grpc:v1.0.x Aug 9, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants