use current ZODB (3rd trial)

[jensens]

Original PR is #317. The second trial (#320) was to chaotic (I made wrong assumptions).

Now a third trial. I start with a simple cherry-pick of the original commit.

[jensens]

Ok, this shows that the original commit already comes with the problem.
As it was green at some point it must be something introduced later.

@plone/testing-team and @jimfulton any idea why it fails so badly here?

[jimfulton]

On Wed, Apr 12, 2017 at 10:50 AM, Jens W. Klein ***@***.***> wrote: Ok, this shows that the original commit already comes with the problem. As it was green at some point it must be something introduced later. @plone/testing-team <https://github.com/orgs/plone/teams/testing-team> and @jimfulton <https://github.com/jimfulton> any idea why it fails so badly here?

I'm confused. The tests were passing and now aren't. I just ran the non-selenium tests (/bin/alltsests) on use-current-zodb-3 on my mac and they all passed. Total time elapsed: 1585.193 seconds Grand total: 90 packages, 0 failures Are the failures selenium tests? I'll try on linux via a docker container.

[jimfulton]

On Wed, Apr 12, 2017 at 11:47 AM, Jim Fulton ***@***.***> wrote: On Wed, Apr 12, 2017 at 10:50 AM, Jens W. Klein ***@***.***> wrote: > Ok, this shows that the original commit already comes with the problem. > As it was green at some point it must be something introduced later. > > @plone/testing-team <https://github.com/orgs/plone/teams/testing-team> > and @jimfulton <https://github.com/jimfulton> any idea why it fails so > badly here? > I'm confused. The tests were passing and now aren't. I just ran the non-selenium tests (/bin/alltsests) on use-current-zodb-3 on my mac and they all passed. Total time elapsed: 1585.193 seconds Grand total: 90 packages, 0 failures Are the failures selenium tests? I'll try on linux via a docker container.

I ran the tests in a linux container. I'm actually unsure how to interpret results from bin/alltests. The summary: Packages with test failures: Failing tests in group plone_app_testing Total time elapsed: 1474.068 seconds Grand total: 90 packages, 1 failures But if I scroll up: Error in test testNormalizeLatin1 (Products.CMFPlone.tests.testUnicodeSplitter.TestCaseNormalizer) Traceback (most recent call last): File "/usr/lib/python2.7/unittest/case.py", line 329, in run testMethod() File "/home/jim/p/plone/buildout.coredev/src/Products.CMFPlone/Products/CMFPlone/tests/testUnicodeSplitter.py", line 127, in testNormalizeLatin1 saved = _setlocale(*LATIN1) File "/home/jim/p/plone/buildout.coredev/src/Products.CMFPlone/Products/CMFPlone/tests/testUnicodeSplitter.py", line 28, in _setlocale str(LATIN1)) Error: ('Unsupported locale. These tests need at least one of the following locales available on your system', "('en_US.ISO-8859-1', 'en_US.ISO8859-15', 'en_GB.ISO8859-15', 'de_DE@euro', 'fr_FR@euro', 'nl_NL@euro')") 1074/1143 (94.0%) Error in test testProcessLatin1 (Products.CMFPlone.tests.testUnicodeSplitter.TestSplitter) Traceback (most recent call last): File "/usr/lib/python2.7/unittest/case.py", line 329, in run testMethod() File "/home/jim/p/plone/buildout.coredev/src/Products.CMFPlone/Products/CMFPlone/tests/testUnicodeSplitter.py", line 89, in testProcessLatin1 saved = _setlocale(*LATIN1) File "/home/jim/p/plone/buildout.coredev/src/Products.CMFPlone/Products/CMFPlone/tests/testUnicodeSplitter.py", line 28, in _setlocale str(LATIN1)) Error: ('Unsupported locale. These tests need at least one of the following locales available on your system', "('en_US.ISO-8859-1', 'en_US.ISO8859-15', 'en_GB.ISO8859-15', 'de_DE@euro', 'fr_FR@euro', 'nl_NL@euro')") Gaaa, 2 errors that don't seem to show up in the summary. I'm guessing I can fix these by installing some local in my container. Oh, more of these above. I also note a traceback with: browser.open(portalURL+'/@@manage-dashboard?_authenticator=' + createToken()) Is this trying to run a selenium test? I don't see a failure in the output.

[jimfulton]

After adding a missing locale, I get no errors from bin/alltests in a linux container.

[jensens]

@jimfulton thanks for testing this. It looks more like a problem or a difference in our Jenkins test setup. I hope we sort this out next week at Plone Open Garden in Sorrento/ Italy.

[gforcada]

@jimfulton @jensens thanks for your effort, finally we could fix the weird errors on our jenkins setup. I removed all cached eggs on .buildout folder and that was it 😄 🎉

[jimfulton]

Woo hoo!