On Tuesday, June 12, 2012 at 1:55 AM, Randall Leeds wrote:
On Mon, Jun 11, 2012 at 3:24 AM, Benoit Chesneau bchesn...@gmail.com
(mailto:bchesn...@gmail.com) wrote:
On Sat, Jun 9, 2012 at 9:15 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) wrote:
Hey,
I've been
On Monday, June 11, 2012 at 6:57 PM, CGS wrote:
Let us know if any test fail and give us the log of the tests. The tests
themselves are pretty self explanatory. If not, at least some tests are
using the CouchDB log. So, I think there will be enough info for debugging.
CGS
Ok,
so I
On Tuesday, June 12, 2012 at 2:09 PM, CGS wrote:
Dubious, test returned 1 (wstat 256, 0x100) says that the permissions are
not in place (therefore, files cannot be created/access, processes are not
started/accessible and so on). Could you tell me where exactly you got that
error?
CGS
Well, the default installation requires root permissions as many paths are
accessible only as root (you did 'sudo make install', didn't you?). Also,
you do sudo apt-get install, so, the tests will be run under root
permissions. That's why I said in the README file that these tests should
be run as
On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
Well, the default installation requires root permissions as many paths are
accessible only as root (you did 'sudo make install', didn't you?). Also,
you do sudo apt-get install, so, the tests will be run under root
permissions. That's why I
Have you modified the parameters from test.cfg to point to your CouchDB
installation?
CGS
On Tue, Jun 12, 2012 at 2:57 PM, till klimp...@gmail.com wrote:
On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
Well, the default installation requires root permissions as many paths
are
Yes, pretty much:
https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
I haven't checked in detail, but – do those lib/etc paths get prefixed with
COUCHDB_TEST_PATH?
Till
--
till
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, June 12, 2012 at 3:07 PM,
COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
configure options. The rest gets this variable in front (e.g., if PREFIX
was set to / at the configuration stage, then COUCHDB_TEST_PATH should be
set to ). E.g., few things from my installation, I have:
- default.ini and
On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
configure options. The rest gets this variable in front (e.g., if PREFIX
was set to / at the configuration stage, then COUCHDB_TEST_PATH should be
set to ). E.g., few things
Can you do a test for me? Please, open an Erlang shell (erl) in tests/
directory (hopefully you will still have the test_util.beam file) and
copy-paste these lines (exit with CTRL+g and qEnter):
l(test_util).
test_util:init_code_path().
test_util:config_files().
l(couch_config).
3 test_util:config_files().
[/usr/etc/couchdb/default.ini,
/home/vagrant/buildbox/testsuite/tests/random_port.ini,
/usr/etc/couchdb/local.ini]
This is the problem – the prefix is not used for sysconfdir. The dir is in /etc
not in PREFIX/etc.
Till
--
till
Sent with Sparrow
OK. I understand.
For the moment, replace test_util.erl from utils with the file attached
here. This should remove COUCHDB_TEST_PATH from the path. I will rewrite
test_util.erl to get the paths independently for your repo.
CGS
On Tue, Jun 12, 2012 at 6:06 PM, till klimp...@gmail.com wrote:
Attachment didn't make it through – can you a patch/file?
On Tuesday, June 12, 2012 at 6:22 PM, CGS wrote:
OK. I understand.
For the moment, replace test_util.erl from utils with the file attached here.
This should remove COUCHDB_TEST_PATH from the path. I will rewrite
test_util.erl to
On Sat, Jun 9, 2012 at 9:15 PM, till klimp...@gmail.com wrote:
Hey,
I've been scratching my own itch and started building 1.2.0 for a couple
Ubuntu distributions.
It's a WIP but I was wondering the following:
1) It builds – but does it work? Is the best bet to run the test suite in
A patch and/or a repo somewhere would be nice :)
On Jun 11, 2012, at 09:08 , CGS wrote:
Hi,
I isolated the tests which are started with make check and make them run over
the default installation under Ubuntu 12.10. Please, let me know if it is
what you need (there is a README file in the
I agree – I also don't have to maintain this alone.
Once this is working as expected, I wanted to push the build stuff into a repo
where more people have access to and we could also created a 'team' on
launchpad to have more people contribute to this (or at least be able to).
Till
On
Not at all. After all, I do not do this for my personal interest, but for
this community. I am glad if I can help.
Cheers,
CGS
On Mon, Jun 11, 2012 at 3:58 PM, till klimp...@gmail.com wrote:
Hey,
thanks, I'm gonna test this shortly. Do you mind if I push it one of my
repo?
Till
On
Ok,
my working repo is here:
https://github.com/till/couchdb-deb
So does anyone have any idea how to debug failed test cases? They never failed
for me before. :D
Till
On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
Not at all. After all, I do not do this for my personal interest, but for
I submitted a bunch of new builds to the launchpad farm.
I tested Lucid (Ubuntu 10.04 LTS) so far (hit verify installation in futon).
If anyone wants to give one of these builds a go and give me feedback – feel
free to. ;-)
Till
Let us know if any test fail and give us the log of the tests. The tests
themselves are pretty self explanatory. If not, at least some tests are
using the CouchDB log. So, I think there will be enough info for debugging.
CGS
On Mon, Jun 11, 2012 at 5:12 PM, till klimp...@gmail.com wrote:
On Jun 9, 2012, at 21:15 , till wrote:
Hey,
I've been scratching my own itch and started building 1.2.0 for a couple
Ubuntu distributions.
Till, awesome! :)
It's a WIP but I was wondering the following:
1) It builds – but does it work? Is the best bet to run the test suite in
Hey,
[ CC'd user@ to get more feedback. ]
I made some progress.
I have builds for the following more or less ready:
* karmic
* lucid
* maverick
* oneiric
* natty
* precise
It's building and I am trying to refine the process a bit. So it might break in
between [aka WIP]. I'm just
Hey,
I've been scratching my own itch and started building 1.2.0 for a couple Ubuntu
distributions.
It's a WIP but I was wondering the following:
1) It builds – but does it work? Is the best bet to run the test suite in
futon, or is there something I could run on the command line when the
Hi,
I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
Unfortunately, I've never built a deb package, so, I cannot provide such a
package. Nevertheless, if you have any problem in building it, just let me
know and I will try to help.
About the mailing list, I suppose adding
24 matches
Mail list logo
