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

Noise in Spatial Tournament #677

Closed
wants to merge 7 commits into from
Closed

Noise in Spatial Tournament #677

wants to merge 7 commits into from

Conversation

Nikoleta-v3
Copy link
Member

Closes #673

The bug seems to have been my fault as I was not passing the argument noise to either
the SpatialMatches generator or the SpatialTournament class.

It has been corrected and also I added a test for the noise in the test_match_generator arcooding to @drvinceknight work in the TestProbEndSpatialTournament.

Locally all 1595 tests seems to be running fine. Let's see what Travis has to say.

@@ -44,7 +44,7 @@ def test_len(self):
with self.assertRaises(NotImplementedError):
len(tt)

def test_build_match_params(self):
def _params(self):
Copy link
Member

Choose a reason for hiding this comment

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

you seem to have lost test_build_match_. I expect this test was not running (always make sure your test fails before it passes :)).

@marcharper
Copy link
Member

marcharper commented Aug 2, 2016

@Nikoleta-v3 Please see the PR that I opened on your branch.

We need to add a test that actually runs a spatial tournament to catch the bug I just fixed...

@drvinceknight
Copy link
Member

We need to add a test that actually runs a spatial tournament to catch the bug I just fixed...

I wondered how the doctest caught something our unit tests didn't... Any idea why this test does not catch whatever the bug was: https://github.com/Axelrod-Python/Axelrod/blob/master/axelrod/tests/unit/test_tournament.py#L621

(Haven't really spoken to @Nikoleta-v3 today, I know she's busy with some writing.)

@marcharper
Copy link
Member

I'm not sure really but it was a tuple unpacking issue for match chunks so I would think that one of the other tests would have invoked it.

@drvinceknight
Copy link
Member

Strange. Definitely worth including the example from the doc test as a unit test to make sure it doesn't happen again (and that we're not counting on the doctests to find bugs) :)

@drvinceknight
Copy link
Member

I have opened https://github.com/Nikoleta-v3/Axelrod/pull/2 with the tests that I feel are necessary. Note that I opened that to your master branch as I didn't go through your fixes: we can chat about this when we catch up today.

@drvinceknight
Copy link
Member

Have spoken to @Nikoleta-v3 and she's asked that I just submit my fix to this as she's had a bunch of data back that needs analysing. I'm closing this and about to open another PR.

@Nikoleta-v3
Copy link
Member Author

@marcharper Thank you for the comments ! I read everything through 😄

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