My issue is that the process for a typically release takes me about ~2
hrs to fully test, build packages and vote. I spent about 6 hours
yesterday (that I really didn't have, but really care about CouchDB),
and still was unable to get a successful rpm to build because test
failures. These tests also take a very long time to complete, so
re-running in a loop until they pass is a tough proposition.
What I'd hate to see is a downstream release person getting this,
expecting to spend an hour on it, and having it eat half their day.
Also, the current builds break my "production ready" criteria
internally, and I think this will be the same for others.
While I fully realize that my vote won't slow this from being released,
I've personally been unable to actually use 1.3.0, as I'm still stuck
trying to get tests to fully run.
As for detailed information, I started another thread for this, and I
can give any additional details necessary as they are requested.
Additionally, I'll spend some time today mucking about with the tests a
bit to see if I can get something useful for an actual report.
Wendall
On 03/11/2013 04:51 PM, Noah Slater wrote:
One last comment here before I pipe down. Could you send through all of
the relevant logs? That will be very helpful for diagnosing the problems
you are running in to. (Despite my arguments about how I believe we can
release with flaky tests, this is obviously a serious matter and we need to
investigate so we understand it thoroughly before we proceed.)
On 11 March 2013 22:42, Wendall Cada <[email protected]> wrote:
On 03/11/2013 03:05 PM, Noah Slater wrote:
Flakey tests are frustrating, but I don't think they will block the
release.
I think they are blockers. CouchDB already has a problem with downstream
maintainers keeping packages current. This effectively pushes these
problems onto the packagers. IMO, this is a critical PR issue as well. Want
to improve the project image? Quit shipping builds that require hours of
work for packagers. Additionally, failing tests block any production
packages for our company. I set these standards, and I don't think this is
unreasonable, nor different from what you'd find with other companies using
couchdb seriously. Encouraging packagers to disable the test suite isn't
good either. I still maintain a -1 and think this build is broken.
Can you provide details of your segfault?
I made note of it in this post http://mail-archives.apache.**
org/mod_mbox/couchdb-dev/**201303.mbox/%3C513E493B.80707%**4083864.com%3E<http://mail-archives.apache.org/mod_mbox/couchdb-dev/201303.mbox/%3C513E493B.80707%4083864.com%3E>
Wendall
On 11 March 2013 21:22, Wendall Cada <[email protected]> wrote:
-1
Tests fail or unable to be run at all on all my target platforms. Fedora
18/Centos 6/Amazon Linux 2012.09
Once the suite finally runs all the way through, I can manually get the
failing test to run on Fedora 18. Centos 6/Amazon Linux just segfaults.
While others may not think this is a -1, I think the tests should ship
in a
condition that they are able to be run. Building should be getting better
for distros, not worse, this is a major regression from my perspective.
Wendall
On 03/10/2013 02:24 PM, Noah Slater wrote:
Dear community,
I would like to call a vote on Apache CouchDB 1.3.0-rc.1.
We encourage the whole community to download and test these release
artefacts so that any critical issues can be resolved before the release
is
made. Everyone is free to vote on this release, so get stuck in!
The release artefacts we are voting on are available here:
wget
https://dist.apache.org/repos/****dist/dev/couchdb/source/1.3.**0/**<https://dist.apache.org/repos/**dist/dev/couchdb/source/1.3.0/**>
rc.1/apache-couchdb-1.3.0.tar.****gz<https://dist.apache.org/**
repos/dist/dev/couchdb/source/**1.3.0/rc.1/apache-couchdb-1.3.**
0.tar.gz<https://dist.apache.org/repos/dist/dev/couchdb/source/1.3.0/rc.1/apache-couchdb-1.3.0.tar.gz>
wget
https://dist.apache.org/repos/****dist/dev/couchdb/source/1.3.**0/**<https://dist.apache.org/repos/**dist/dev/couchdb/source/1.3.0/**>
rc.1/apache-couchdb-1.3.0.tar.****gz.asc<https://dist.apache.**
org/repos/dist/dev/couchdb/**source/1.3.0/rc.1/apache-**
couchdb-1.3.0.tar.gz.asc<https://dist.apache.org/repos/dist/dev/couchdb/source/1.3.0/rc.1/apache-couchdb-1.3.0.tar.gz.asc>
wget
https://dist.apache.org/repos/****dist/dev/couchdb/source/1.3.**0/**<https://dist.apache.org/repos/**dist/dev/couchdb/source/1.3.0/**>
rc.1/apache-couchdb-1.3.0.tar.****gz.ish<https://dist.apache.**
org/repos/dist/dev/couchdb/**source/1.3.0/rc.1/apache-**
couchdb-1.3.0.tar.gz.ish<https://dist.apache.org/repos/dist/dev/couchdb/source/1.3.0/rc.1/apache-couchdb-1.3.0.tar.gz.ish>
wget
https://dist.apache.org/repos/****dist/dev/couchdb/source/1.3.**0/**<https://dist.apache.org/repos/**dist/dev/couchdb/source/1.3.0/**>
rc.1/apache-couchdb-1.3.0.tar.****gz.md5<https://dist.apache.**
org/repos/dist/dev/couchdb/**source/1.3.0/rc.1/apache-**
couchdb-1.3.0.tar.gz.md5<https://dist.apache.org/repos/dist/dev/couchdb/source/1.3.0/rc.1/apache-couchdb-1.3.0.tar.gz.md5>
wget
https://dist.apache.org/repos/****dist/dev/couchdb/source/1.3.**0/**<https://dist.apache.org/repos/**dist/dev/couchdb/source/1.3.0/**>
rc.1/apache-couchdb-1.3.0.tar.****gz.sha<https://dist.apache.**
org/repos/dist/dev/couchdb/**source/1.3.0/rc.1/apache-**
couchdb-1.3.0.tar.gz.sha<https://dist.apache.org/repos/dist/dev/couchdb/source/1.3.0/rc.1/apache-couchdb-1.3.0.tar.gz.sha>
Please follow the test procedure here:
http://wiki.apache.org/****couchdb/Test_procedure<http://wiki.apache.org/**couchdb/Test_procedure>
<http://**wiki.apache.org/couchdb/Test_**procedure<http://wiki.apache.org/couchdb/Test_procedure>
Please remember that "rc.1" is an annotation. If the vote passes, these
artefacts will be released as Apache CouchDB 1.3.0.
Thanks,
