-
Notifications
You must be signed in to change notification settings - Fork 486
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
Issue876Test.Reset is broken #884
Comments
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
|
Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero). I don't understand very well what is the propose of the check. To generate always the same random numbers after a world reset? This is not happening at all. Maybe @nkoenig can help with this, he is listed as the author of the commit (87ccca6). |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). I took a look at this last week. The following patch adds an additional test, and a potential fix to the broken test. I haven't had a chance to test fully.
|
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). I've committed that patch (6ff5ea4) in branch issue_884. Currently it is required to reset the random seed right after loading the world in order to guarantee repeatability. I'm not sure if this satisfies the intent of #876. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). Awesome, thanks. Resetting the seed after loading the world is fine. As long as there is a way to get repeatable behavior. |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). Ok, I'll make a pull request. |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I approved the pull request, but I apparently never tested it, since the test doesn't pass.
I found this in my overnight testing of the gazebo_2.0 branch. It's not in Jenkins yet because gazebo_2.0 hasn't been merged to default recently enough.
The text was updated successfully, but these errors were encountered: