Re: [Zope-dev] IRC meeting summaries from 2010-07-13 and 2010-07-06
I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ 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 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] IRC meeting summaries from 2010-07-13 and 2010-07-06
It sounds strange. The site is set as public. I have tested with different browsers without login and I could download files. Google account should not be required. Do you mean you cannot see the listing of files when you accessed to that URL in your browser? Takeshi On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote: I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ 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 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 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] IRC meeting summaries from 2010-07-13 and 2010-07-06
Hi Takeshi, I can see the listing but when I click on a file download link I get a page saying insufficient privileges. You must be logged in to view this page. jens On Jul 18, 2010, at 11:27, Takeshi Yamamoto t...@mac.com wrote: It sounds strange. The site is set as public. I have tested with different browsers without login and I could download files. Google account should not be required. Do you mean you cannot see the listing of files when you accessed to that URL in your browser? Takeshi On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote: I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ 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 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 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] IRC meeting summaries from 2010-07-13 and 2010-07-06
Hi Jens, I am afraid that if you are clicking the v.2 link instead of download link. The download link is located just under the file name per file. Takeshi On Jul 18, 2010, at 7:07 PM, Jens Vagelpohl wrote: Hi Takeshi, I can see the listing but when I click on a file download link I get a page saying insufficient privileges. You must be logged in to view this page. jens On Jul 18, 2010, at 11:27, Takeshi Yamamoto t...@mac.com wrote: It sounds strange. The site is set as public. I have tested with different browsers without login and I could download files. Google account should not be required. Do you mean you cannot see the listing of files when you accessed to that URL in your browser? Takeshi On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote: I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ 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 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 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] IRC meeting summaries from 2010-07-13 and 2010-07-06
Thanks Takeshi, that was the problem. I never clicked that link because on the iPad it shows up in Japanese letters so I had no idea what it was. jens On Jul 18, 2010, at 12:43, Takeshi Yamamoto t...@mac.com wrote: Hi Jens, I am afraid that if you are clicking the v.2 link instead of download link. The download link is located just under the file name per file. Takeshi On Jul 18, 2010, at 7:07 PM, Jens Vagelpohl wrote: Hi Takeshi, I can see the listing but when I click on a file download link I get a page saying insufficient privileges. You must be logged in to view this page. jens On Jul 18, 2010, at 11:27, Takeshi Yamamoto t...@mac.com wrote: It sounds strange. The site is set as public. I have tested with different browsers without login and I could download files. Google account should not be required. Do you mean you cannot see the listing of files when you accessed to that URL in your browser? Takeshi On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote: I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ 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 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 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] IRC meeting summaries from 2010-07-13 and 2010-07-06
Jens, Thanks a lot for detail description. I have changed the display language. Now it is shown as Download. I could fix it. I assumed these messages are displayed in browser's language, but it was wrong. On Jul 18, 2010, at 7:50 PM, Jens Vagelpohl wrote: Thanks Takeshi, that was the problem. I never clicked that link because on the iPad it shows up in Japanese letters so I had no idea what it was. jens On Jul 18, 2010, at 12:43, Takeshi Yamamoto t...@mac.com wrote: Hi Jens, I am afraid that if you are clicking the v.2 link instead of download link. The download link is located just under the file name per file. Takeshi On Jul 18, 2010, at 7:07 PM, Jens Vagelpohl wrote: Hi Takeshi, I can see the listing but when I click on a file download link I get a page saying insufficient privileges. You must be logged in to view this page. jens On Jul 18, 2010, at 11:27, Takeshi Yamamoto t...@mac.com wrote: It sounds strange. The site is set as public. I have tested with different browsers without login and I could download files. Google account should not be required. Do you mean you cannot see the listing of files when you accessed to that URL in your browser? Takeshi On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote: I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ 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 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 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: 33 OK, 21 Failed, 2 Unknown
Summary of messages to the zope-tests list. Period Sat Jul 17 12:00:00 2010 UTC to Sun Jul 18 12:00:00 2010 UTC. There were 56 messages: 6 from Zope Tests, 2 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 17 from buildbot at winbot.zope.org, 13 from ccomb at free.fr, 5 from ct at gocept.com, 9 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Total languishing bugs for zopeapp: 7 From: ct at gocept.com Date: Sat Jul 17 20:30:19 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016871.html Subject: FAILED : Total languishing bugs for zopetoolkit: 108 From: ct at gocept.com Date: Sat Jul 17 20:36:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016872.html Subject: FAILED : Total languishing bugs for zope: 168 From: ct at gocept.com Date: Sat Jul 17 20:41:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016873.html Subject: FAILED : Total languishing bugs for zope2: 63 From: ct at gocept.com Date: Sat Jul 17 20:45:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016874.html Subject: FAILED: Repository policy check found errors in 413 projects From: ct at gocept.com Date: Sat Jul 17 21:15:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016876.html Subject: FAILED : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Sat Jul 17 22:04:06 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016884.html Subject: FAILED : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Sat Jul 17 22:05:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016885.html Subject: FAILED : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Sat Jul 17 22:05:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016886.html Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Sat Jul 17 22:13:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016888.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Sat Jul 17 22:58:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016893.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Sat Jul 17 23:09:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016894.html Subject: FAILED : winbot / ztk_10 py_270_win32 From: buildbot at winbot.zope.org Date: Sat Jul 17 23:45:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016899.html Subject: FAILED : winbot / ztk_10 py_270_win64 From: buildbot at winbot.zope.org Date: Sat Jul 17 23:52:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016900.html Subject: FAILED : ZTK 1.0dev / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Sun Jul 18 00:17:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016902.html Subject: FAILED : winbot / ZODB_dev py_254_win32 From: buildbot at winbot.zope.org Date: Sun Jul 18 00:55:41 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016906.html Subject: FAILED : winbot / ZODB_dev py_265_win32 From: buildbot at winbot.zope.org Date: Sun Jul 18 01:50:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016908.html Subject: FAILED : ZTK 1.0 / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Sun Jul 18 01:52:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016909.html Subject: FAILED : winbot / ZODB_dev py_265_win64 From: buildbot at winbot.zope.org Date: Sun Jul 18 02:44:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016913.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Sun Jul 18 03:40:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016915.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Sun Jul 18 04:35:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016917.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Sun Jul 18 07:35:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016921.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Sun Jul 18 03:01:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016914.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.5-maestro From: buildbot at enfoldsystems.com Date: Sun Jul 18 03:58:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016916.html Tests passed OK --- Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Sat Jul 17 21:08:37 EDT 2010 URL:
[Zope-dev] ./bin/test failing with trunk zope.testing
Hello, When running zope.testing's tests on my laptop, I get many failures. I've run the tests plenty of times before and haven't got these failures. Am a bit mystified, so I'd appreciate any help. jml Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Failure in test /home/jml/src/zope.testing/trunk/src/zope/testing/testrunner/testrunner-debugging-layer-setup.test Traceback (most recent call last): File /usr/lib/python2.6/unittest.py, line 279, in run testMethod() File /home/jml/src/zope.testing/trunk/src/zope/testing/doctest/__init__.py, line 2249, in runTest raise self.failureException(self.format_failure(new.getvalue())) DocTestFailureException: Failed doctest test for testrunner-debugging-layer-setup.test File /home/jml/src/zope.testing/trunk/src/zope/testing/testrunner/testrunner-debugging-layer-setup.test, line 0 -- File /home/jml/src/zope.testing/trunk/src/zope/testing/testrunner/testrunner-debugging-layer-setup.test, line 100, in testrunner-debugging-layer-setup.test Failed example: try: zope.testing.testrunner.run_internal( ['--path', dir, '-Dvv', '--tests-pattern', 'tests2']) finally: sys.stdin = real_stdin # doctest: +ELLIPSIS +REPORT_NDIFF Differences (ndiff with -expected +actual): Running tests at level 1 Running tests2.Layer1 tests: Set up tests2.Layer1 in N.NNN seconds. Running: a_test (tests2) Ran 1 tests with 0 failures and 0 errors in N.NNN seconds. Running tests2.Layer2 tests: Tear down tests2.Layer1 ... not supported Running in a subprocess. Set up tests2.Layer2 ** BLANKLINE Can't post-mortem debug when running a layer as a subprocess! Try running layer 'tests2.Layer2' by itself. BLANKLINE ** BLANKLINE Traceback (most recent call last): - ... + File /home/jml/.buildout/eggs/zope.testrunner-4.0.0b4-py2.6.egg/zope/testrunner/runner.py, Line NNN, in run_layer + setup_layer(options, layer, setup_layers) + File /home/jml/.buildout/eggs/zope.testrunner-4.0.0b4-py2.6.egg/zope/testrunner/runner.py, Line NNN, in setup_layer + layer.setUp() + File /tmp/tmprTh_Qv/TESTS-DIR/tests2.py, Line NNN, in setUp raise ValueError ValueError BLANKLINE BLANKLINE Tests with errors: -runTest (zope.testing.testrunner.runner.SetUpLayerFailure) ? +runTest (zope.testrunner.runner.SetUpLayerFailure) Total: 1 tests, 0 failures, 1 errors in N.NNN seconds. True --Return-- /home/jml/src/zope.testing/trunk/src/zope/testing/doctest/__init__.py(360)set_trace()-None - pdb.Pdb.set_trace(self) (Pdb) p x *** NameError: NameError(name 'x' is not defined,) (Pdb) c Failure in test /home/jml/src/zope.testing/trunk/src/zope/testing/testrunner/testrunner-debugging.txt Traceback (most recent call last): File /usr/lib/python2.6/unittest.py, line 279, in run testMethod() File /home/jml/src/zope.testing/trunk/src/zope/testing/doctest/__init__.py, line 2249, in runTest raise self.failureException(self.format_failure(new.getvalue())) DocTestFailureException: Failed doctest test for testrunner-debugging.txt File /home/jml/src/zope.testing/trunk/src/zope/testing/testrunner/testrunner-debugging.txt, line 0 -- File /home/jml/src/zope.testing/trunk/src/zope/testing/testrunner/testrunner-debugging.txt, line 35, in testrunner-debugging.txt Failed example: try: testrunner.run_internal(defaults) finally: sys.stdin = real_stdin # doctest: +ELLIPSIS Expected: Running zope.testing.testrunner.layer.UnitTests tests: ... testrunner-ex/sample3/sampletests_d.py(NNN)test_set_trace1() - y = x (Pdb) p x 1 (Pdb) c Ran 1 tests with 0 failures and 0 errors in N.NNN seconds. ... False Got: Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in N.NNN seconds. Ran 1 tests with 0 failures and 0 errors in N.NNN seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in N.NNN seconds. False --Return-- /home/jml/src/zope.testing/trunk/src/zope/testing/doctest/__init__.py(360)set_trace()-None - pdb.Pdb.set_trace(self) (Pdb) p x *** NameError: NameError(name 'x' is not defined,) (Pdb) c Failure in test /home/jml/src/zope.testing/trunk/src/zope/testing/testrunner/testrunner-edge-cases.txt Traceback (most recent call last): File /usr/lib/python2.6/unittest.py, line 279, in run testMethod() File
Re: [Zope-dev] ./bin/test failing with trunk zope.testing
Hi. On Sun, Jul 18, 2010 at 5:50 PM, Jonathan Lange j...@mumak.net wrote: When running zope.testing's tests on my laptop, I get many failures. I've run the tests plenty of times before and haven't got these failures. Am a bit mystified, so I'd appreciate any help. Looks like the tests assume to be run under the zope.testing.testrunner: -runTest (zope.testing.testrunner.runner.SetUpLayerFailure) ? +runTest (zope.testrunner.runner.SetUpLayerFailure) but you end up with the one from zope.testrunner. If you pin zc.recipe.testrunner to version 1.2.0, that should do the trick for now. Someone should look into making the tests compatible with both testrunners or requiring the new zope.testrunner. 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] ./bin/test failing with trunk zope.testing
On Sun, Jul 18, 2010 at 5:56 PM, Hanno Schlichting ha...@hannosch.eu wrote: Hi. On Sun, Jul 18, 2010 at 5:50 PM, Jonathan Lange j...@mumak.net wrote: When running zope.testing's tests on my laptop, I get many failures. I've run the tests plenty of times before and haven't got these failures. Am a bit mystified, so I'd appreciate any help. Looks like the tests assume to be run under the zope.testing.testrunner: - runTest (zope.testing.testrunner.runner.SetUpLayerFailure) ? + runTest (zope.testrunner.runner.SetUpLayerFailure) but you end up with the one from zope.testrunner. If you pin zc.recipe.testrunner to version 1.2.0, that should do the trick for now. Someone should look into making the tests compatible with both testrunners or requiring the new zope.testrunner. Thanks. Actually, it turned out to be something of a pebkac. I was getting trunk from the old Launchpad branch (lp:~vcs-imports/zope.testing/trunk) rather than the new Launchpad branch (lp:zope.testing). With the new branch, everything works out of the box. Sorry for the noise. While we're here, if I want to patch the Zope testrunner, should I submit patches against zope.testing or zope.testrunner? jml ___ 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] ./bin/test failing with trunk zope.testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan Lange wrote: On Sun, Jul 18, 2010 at 5:56 PM, Hanno Schlichting ha...@hannosch.eu wrote: Hi. On Sun, Jul 18, 2010 at 5:50 PM, Jonathan Lange j...@mumak.net wrote: When running zope.testing's tests on my laptop, I get many failures. I've run the tests plenty of times before and haven't got these failures. Am a bit mystified, so I'd appreciate any help. Looks like the tests assume to be run under the zope.testing.testrunner: -runTest (zope.testing.testrunner.runner.SetUpLayerFailure) ? +runTest (zope.testrunner.runner.SetUpLayerFailure) but you end up with the one from zope.testrunner. If you pin zc.recipe.testrunner to version 1.2.0, that should do the trick for now. Someone should look into making the tests compatible with both testrunners or requiring the new zope.testrunner. Thanks. Actually, it turned out to be something of a pebkac. I was getting trunk from the old Launchpad branch (lp:~vcs-imports/zope.testing/trunk) rather than the new Launchpad branch (lp:zope.testing). With the new branch, everything works out of the box. Sorry for the noise. While we're here, if I want to patch the Zope testrunner, should I submit patches against zope.testing or zope.testrunner? Good question. We intend to remove all the real code in zope.testing.testrunner at some point, leaving only backward- compatibility imports in its place. At this point, if you are still using the one from zope.testing in your projects, I would say to submit the patch against that: we should be able to use 'patch -pN' to get it merged, likely. Trds. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkxDKv8ACgkQ+gerLs4ltQ5KLwCdHOtMwzU1AZJc3B6PEoWmu0FW CJcAn3w75+CTNuYi/PX/tthU8UEG1Muv =saXV -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 )
