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

fix gpr_stack_lockfree_test assert bug on 64 bits #4484

Merged
merged 2 commits into from
Dec 16, 2015

Conversation

ksophocleous
Copy link
Contributor

this fixes issue #4483

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@grpc-kokoro
Copy link

Can one of the admins verify this patch?

2 similar comments
@grpc-kokoro
Copy link

Can one of the admins verify this patch?

@grpc-kokoro
Copy link

Can one of the admins verify this patch?

@ksophocleous
Copy link
Contributor Author

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

@ctiller
Copy link
Member

ctiller commented Dec 16, 2015

This is OK to test

@ctiller
Copy link
Member

ctiller commented Dec 16, 2015

Thanks for the fix! A couple of style nits and then this is good to go.

@ksophocleous
Copy link
Contributor Author

yeah sure, just a moment

@ksophocleous
Copy link
Contributor Author

the error in Basic tests seems unrelated to anything I have done.

ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2332) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2801) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

@ctiller
Copy link
Member

ctiller commented Dec 16, 2015

Yeah it's completely unrelated

On Wed, Dec 16, 2015, 9:35 AM Konstantinos Sofokleous <
notifications@github.com> wrote:

the error in Basic tests seems unrelated to anything I have done.

ERROR: Connection was broken: java.io.IOException: Unexpected termination
of the channel
at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2332)
at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2801)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801)
at java.io.ObjectInputStream.(ObjectInputStream.java:299)
at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
at
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)


Reply to this email directly or view it on GitHub
#4484 (comment).

ctiller added a commit that referenced this pull request Dec 16, 2015
…e_test

fix gpr_stack_lockfree_test assert bug on 64 bits
@ctiller ctiller merged commit 9e38c21 into grpc:master Dec 16, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Jan 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants