Repository navigation
Conversation
|
39 new or modified tests were run on 7 engines. Test results
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These tests all involve an iterator that violates the iterator protocol by having
.next()either throw or return an object with a throwy.doneor.valuegetter. In these case the.return()method is not called, which the tests were supposed to be catching by having it throw an error and asserting a different error was thrown.But, IteratorClose in the case of an error swallows any errors thrown by
.return(), so they'd never see the one from.return().Work around this by having
.return()set a flag, then asserting it wasn't set.