Skip to content

Conversation

@petertseng
Copy link
Member

As part of the work to have consistency between tracks as in https://github.com/exercism/todo/issues/104 and https://github.com/exercism/todo/issues/13. Comments are in individual commit messages.

@petertseng
Copy link
Member Author

Interesting that the CI is failing. The flake failures are files untouched by me. I ran tests locally and this worked, so I know this exercise is fine. But something changed in the past 16 days. Maybe flake added new tests?

@petertseng
Copy link
Member Author

Seems unlikely. flake8 hasn't changed either at https://gitlab.com/pycqa/flake8/commits/master . So I am stumped.

@petertseng
Copy link
Member Author

Tested an empty commit on master. That also fails. Guess we gotta get those fixed up. I really do wonder what changed...

E: Ah. The combination of flake8 forbidding 1.6 but pep8 releasing 1.7 means that now flake8 is now checking things it wasn't checking before. Guess we just have to comply with new rules now.

The original tests had tests for "" and 0.
This is when both inputs are the boundary condition.
Now we should also test when only one input is at the boundary.
So we should test a non-empty string with 0, and "" with a nonzero span.

These are consistent with the values defined in
https://github.com/exercism/x-common/blob/master/largest-series-product.json
In these cases, the result should be 0 as well. This guards against
solutions that assume the minimum is 1.
@petertseng
Copy link
Member Author

Rebased on master. Should be fine now.

behrtam added a commit that referenced this pull request Jan 26, 2016
largest-series-product corner cases
@behrtam behrtam merged commit 396be32 into exercism:master Jan 26, 2016
@behrtam
Copy link
Contributor

behrtam commented Jan 26, 2016

Looks good. Thanks for your effort.

@petertseng petertseng deleted the lsp-corner branch January 26, 2016 10:53
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.

2 participants