Mailing List Archive: Zope: CMF

CMF Tests: 3 OK, 1 Failed

1 2

View All

Index | Next | Previous | View Threaded

cmf-tests at epy

Aug 15, 2009, 4:59 AM

Post #1 of 27 (2313 views)
Permalink

CMF Tests: 3 OK, 1 Failed

Summary of messages to the cmf-tests list.
Period Fri Aug 14 12:00:00 2009 UTC to Sat Aug 15 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Fri Aug 14 21:15:27 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011880.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Fri Aug 14 21:09:21 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011877.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Fri Aug 14 21:11:22 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011878.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Fri Aug 14 21:13:27 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011879.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 16, 2009, 4:59 AM

Post #2 of 27 (2248 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Sat Aug 15 12:00:00 2009 UTC to Sun Aug 16 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Sat Aug 15 21:12:20 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011884.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Sat Aug 15 21:06:19 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011881.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Sat Aug 15 21:08:20 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011882.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Sat Aug 15 21:10:20 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011883.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 17, 2009, 4:59 AM

Post #3 of 27 (2253 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Sun Aug 16 12:00:00 2009 UTC to Mon Aug 17 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Sun Aug 16 21:17:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011888.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Sun Aug 16 21:11:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011885.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Sun Aug 16 21:13:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011886.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Sun Aug 16 21:15:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011887.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

tseaver at palladion

Aug 17, 2009, 7:45 AM

Post #4 of 27 (2254 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

CMF Tests Summarizer wrote:
> Summary of messages to the cmf-tests list.
> Period Sun Aug 16 12:00:00 2009 UTC to Mon Aug 17 12:00:00 2009 UTC.
> There were 4 messages: 4 from CMF Tests.
>
>
> Test failures
> -------------
>
> Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
> From: CMF Tests
> Date: Sun Aug 16 21:17:25 EDT 2009
> URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011888.html

This test appears to be due to changes which Alec made in fixing the
MailHost product on the Zope trunk. I think these doctests themselves
are largely bogus (they are breaking on bits we don't care about), but
maybe there is an easy fix?

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver [at] palladion
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKiW0U+gerLs4ltQ4RAtk6AKDI6mYd+M27gyISBD7NBrLZkA2KcACfblHN
iE3/LP2oXYzqGQumuE+SqJA=
=Srzn
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Aug 17, 2009, 7:56 AM

Post #5 of 27 (2241 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Aug 17, 2009, at 16:45 , Tres Seaver wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 :
>> Linux
>> From: CMF Tests
>> Date: Sun Aug 16 21:17:25 EDT 2009
>> URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011888.html
>
> This test appears to be due to changes which Alec made in fixing the
> MailHost product on the Zope trunk. I think these doctests themselves
> are largely bogus (they are breaking on bits we don't care about), but
> maybe there is an easy fix?

These failures have been brought up in a zope-dev thread about the
MailHost changes, they are related to a switch from base64 to quoted-
printable encoding for some headers. There has not been any final
determination if this change is OK. Alec has promised to fix the tests
once this has been decided.

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkqJb5gACgkQRAx5nvEhZLJsrgCfUcacJyJ0eLJFcpRqM1puvpq1
GHYAoInsi2odl1VtOcHSTuqsbr57I/Ff
=qphC
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

apm13 at columbia

Aug 17, 2009, 8:48 AM

Post #6 of 27 (2240 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

On Mon, Aug 17, 2009 at 7:56 AM, Jens Vagelpohl<jens [at] dataflake> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Aug 17, 2009, at 16:45 , Tres Seaver wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>> Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
>>> From: CMF Tests
>>> Date: Sun Aug 16 21:17:25 EDT 2009
>>> URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011888.html
>>
>> This test appears to be due to changes which Alec made in fixing the
>> MailHost product on the Zope trunk. �I think these doctests themselves
>> are largely bogus (they are breaking on bits we don't care about), but
>> maybe there is an easy fix?
>
> These failures have been brought up in a zope-dev thread about the MailHost
> changes, they are related to a switch from base64 to quoted-printable
> encoding for some headers. There has not been any final determination if
> this change is OK. Alec has promised to fix the tests once this has been
> decided.

Exactly. The failures are essentially cosmetic, I can fix them either
by removing the Quoted Printable configuration from MailHost or by
changing the CMF tests to expect Quoted Printable instead of Base64.
Quoted Printable is easily readable/debuggable and doesn't get
penalized by spam filters, base64 is more compact. It may make the
most sense to remove the Quoted Printable config from MailHost and
just punt this decision to some future release.

Alec
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

hanno at hannosch

Aug 17, 2009, 8:52 AM

Post #7 of 27 (2246 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

On Mon, Aug 17, 2009 at 5:48 PM, Alec Mitchell<apm13 [at] columbia> wrote:
> It may make the
> most sense to remove the Quoted Printable config from MailHost and
> just punt this decision to some future release.

Currently your changes only apply to Zope trunk aka 2.13 which is in
early development. The change looks perfectly fine to me for that
release.

If you get the permission to backport these changes to 2.12 (or be
bold enough to just do it, since they seem to make sense) you could
back out this one change, so the 2.12 would keep the slightly more
backwards compatible notion.

Hanno
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Aug 17, 2009, 9:40 AM

Post #8 of 27 (2249 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Aug 17, 2009, at 17:52 , Hanno Schlichting wrote:

> If you get the permission to backport these changes to 2.12 (or be
> bold enough to just do it, since they seem to make sense) you could
> back out this one change, so the 2.12 would keep the slightly more
> backwards compatible notion.

Since this is just a cosmetic change and it takes 5 seconds to change
the test there's no reason at all to only apply part of the changes to
2.12, provided they get applied to begin with (which I hope).

Backwards-compatibility is great, but let's not overdo it. If anyone
relies on those headers being specifically base64 the application is
broken by design.

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkqJh/wACgkQRAx5nvEhZLISQwCeMXmymNDcGK60VX23RqUKABP4
fzAAnREAD45iDftlOw0FtztZ+x/bXRqY
=pOCB
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Aug 17, 2009, 10:19 AM

Post #9 of 27 (2240 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

On 2009-8-17 17:48, Alec Mitchell wrote:
> Exactly. The failures are essentially cosmetic, I can fix them either
> by removing the Quoted Printable configuration from MailHost or by
> changing the CMF tests to expect Quoted Printable instead of Base64.
> Quoted Printable is easily readable/debuggable and doesn't get
> penalized by spam filters, base64 is more compact. It may make the
> most sense to remove the Quoted Printable config from MailHost and
> just punt this decision to some future release.

I would rather see those quopri changse go in for two reasons: it makes
testing emails easier us humans can read quoted printable text while
base64 looks like line noice, and in my experience spamfilters tend to
consider base64 encoded emails more likely to spam.

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 19, 2009, 4:59 AM

Post #10 of 27 (2242 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Tue Aug 18 12:00:00 2009 UTC to Wed Aug 19 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Tue Aug 18 21:13:13 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011896.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Tue Aug 18 21:07:13 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011893.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Tue Aug 18 21:09:13 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011894.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Tue Aug 18 21:11:13 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011895.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 20, 2009, 4:59 AM

Post #11 of 27 (2232 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Wed Aug 19 12:00:00 2009 UTC to Thu Aug 20 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Wed Aug 19 21:12:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011900.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Wed Aug 19 21:06:24 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011897.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Wed Aug 19 21:08:24 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011898.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Wed Aug 19 21:10:24 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011899.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 21, 2009, 4:59 AM

Post #12 of 27 (2228 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Thu Aug 20 12:00:00 2009 UTC to Fri Aug 21 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Thu Aug 20 21:11:58 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011904.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Thu Aug 20 21:05:58 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011901.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Thu Aug 20 21:07:58 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011902.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Thu Aug 20 21:09:58 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011903.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 22, 2009, 4:59 AM

Post #13 of 27 (2227 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Fri Aug 21 12:00:00 2009 UTC to Sat Aug 22 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Fri Aug 21 21:12:17 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011908.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Fri Aug 21 21:06:17 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011905.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Fri Aug 21 21:08:17 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011906.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Fri Aug 21 21:10:17 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011907.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 23, 2009, 4:59 AM

Post #14 of 27 (2225 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Sat Aug 22 12:00:00 2009 UTC to Sun Aug 23 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Sat Aug 22 21:12:10 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011912.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Sat Aug 22 21:06:09 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011909.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Sat Aug 22 21:08:09 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011910.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Sat Aug 22 21:10:09 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011911.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 24, 2009, 4:59 AM

Post #15 of 27 (2218 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Sun Aug 23 12:00:00 2009 UTC to Mon Aug 24 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Sun Aug 23 21:12:20 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011916.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Sun Aug 23 21:06:20 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011913.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Sun Aug 23 21:08:20 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011914.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Sun Aug 23 21:10:20 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011915.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 25, 2009, 4:59 AM

Post #16 of 27 (2213 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Mon Aug 24 12:00:00 2009 UTC to Tue Aug 25 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Mon Aug 24 21:12:14 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011920.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Mon Aug 24 21:06:14 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011917.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Mon Aug 24 21:08:14 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011918.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Mon Aug 24 21:10:14 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011919.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

cmf-tests at epy

Aug 26, 2009, 4:59 AM

Post #17 of 27 (2198 views)
Permalink

CMF Tests: 3 OK, 1 Failed [In reply to]

Summary of messages to the cmf-tests list.
Period Tue Aug 25 12:00:00 2009 UTC to Wed Aug 26 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.

Test failures
-------------

Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
From: CMF Tests
Date: Tue Aug 25 21:12:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011924.html

Tests passed OK
---------------

Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Tue Aug 25 21:06:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011921.html

Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux
From: CMF Tests
Date: Tue Aug 25 21:08:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011922.html

Subject: OK : CMF-trunk Zope-2.12 Python-2.6.2 : Linux
From: CMF Tests
Date: Tue Aug 25 21:10:25 EDT 2009
URL: http://mail.zope.org/pipermail/cmf-tests/2009-August/011923.html

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

tseaver at palladion

Mar 31, 2010, 9:55 AM

Post #18 of 27 (1013 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hanno Schlichting wrote:
> Hi Tres,
>
> On Wed, Mar 31, 2010 at 5:02 PM, Tres Seaver <tseaver [at] palladion> wrote:
>> I can't even get the trunk buildout to build this morning: Hanno, do
>> you have any clue what is going on here?
>>
>> The version, 3.7.1, is not consistent with the requirement, \
>> 'zope.sendmail<3.7.0'.
>> While:
>> Installing test-zope212.
>> Error: Bad version 3.7.1
>
> I added lots of version pins for all unpinned packages to the
> buildout. I guess some of those loose ends suddenly became
> problematic. I'm not sure which one exactly caused this, though.

This is a problem with trying to run both the Zope-trunk tests and the
Zope-2.12 tests in the same buildout: we should ideally be able to have
*both* zope.sendmail versions in the 'eggs' directory, with the
"correct" one for each testrunner configured somehow. I don't think the
testrunner recipe is clever enough for this usage, though.

> After my change the buildout runs at least. Judging from your commits,
> you are working on the test failures. I'll leave you to it for a while
> :) I was planning to look at them later today.

I've squished them all, I think, running against the trunk. There are
still a bunch of errors / failures running under 2.12.3, though, which I
can't figure out.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver [at] palladion
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkuzfl4ACgkQ+gerLs4ltQ7hLQCg2uKF+wmK8LZ8IDrkbR86vM81
vD0AoKMBNtV5AHVrUrKxAYF0JN1Sd6r7
=1a7y
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] zope
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

tseaver at palladion

Mar 31, 2010, 11:02 AM

Post #19 of 27 (1015 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tres Seaver wrote:
> Hanno Schlichting wrote:
>> Hi Tres,
>
>> On Wed, Mar 31, 2010 at 5:02 PM, Tres Seaver <tseaver [at] palladion> wrote:
>>> I can't even get the trunk buildout to build this morning: Hanno, do
>>> you have any clue what is going on here?
>>>
>>> The version, 3.7.1, is not consistent with the requirement, \
>>> 'zope.sendmail<3.7.0'.
>>> While:
>>> Installing test-zope212.
>>> Error: Bad version 3.7.1
>> I added lots of version pins for all unpinned packages to the
>> buildout. I guess some of those loose ends suddenly became
>> problematic. I'm not sure which one exactly caused this, though.
>
> This is a problem with trying to run both the Zope-trunk tests and the
> Zope-2.12 tests in the same buildout: we should ideally be able to have
> *both* zope.sendmail versions in the 'eggs' directory, with the
> "correct" one for each testrunner configured somehow. I don't think the
> testrunner recipe is clever enough for this usage, though.
>
>> After my change the buildout runs at least. Judging from your commits,
>> you are working on the test failures. I'll leave you to it for a while
>> :) I was planning to look at them later today.
>
> I've squished them all, I think, running against the trunk. There are
> still a bunch of errors / failures running under 2.12.3, though, which I
> can't figure out.

I believe the root of this problem is that the 'index' and 'versions'
bits of a buildout.cfg are effectively Highlanders ("there can only be
one"). I gave up on trying to get the "two, two, two Zopes in one"
buildout to work, and instead created a separate buildout.cfg for
running CMF's tests against Zope 2.12.3.

Unless somebody objects violently, I plan to check the attached config
in on a branch of the main CMF buildout, and rip out the stuff which
tries to do both from the trunk version. This change will require
Stefan's nightly runner to be adjusted, so I'm CC'ing him.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver [at] palladion
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkuzjjUACgkQ+gerLs4ltQ6cVACg1RC0QGs2TYfJTuKprgGIsox2
RAEAoJ8Qokke0sN2W+ir3lkT3z7ksNAS
=WlVc
-----END PGP SIGNATURE-----

Attachments:

buildout.cfg (0.82 KB)

hanno at hannosch

Mar 31, 2010, 11:16 AM

Post #20 of 27 (1014 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

2010/3/31 Tres Seaver <tseaver [at] palladion>:
> I believe the root of this problem is that the 'index' and 'versions'
> bits of a buildout.cfg are effectively Highlanders ("there can only be
> one"). I gave up on trying to get the "two, two, two Zopes in one"
> buildout to work, and instead created a separate buildout.cfg for
> running CMF's tests against Zope 2.12.3.

Yeah, that sounds sensible. The extra test part with an index was a
hack in the first place.

> Unless somebody objects violently, I plan to check the attached config
> in on a branch of the main CMF buildout, and rip out the stuff which
> tries to do both from the trunk version. This change will require
> Stefan's nightly runner to be adjusted, so I'm CC'ing him.

Looks all good, except for this first line of comment, which should be
CMF trunk + Zope 2.12 :)

> # CMF trunk + Zope trunk

Personally I prefer versions.cfg files, so we could use an:

extends = http://download.zope.org/Zope2/index/2.12.3/versions.cfg

instead of the index = line. But I don't care much for this specific
test buildout.

> [buildout]
> parts =
> zopepy
> test
> eggs =
> Zope2
> Products.CMFCalendar
> Products.CMFCore [test]
> Products.CMFDefault
> Products.CMFTopic
> Products.CMFUid
> Products.DCWorkflow
> Products.GenericSetup
> five.localsitemanager
> develop =
> src/Products.CMFCalendar
> src/Products.CMFCore
> src/Products.CMFDefault
> src/Products.CMFTopic
> src/Products.CMFUid
> src/Products.DCWorkflow
> src/Products.GenericSetup
> src/five.localsitemanager
> index = http://download.zope.org/Zope2/index/2.12.3
>
> [versions]
> # CMF-only dependencies
> five.formlib = 1.0.2
>
> [zopepy]
> recipe = zc.recipe.egg
> eggs = ${buildout:eggs}
> interpreter = zopepy
> scripts = zopepy
>
> [test]
> recipe = zc.recipe.testrunner
> eggs = ${buildout:eggs}
> defaults = ['--module', '^Products[.](CMF|DC|GenericSetup)|^five[.]']
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] zope
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

tseaver at palladion

Mar 31, 2010, 11:33 AM

Post #21 of 27 (1018 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hanno Schlichting wrote:
> 2010/3/31 Tres Seaver <tseaver [at] palladion>:
>> I believe the root of this problem is that the 'index' and 'versions'
>> bits of a buildout.cfg are effectively Highlanders ("there can only be
>> one"). I gave up on trying to get the "two, two, two Zopes in one"
>> buildout to work, and instead created a separate buildout.cfg for
>> running CMF's tests against Zope 2.12.3.
>
> Yeah, that sounds sensible. The extra test part with an index was a
> hack in the first place.
>
>> Unless somebody objects violently, I plan to check the attached config
>> in on a branch of the main CMF buildout, and rip out the stuff which
>> tries to do both from the trunk version. This change will require
>> Stefan's nightly runner to be adjusted, so I'm CC'ing him.
>
> Looks all good, except for this first line of comment, which should be
> CMF trunk + Zope 2.12 :)
>
>> # CMF trunk + Zope trunk
>
> Personally I prefer versions.cfg files, so we could use an:
>
> extends = http://download.zope.org/Zope2/index/2.12.3/versions.cfg
>
> instead of the index = line. But I don't care much for this specific
> test buildout.

OK, the change I'm planning on the trunk essentially reverts your last
commit (all the extra version pins to make the 'test-zope212' part
build), plus deleting the test-zope212 part (see attached patch).

BTW, I think the other test buildouts which do not run aganst the Zope2
trunk should probably also be adjusted to use released Zope 2.12.x eggs
as well: we aren't co-developing the Zope 2.12 branch along with CMF
2.2 (any more, at least).

I also don't know why the 'instance' and 'i18n*' parts are configured in
these buildouts -- does somebody have a memory of why, or a reason to
keep them?

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver [at] palladion
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkuzlXcACgkQ+gerLs4ltQ6GtgCePELI/PiWKI71CESkmn6ybLou
YFgAoJHrg5d2A4wTIsc1jeh8UjUqCqOD
=N8Fu
-----END PGP SIGNATURE-----

Attachments:

remove_212_stuff.patch (1.78 KB)

hanno at hannosch

Mar 31, 2010, 11:41 AM

Post #22 of 27 (1013 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

On Wed, Mar 31, 2010 at 8:33 PM, Tres Seaver <tseaver [at] palladion> wrote:
> OK, the change I'm planning on the trunk essentially reverts your last
> commit (all the extra version pins to make the 'test-zope212' part
> build), plus deleting the test-zope212 part (see attached patch).

Sure. That wasn't much more than a band-aid.

> BTW, I think the other test buildouts which do not run aganst the Zope2
> trunk should probably also be adjusted to use released Zope 2.12.x eggs
> as well: we aren't co-developing the Zope 2.12 branch along with CMF
> 2.2 (any more, at least).

Well, it is nice to catch problems introduced in Zope 2 on the day
after they are made. And not when someone tries to update the buildout
to a new version at some later point. The risk is much lower for
stable branches, but it still exists.

As seen from todays test failures, they nicely showed how I screwed
some things up a bit too much on Zope trunk :)

> I also don't know why the 'instance' and 'i18n*' parts are configured in
> these buildouts -- does somebody have a memory of why, or a reason to
> keep them?

Yvo has to comment this. I think he sometimes rebuilds the pot files
in CMF with the i18n part. Not sure about the instance.

Hanno
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] zope
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Mar 31, 2010, 12:36 PM

Post #23 of 27 (1017 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 3/31/10 20:33 , Tres Seaver wrote:
> I also don't know why the 'instance' and 'i18n*' parts are configured in
> these buildouts -- does somebody have a memory of why, or a reason to
> keep them?

The "instance" part is a pure convenience to quickly fire up an instance
if I need to look at something in the ZMI while doing development. If
there's no pressing reason to remove it I'd really like to keep it.

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkuzpC8ACgkQRAx5nvEhZLIQqgCbBHzB46qtTkc+MUpK0Wu8OoOM
mM0Anjpp3i/yfLNEeLJoNmkq2R1KZ9Kp
=RF/w
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] zope
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

tseaver at palladion

Mar 31, 2010, 1:07 PM

Post #24 of 27 (1014 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jens Vagelpohl wrote:
> On 3/31/10 20:33 , Tres Seaver wrote:
>> I also don't know why the 'instance' and 'i18n*' parts are configured in
>> these buildouts -- does somebody have a memory of why, or a reason to
>> keep them?
>
> The "instance" part is a pure convenience to quickly fire up an instance
> if I need to look at something in the ZMI while doing development. If
> there's no pressing reason to remove it I'd really like to keep it.

I can see leaving that alone for the trunk-on-trunk buildout: do you
need it for the buildouts used to test against other Zope versions?
The extra clutter and build time seems untidy to me.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver [at] palladion
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkuzq4QACgkQ+gerLs4ltQ5RjACgrtFddsSOiSc3Kam9sSRYt09V
J4QAoM6tUIpfiW5tsbWDGvaEy1c0Bevm
=IKyY
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] zope
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Mar 31, 2010, 1:28 PM

Post #25 of 27 (1014 views)
Permalink

Re: CMF Tests: 3 OK, 1 Failed [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 3/31/10 22:07 , Tres Seaver wrote:
> Jens Vagelpohl wrote:
>> On 3/31/10 20:33 , Tres Seaver wrote:
>>> I also don't know why the 'instance' and 'i18n*' parts are configured in
>>> these buildouts -- does somebody have a memory of why, or a reason to
>>> keep them?
>> The "instance" part is a pure convenience to quickly fire up an instance
>> if I need to look at something in the ZMI while doing development. If
>> there's no pressing reason to remove it I'd really like to keep it.
>
> I can see leaving that alone for the trunk-on-trunk buildout: do you
> need it for the buildouts used to test against other Zope versions?
> The extra clutter and build time seems untidy to me.

I'm surprised that you want to remove it. I use it for all buildout
combinations. How do you start an instance while doing work on CMF
proper? Or do you never need any ZMI access or test portal instances? Do
you manually create a separate buildout extending CMF.buildout? IMHO
that would be a needless obstancle as opposed to keeping the "instance"
part.

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkuzsGoACgkQRAx5nvEhZLJSDQCfV6Gue1BBSzQwrj0qd41ecAJ3
1pkAoKzOzmnYUxX6D6h6HnvFYahnVm+6
=3lsZ
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] zope
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads