Re: [Zope-dev] Getting back to "green"
Hello,
On Mon, 17 Oct 2011 10:58:55 -0400 you wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/17/2011 10:21 AM, Adam GROSZER wrote:
>> Hello,
>>
>> On Mon, 17 Oct 2011 10:08:55 -0400 you wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>>
>>> We've lost our discipline about keeping the daily tests passing.
>>> I think this is due to two factors:
>>>
>>> - - We are running tests for code that nobody is actively
>>> maintaining (e.g., all the 'z3c.*' packages which have been
>>> broken for months).
>>
>> If you mean the failures on windowze, I think most of them fail on
>> lxml not having windows egg :-S, someone should kick Sidnei(???)
>
> If the z3c.* packages are being maintained, but not by folks who can
> resolve that issue on Windows, then we should do the testing on a
> platform where the maintainers *can* get the tests to pass. Having
> the board stay red destroys its value for *everybody*, including those
> who don't need or care about those packages.
>>> - - Because of the noise of those failures, we've gotten
>>> complacent about seeing multiple failures in the daily test
>>> report, and thus quit trying to find and fix "new" failures in
>>> code which is maintained.
>>>
>>> I would like to propose that we quit reporting test failures for
>>> the unmaintained packages ('zc3.*', for a start. If somebody
>>> really thinks there is value in such testing, we could perhaps
>>> run those tests only weekly (like the others which have
>>> "expected" failures).
>>
>> If it's about suppressing the *reporting* then suppress that, not
>> the test runs please. Just in case someone wants to maintain a
>> package ;-)
>
> Why waste any resources on tests if nobody is going to find and fix
> failures?
Aber hallo, z3c.form is in there. I do *not* think that's not maintained.
Actually I *know* what's the problem, just can't solve it.
Keeping the tests running is like having the *positive* attitude instead
of the dark "I don't care".
--
Best regards,
Adam GROSZER
--
Quote of the day:
Drama often obscures the real issues
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 21, OK: 28, UNKNOWN: 2
This is the summary for test reports received on the zope-tests list between 2011-10-16 00:00:00 UTC and 2011-10-17 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received [1]FAILED (failures=2) : Zope-trunk Python-2.6.6 : Linux [2]FAILED (failures=2) : Zope-trunk-alltests Python-2.6.6 : Linux [3]ZTK 1.0dev / Python2.4.6 Linux 64bit [4]ZTK 1.0dev / Python2.5.5 Linux 64bit [5]ZTK 1.0dev / Python2.6.5 Linux 64bit [6]ZTK 1.1 / Python2.5.5 Linux 64bit [7]ZTK 1.1 / Python2.6.5 Linux 64bit [8]ZTK 1.1 / Python2.7.2 Linux 64bit [9]ZTK 1.1dev / Python2.5.5 Linux 64bit [10] ZTK 1.1dev / Python2.6.5 Linux 64bit [11] ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [12] winbot / z3c.authenticator_py_265_32 [13] winbot / z3c.baseregistry_py_265_32 [14] winbot / z3c.contents_py_265_32 [15] winbot / z3c.form_py_265_32 [16] winbot / z3c.formui_py_265_32 [17] winbot / z3c.jsontree_py_265_32 [18] winbot / z3c.layer.pagelet_py_265_32 [19] winbot / z3c.layer.ready2go_py_265_32 [20] winbot / z3c.macro_py_265_32 [21] winbot / z3c.pagelet_py_265_32 [22] winbot / z3c.tabular_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 [23] winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1]UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-October/051276.html [2]UNKNOWN FAILED (failures=2) : Zope-trunk-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-October/051277.html [3]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051252.html [4]FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051250.html [5]FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051251.html [6]FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051294.html [7]FAILED ZTK 1.1 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051293.html [8]FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051292.html [9]FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051248.html [10] FAILED ZTK 1.1dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051247.html [11] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051249.html [12] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051264.html [13] FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051261.html [14] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051260.html [15] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051255.html [16] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051257.html [17] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051262.html [18] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051258.html [19] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051267.htm
Re: [Zope-dev] [Checkins] SVN: Zope/trunk/ `setHeader('Set-Cookie', ...)` special-casing can die
On Mon, Oct 17, 2011 at 11:57, Stefan H. Holek wrote: > There are test failures on Zope trunk which look to be connected to your > changes. > https://mail.zope.org/pipermail/zope-tests/2011-October/051224.html > > Please investigate, Ugh. Those tests can go, and someone already dealt with them before I got to them. Mea Culpa! -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [collective.recipe.solrinstance] Example not working
On 17 October 2011 18:36, Hanno Schlichting wrote: > On Mon, Oct 17, 2011 at 11:19 AM, Andreas Jung wrote: >> I used the single-core example for the solrinstance recipe: > > I think someone reported the Solr core examples to be broken in the > latest releases. I don't use the core-variants myself, though. > > Without an issue tracker, it's hard to keep track of those reports. > > Should we migrate the recipe to github and get a free issue tracker? +1 Laurence ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [collective.recipe.solrinstance] Example not working
On Mon, Oct 17, 2011 at 11:19 AM, Andreas Jung wrote: > I used the single-core example for the solrinstance recipe: I think someone reported the Solr core examples to be broken in the latest releases. I don't use the core-variants myself, though. Without an issue tracker, it's hard to keep track of those reports. Should we migrate the recipe to github and get a free issue tracker? Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Getting back to "green"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/2011 10:21 AM, Adam GROSZER wrote:
> Hello,
>
> On Mon, 17 Oct 2011 10:08:55 -0400 you wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> We've lost our discipline about keeping the daily tests passing.
>> I think this is due to two factors:
>>
>> - - We are running tests for code that nobody is actively
>> maintaining (e.g., all the 'z3c.*' packages which have been
>> broken for months).
>
> If you mean the failures on windowze, I think most of them fail on
> lxml not having windows egg :-S, someone should kick Sidnei(???)
If the z3c.* packages are being maintained, but not by folks who can
resolve that issue on Windows, then we should do the testing on a
platform where the maintainers *can* get the tests to pass. Having
the board stay red destroys its value for *everybody*, including those
who don't need or care about those packages.
>> - - Because of the noise of those failures, we've gotten
>> complacent about seeing multiple failures in the daily test
>> report, and thus quit trying to find and fix "new" failures in
>> code which is maintained.
>>
>> I would like to propose that we quit reporting test failures for
>> the unmaintained packages ('zc3.*', for a start. If somebody
>> really thinks there is value in such testing, we could perhaps
>> run those tests only weekly (like the others which have
>> "expected" failures).
>
> If it's about suppressing the *reporting* then suppress that, not
> the test runs please. Just in case someone wants to maintain a
> package ;-)
Why waste any resources on tests if nobody is going to find and fix
failures?
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6cQq8ACgkQ+gerLs4ltQ4aegCgsdOW/Fs9LxVqwo3Pb2OXDw2N
4NIAn3b+OuPml61WVj+n107FpbHf3c2u
=upzk
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Getting back to "green"
Hello,
On Mon, 17 Oct 2011 10:08:55 -0400 you wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> We've lost our discipline about keeping the daily tests passing. I
> think this is due to two factors:
>
> - - We are running tests for code that nobody is actively maintaining
>(e.g., all the 'z3c.*' packages which have been broken for months).
If you mean the failures on windowze, I think most of them fail on lxml
not having windows egg :-S, someone should kick Sidnei(???)
> - - Because of the noise of those failures, we've gotten complacent about
>seeing multiple failures in the daily test report, and thus quit
>trying to find and fix "new" failures in code which is maintained.
>
> I would like to propose that we quit reporting test failures for the
> unmaintained packages ('zc3.*', for a start. If somebody really
> thinks there is value in such testing, we could perhaps run those
> tests only weekly (like the others which have "expected" failures).
If it's about suppressing the *reporting* then suppress that, not the
test runs please. Just in case someone wants to maintain a package ;-)
--
Best regards,
Adam GROSZER
--
Quote of the day:
The best of what we do and are, Just God, forgive!
- William Wordsworth
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Getting back to "green"
On Oct 17, 2011, at 16:08 , Tres Seaver wrote:
> I would like to propose that we quit reporting test failures for the
> unmaintained packages ('zc3.*', for a start. If somebody really
> thinks there is value in such testing, we could perhaps run those
> tests only weekly (like the others which have "expected" failures).
+1
jens
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Getting back to "green"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We've lost our discipline about keeping the daily tests passing. I
think this is due to two factors:
- - We are running tests for code that nobody is actively maintaining
(e.g., all the 'z3c.*' packages which have been broken for months).
- - Because of the noise of those failures, we've gotten complacent about
seeing multiple failures in the daily test report, and thus quit
trying to find and fix "new" failures in code which is maintained.
I would like to propose that we quit reporting test failures for the
unmaintained packages ('zc3.*', for a start. If somebody really
thinks there is value in such testing, we could perhaps run those
tests only weekly (like the others which have "expected" failures).
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6cNvcACgkQ+gerLs4ltQ5N+gCfYAD2UM6Y5ikE92VHERoTk24o
YpkAmwVy9SvDWBW/vrNyR3nDmryDAPXZ
=9kh3
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Conversion old.zope.org to static site
Hi Tom, > Further I have noticed two things: > > 1) Some pages are not recognized correctly and trigger a download (on > Firefox) or show the source code (on IE): > > http://old.zope.org/Members/pje/Wikis/ZPatterns/HowTriggersWork.1 > > 2) For some locations the folder contents are shown instead of the > default page: > > http://old.zope.org/DevHome/CVS/ZopeCVSFAQ Those two are now fixed. Thanks for the heads-up! If you see anything else just drop me a note. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: Zope/trunk/ `setHeader('Set-Cookie', ...)` special-casing can die
Hi Martijn,
There are test failures on Zope trunk which look to be connected to your
changes.
https://mail.zope.org/pipermail/zope-tests/2011-October/051224.html
Please investigate,
Stefan
On 13.10.2011, at 15:18, Martijn Pieters wrote:
> Log message for revision 123087:
> `setHeader('Set-Cookie', ...)` special-casing can die
>
> Use the cookie APIs or addHeader instead.
>
>
> Changed:
> U Zope/trunk/doc/CHANGES.rst
> U Zope/trunk/src/ZPublisher/HTTPResponse.py
>
> -=-
> Modified: Zope/trunk/doc/CHANGES.rst
> ===
> --- Zope/trunk/doc/CHANGES.rst2011-10-13 09:46:28 UTC (rev 123086)
> +++ Zope/trunk/doc/CHANGES.rst2011-10-13 13:18:32 UTC (rev 123087)
> @@ -50,6 +50,11 @@
> Restructuring
> +
>
> +- Removed the special handling of `Set-Cookie` headers in
> + `HTTPResponse.setHeader`. Use the `setCookie`/`appendCookie`/`expireCookie`
> + methods instead, or if low-level control is needed, use `addHeader` instead
> + to get the exact same effect.
> +
> - Removed the `App.version_txt.getZopeVersion` API, you can use
> ``pkg_resources.get_distribution('Zope2').version`` instead.
>
>
> Modified: Zope/trunk/src/ZPublisher/HTTPResponse.py
> ===
> --- Zope/trunk/src/ZPublisher/HTTPResponse.py 2011-10-13 09:46:28 UTC (rev
> 123086)
> +++ Zope/trunk/src/ZPublisher/HTTPResponse.py 2011-10-13 13:18:32 UTC (rev
> 123087)
> @@ -330,13 +330,8 @@
> if not scrubbed:
> name, value = _scrubHeader(name, value)
> key = name.lower()
> -# The following is crazy, given that we have APIs for cookies.
> -# Special behavior will go away in Zope 2.13
> -if key == 'set-cookie':
> -self.accumulated_headers.append((name, value))
> -else:
> -name = literal and name or key
> -self.headers[name] = value
> +name = literal and name or key
> +self.headers[name] = value
>
> def appendHeader(self, name, value, delimiter=", "):
> """ Append a value to an HTTP return header.
>
> ___
> checkins mailing list
> check...@zope.org
> https://mail.zope.org/mailman/listinfo/checkins
--
Stefan H. Holek
ste...@epy.co.at
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [collective.recipe.solrinstance] Example not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I used the single-core example for the solrinstance recipe: http://pypi.python.org/pypi/collective.recipe.solrinstance/3.5#examples-single-solr Trying to access localhost:1234/solr/admin gives me HTTP ERROR 404 Problem accessing /solr/admin/index.jsp. Reason: missing core name in path Powered by Jetty:// Anything I am missing here or is the example or the recipe broken? Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJOm/MzAAoJEADcfz7u4AZj0A0Lv1N2piUWpXmtbpZzZaM+iy9p F7Kte+1GW2ZR59SKlp2G+OjriG8s0TVPoPlUdroWqf2eWduwHo7z/LvQzVoA5RVv 1+KiyC/bHRR5ckWtYa9KhNBIOqySCItQdD39ir11Mcbh5WDMmaj0AHGVChQ1nyIX bnJIet0lb7DMHWsuj1taZ1m9T9Ob3aUdK0qChwwCAOJei4aySFoyFHvhg/KNcgb3 ihWLY/8wJkYch6NgHK1XV6SqJ3u4pgTmbpVsaNLz7NgGq7DKhrpbluoa74Lmyglg PGfrzrIAPyJFQfVmQaz9L2eVDSwjG+JBw1W36FUNZ/AlKBTh/ypsy0NW4MQGD0tS SgOzGXPwH1keXaH+PUk1kfMbMT7nTlAKweVsO7k6XwD5R/IwVGZEkHDf8P+Xro/W Ywrya7h4nNkX19b2+3AVKBtyJgrmsmDoAXCfSpslzhhqOlE6lsX4FA7DhVRRlgfh wf1L/pr8J0gN8EACPT44hkvVHX6bS74= =nWGu -END PGP SIGNATURE- <>___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
