Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

PHPC-450: Fix test failures for MongoDB 3.2 #156

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

Merged
jmikola merged 9 commits into mongodb:master from jmikola:phpc-450
Dec 10, 2015
Merged

Conversation

@jmikola
Copy link
Member

@jmikola jmikola commented Dec 9, 2015

@jmikola jmikola force-pushed the phpc-450 branch 2 times, most recently from 31f0124 to f8068c8 Compare December 9, 2015 18:59
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks (and all the same changes above) like something that needs to be split into two tests.
One on pre 3.2, and one 3.2+

Copy link
Member Author

@jmikola jmikola Dec 9, 2015

Choose a reason for hiding this comment

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

Good point. I'll split these and the fail point test to use the 3.0 test server.

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this no longer true?
It used to quite literally (and intentionally) result in an abort() to make sure the getmore failed completely

Copy link
Member Author

@jmikola jmikola Dec 9, 2015

Choose a reason for hiding this comment

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

Oh, it's possible that getMore itself aborts (I don't recall offhand). I thought this was referring to the PHP function itself and sending the configureFailPoint command, which certainly wasn't true.

Copy link
Contributor

Choose a reason for hiding this comment

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

No no, the comment is referring to mongod

Copy link
Member Author

Choose a reason for hiding this comment

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

Got it. I revised the comment below. 👍

@jmikola jmikola force-pushed the phpc-450 branch 3 times, most recently from aa877b3 to 48323ea Compare December 10, 2015 06:36
@jmikola jmikola changed the title (削除) [WIP] PHPC-450: Fix test failures for MongoDB 3.2 (削除ここまで) (追記) PHPC-450: Fix test failures for MongoDB 3.2 (追記ここまで) Dec 10, 2015
Copy link
Contributor

derickr commented Dec 10, 2015

LGTM

@jmikola jmikola force-pushed the phpc-450 branch 2 times, most recently from 67f7d4c to 48323ea Compare December 10, 2015 17:16
This also entails a change to done/end_of_event cursor field assertions. These are internal libmongoc cursor fields and their values aren't relevant to the tests. In the future, we may consider removing them from the Cursor's dump output.
Since isMaster's response varies by server version, we can omit it from expected Server dump output.
The fail point used in this test does not yet support 3.2's getMore command, so this must be run on 3.0 (or earlier). See: SERVER-21831
This change also splits the test into query/command variants, corrects the title (which was apparently copied from cursor-getmore-004.phpt), and removes the use of data fixtures (small documents inserted within the test work just fine for its purposes).
@jmikola jmikola merged commit b64561b into mongodb:master Dec 10, 2015
jmikola added a commit that referenced this pull request Dec 10, 2015
@jmikola jmikola deleted the phpc-450 branch December 10, 2015 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /