Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Fix remaining failing test in 5.2 #2195
Comments
I'm working on |
For 5.1 Details: The (swallowed) error is Doing exactly the same in Plone 5.1 in |
Just a note: reverting this zopefoundation/Products.CMFCore@05b3968#diff-4e6966d1d7ef0aaed5a8c2322c887fb1 |
The two issues that pass locally might be fixed with plone/Products.Marshall@23a7752 |
plone/Products.Marshall@23a7752 fixed failures I had when running The remaining failure in |
@pbauer I've been trying a different approach to that one in plone/plone.app.folder#14 but I haven't gotten it quite right yet. |
So here is small story about the failing tests in The two breaking tests Here is the relevant part of the log:
What? Why is does First I reproduced the error by testing all packages in the test-group Archetypes (where the error occurs):
Then I only use the test-layers that are actually set up according to the output:
That works, I see the error. But I will not try to read 733 tests and wait for more than 3 minutes each time I think I may have fixed something! Thus I use divide and conquer to figure out which combination producedes the failing tests: remove half of the packages layers and see if it still fails. If they pass try the other half. Do the same with the layers. Remember to keep It turned out that the following combination exposed the issue:
Still way to many tests to have a look. Most of them in Consequently I kept only one doctest that still kept the issue by commenting out the others in Now I needed to find a combination of three tests from these layers that still expose the issue. To to that I added the option -vv to the testrunner to see the names and python path of all tests I still run.
24 seconds? I can work with that. Still I remove tests from each layer until I only have three tests remaining and revert my changes to . The result is the following:
Since more than one test still exposed the issue I kept only very simple ones because I guessed that the issue is actually in the setup or teardown. So next I change the test At this point I can skip constraining the layers since I only run three tests from two packages. Time to actually read what the remaining tests are doing. I strip down all tests and their setup to the base minimum that still breaks the tests and cannot find anything. I turn So the test-layers for the two tests that do not fail or error by themselves but trigger the issue in the failing tests ( This is the moment when I decide to migrate them to proper I hope that monster will never rear its ugly head again until I fear it will be quite some time until all |
Branch: refs/heads/master Date: 2017-11-09T17:18:47+01:00 Author: Philip Bauer (pbauer) <bauer@starzel.de> Commit: plone/Products.CMFFormController@b51fb48 Migrate breaking tests to plone.app.testing. See plone/Products.CMFPlone#2195. Files changed: M CHANGES.rst M Products/CMFFormController/tests/testRedirectTo.py M setup.py Repository: Products.CMFFormController Branch: refs/heads/master Date: 2017-11-09T21:37:49+01:00 Author: Philip Bauer (pbauer) <bauer@starzel.de> Commit: plone/Products.CMFFormController@c1109e5 Merge pull request #14 from plone/migrate_breakting_tests Migrate breaking tests to plone.app.testing Files changed: M CHANGES.rst M Products/CMFFormController/tests/testRedirectTo.py M setup.py
@pbauer you should turn that into a blog post! According to http://jenkins.plone.org/py3/deps-reverse/Products.CMFFormController.svg only archetypes, ATCT and CMFPlone use CMFFormController, and on CMFPlone is almost gone, is still that much work to do? Lastly, regarding migration to p.a.testing, sadly is the way to go, we need to have all tests over it to avoid isolation tests. |
@gforcada I did as you said |
The final issue was fixed with plone/plone.app.folder#14 by @davisagli. Many thanks! |
With this closed we can start merging the open pull-requests that fix imports with Python 3. Tada! |
pbauer commentedOct 27, 2017
•
edited
Plone 5.2 - Python 2.7 is finally green but we still have 9 failling tests in http://jenkins.plone.org/job/plone-5.2-python-2.7-at/.
This is a meta-ticket so that people do not work on the same issue at the same time.
Here are these tests and links to issue/pr.
Products.ATContentTypes.tests.traversal.txt
see belowProducts.CMFFormController.tests.testRedirectTo.TestRedirectToFunctional.test_attacker_redirect
passes locally. Fixed in plone/Products.CMFFormController#14Products.CMFFormController.tests.testRedirectTo.TestRedirectToFunctional.test_regression
passes locally. Fixed in plone/Products.CMFFormController#14plone.app.blob.tests.test_integration.IntegrationTests.testIconLookupForUnknownMimeType
. Issue #2194src.plone.app.blob.tests.replacement-types.txt
. Issue #2193Products.Archetypes.tests.traversal.txt
PR: zopefoundation/Zope#215plone.app.blob.tests.test_replacements.FileReplacementTests.testCreateFileBlob
PR: plone/plone.app.blob#44plone.app.imaging.tests.test_new_scaling.ImagePublisherTests.testPublishFTPScaleViaUID
. PR: zopefoundation/Zope#214plone.app.imaging.tests.test_new_scaling.ImagePublisherTests.testPublishWebDavScaleViaUID
. PR: zopefoundation/Zope#214Robot.Test Controlpanel Types.Scenario: Allow comments for Link Type
Fix: 561bc78The text was updated successfully, but these errors were encountered: