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

[TEST] Refactor RPC test to isolate runs into a sub-function #8656

Merged
merged 1 commit into from
Aug 5, 2021

Conversation

tqchen
Copy link
Member

@tqchen tqchen commented Aug 4, 2021

We kill the rpc server in the del function. When a server
co-exist with remote resources in the same function scope,
the destruction order is not determined.

This can cause server to be destructed before the actual remote array.
As a side effect, it can cause sometime test to timeout due to
waiting on the socket.

We kill the rpc server in the del function. When a server
co-exist with remote resources in the same function scope,
the destruction order is not determined.

This can cause server to be destructed before the actual remote array.
As a side effect, it can cause sometime test to timeout due to
waiting on the socket.
Copy link
Member

@junrushao junrushao left a comment

Choose a reason for hiding this comment

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

This theory definitely makes sense to me :-)

@areusch
Copy link
Contributor

areusch commented Aug 4, 2021

this makes sense to me, but even better would be to create either a test fixture or context manager to wrap the server. then we can reason even better about when it should be destroyed, particularly with xdist.

@areusch areusch merged commit 36bb629 into apache:main Aug 5, 2021
mehrdadh pushed a commit to mehrdadh/tvm that referenced this pull request Aug 11, 2021
…8656)

We kill the rpc server in the del function. When a server
co-exist with remote resources in the same function scope,
the destruction order is not determined.

This can cause server to be destructed before the actual remote array.
As a side effect, it can cause sometime test to timeout due to
waiting on the socket.
ylc pushed a commit to ylc/tvm that referenced this pull request Sep 29, 2021
…8656)

We kill the rpc server in the del function. When a server
co-exist with remote resources in the same function scope,
the destruction order is not determined.

This can cause server to be destructed before the actual remote array.
As a side effect, it can cause sometime test to timeout due to
waiting on the socket.
ylc pushed a commit to ylc/tvm that referenced this pull request Jan 13, 2022
…8656)

We kill the rpc server in the del function. When a server
co-exist with remote resources in the same function scope,
the destruction order is not determined.

This can cause server to be destructed before the actual remote array.
As a side effect, it can cause sometime test to timeout due to
waiting on the socket.
apivovarov pushed a commit to apivovarov/tvm that referenced this pull request May 8, 2022
…8656)

We kill the rpc server in the del function. When a server
co-exist with remote resources in the same function scope,
the destruction order is not determined.

This can cause server to be destructed before the actual remote array.
As a side effect, it can cause sometime test to timeout due to
waiting on the socket.
apivovarov added a commit to neo-ai/tvm that referenced this pull request May 8, 2022
* [Jenkins] Use 8 and 16 jobs to build for GPU and CPU

* [TEST] Refactor RPC test to isolate runs into a sub-function (apache#8656)

We kill the rpc server in the del function. When a server
co-exist with remote resources in the same function scope,
the destruction order is not determined.

This can cause server to be destructed before the actual remote array.
As a side effect, it can cause sometime test to timeout due to
waiting on the socket.

Co-authored-by: Tianqi Chen <tqchen@users.noreply.github.com>
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.

3 participants