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

encoding/gob: fuzz testing failure #3160

Closed
gopherbot opened this issue Feb 29, 2012 · 2 comments
Closed

encoding/gob: fuzz testing failure #3160

gopherbot opened this issue Feb 29, 2012 · 2 comments
Assignees
Milestone

Comments

@gopherbot
Copy link

@gopherbot gopherbot commented Feb 29, 2012

by werner.hattingh:

What steps will reproduce the problem?
1. run go test under pkg/encoding/gob  over and over till fail
2.
3.

What is the expected output?
Pass all the time

What do you see instead?
Test failing

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g

Which operating system are you using?
linux

Which revision are you using?  (hg identify)
2bd4bf330ca5 tip


Please provide any additional information below.
It is a Fuzz test that fails so it is intermittent because of random seed. See attach
file for one that fail with seed value.

Attachments:

  1. test.out (4485 bytes)
@dsymonds
Copy link
Member

@dsymonds dsymonds commented Mar 1, 2012

Comment 1:

Thanks for this.

Labels changed: added priority-go1, packagebug, removed priority-triage.

Owner changed to @dsymonds.

Status changed to Accepted.

@dsymonds
Copy link
Member

@dsymonds dsymonds commented Mar 1, 2012

Comment 2:

This issue was closed by revision 1f0f459.

Status changed to Fixed.

@gopherbot gopherbot added fixed labels Mar 1, 2012
@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.