I manually tested all the pytest consumers and if there is more to
check that I dont see, I can report back more testing.
The thing is that as times goes by, the tests already made become
insubstantial because for example I tested all for pytest 3.6.3, now
we are in pytest 3.6.4.
I commit to have the pytest suite up to date and check the changelogs
to warn and foresee any possible problems.
Thanks for the comment and the explanation about why this is not been committed.
I'll wait then.
Elias.
2018-08-02 13:41 GMT-03:00 Stuart Henderson <stu@spacehopper.org>:
> On 2018/08/02 11:11, Elias M. Mariani wrote:
>> Stuart, Remi,
>> Could you help me with this ?
>> I dont want the updates to get any bigger as times goes by and the
>> changes were extensively tested.
>
> This is a wanted update but between py2 and py3 dep's there are 200+
> fullpkgpaths involved, so it is likely to take a while for a developer to
> have time to fit in enough testing to gain confidence to commit it.
>
>
>> Cheers.
>> Elias.
>>
>>
>> 2018-07-30 20:20 GMT-03:00 Elias M. Mariani <marianielias@gmail.com>:
>> > Updating the update.
>> > All the following changes were tested again, this time against
>> > databases/py-sqlalchemy,python3
>> > 1 failed, 7809 passed, 888 skipped
>> >
>> > The same result as the current, version, the previous update and the
>> > current update.
>> > (The test uses py-test-xdist, and is very complete)
>> >
>> > added also
>> > devel/py-pluggy
>> > Update from 0.6.0 to 0.7.1
>> > https://github.com/pytest-dev/pluggy/blob/master/CHANGELOG.rst
>> > Not a single function removed, only deprecated. (the only real
>> > consumer is devel/py-test).
>> >
>> > 2018-07-26 15:13 GMT-03:00 Elias M. Mariani <marianielias@gmail.com>:
>> >> Moving the thread just to change the title to something more descriptive.
>> >>
>> >> Hi,
>> >> I have the following list of ports, all share interdependencies
>> >> between them, thats why I think that the best would be to commit the
>> >> hole thing together.
>> >> I'm talking about py-test.
>> >> I have the diff ready to update:
>> >> devel/py-hypothesis
>> > Further update from 3.66.1 to 3.66.14
>> > https://hypothesis.readthedocs.io/en/master/changes.html
>> > Mostly performance upgrades and bugfixes.
>> >
>> >> devel/py-py
>> >> devel/py-test
>> > Further update from 3.6.3 to 3.6.4
>> > https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst
>> > No potential problem with the changes.
>> >
>> >> devel/py-test-httpbin
>> >> devel/py-test-localserver
>> >> devel/py-test-mock
>> >> devel/py-test-runner
>> >> devel/py-test-xdist
>> > Further update from 1.22.2 to 1.22.5
>> > https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst
>> > No potential problem with the changes.
>> >
>> >>
>> >> And a tarball with:
>> >> devel/py-test-forked (new dependency of devel/py-test-xdist).
>> >>
>> >> To check for the possibility of this updates affecting other ports I
>> >> checked every port using the current versions vs the updated versions,
>> >> the results are attached.
>> >> The format is:
>> >> FULLPKGPATH
>> >> Result using current version
>> >> Result using new version (if differences exist, none if equals)
>> >>
>> >> The only ones giving a different result are:
>> >> www/py-httpie
>> >> 4 failed, 223 passed, 4 skipped, 13 warnings
>> >> Error: fixture is being applied more than once to the same function
>> >>
>> >> devel/py-doit
>> >> 2 failed, 731 passed, 21 skipped
>> >> Error: fixture is being applied more than once to the same function
>> >>
>> >> According to the pytest changelog:
>> >> "Now when @pytest.fixture is applied more than once to the same
>> >> function a ValueError is raised. This buggy behavior would cause
>> >> surprising problems and if was working for a test suite it was mostly
>> >> by accident."
>> >> https://docs.pytest.org/en/latest/changelog.html#pytest-3-6-0-2018-05-23
>> >>
>> >> So I think that with this we can rest assure that the updates work fine.
>> >> With that I propose to update the versions with the unified diff that
>> >> I attached as well, and the new dependency on py-test-xdist:
>> >> py-test-forked (also attached...).
>> >> Doing the change at once seems to me reasonable given the
>> >> interdependency and also the way in witch I made the tests.
>> >>
>> >> Cheers.
>> >> Elias.
>>
No comments:
Post a Comment