Skip to content

[Travis] Do not use legacy mongo ext #24440

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

Closed
wants to merge 1 commit into from

Conversation

chalasr
Copy link
Member

@chalasr chalasr commented Oct 5, 2017

Q A
Branch? 3.4
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets n/a
License MIT
Doc PR n/a

Should make travis green after #24438

@chalasr
Copy link
Member Author

chalasr commented Oct 5, 2017

Remaining failure unrelated.

@nicolas-grekas
Copy link
Member

Fixed in #24409 by a group legacy annotation.

@chalasr
Copy link
Member Author

chalasr commented Oct 5, 2017

@nicolas-grekas But the test should not be marked as legacy, the class itself is not deprecated

@nicolas-grekas
Copy link
Member

Hum indeed... See master where I just removed the group and kept the test class obviously.
The issue with the attached patch is that we should still test with mongo.so in 3.4.
Maybe the legacy group is enough? The class is still tested.

@stof
Copy link
Member

stof commented Oct 5, 2017

Well, we don't have an easy way to make it legacy conditionally (only when tests are running with the old extension). So I would say it is fine for now.

@chalasr
Copy link
Member Author

chalasr commented Oct 5, 2017

👍 fine for me as well

@chalasr chalasr deleted the mongodb-ext-34 branch October 5, 2017 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants