Hi everyone,
Time for the weekend update, now that the monorepo merge has landed.
# TL;DR
1 new ticket filed for a recurring issue. No help has materialized
in helping get rid of currently failing tests :( Please help!
# New Issues
COUCHDB-3352: JS: couchjs SIGSEGVs
Seen this one before but d
e shell
has a different locale set than the non-interactive shell inside
Docker, and the latter was trying to decode it to ASCII (and failing).
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Monday, March 27, 2017 4:26:46 PM
> Subjec
Monday update: we have 2 new test failures, 1 test harness failure,
and 1 resolved issue (Thanks Jay Doane!)
# New Issues
COUCHDB-3345: JS: stats.js silent failure
The test simply shows 'fail' with no tracebacks or further info.
Silent failures are troubling.
COUCHDB-3346: JS: reduce.js "JSO
Another update to my original email.
TL;DR: 3 more sporadic failures in the test suite have shown up, and the
build issue on CentOS 6 has been ironed out. Help still needed!
I decided to move to JIRA tickets for everything, but don't let this
fool you: these test cases need some tender loving car
Replying to my original email with an update.
Reminder:
The goal here is to get CI builds useful for everyone. That means stable
builds with no test failures, so that when a status turns from passing
to failed, it actually means something. Your help to get us there is
*very much appreciated*. :D
> On 20 Mar 2017, at 06:50, Joan Touzet wrote:
>
> Hello,
>
> I've been getting our CI workflows cleaned up a bit, including
> re-enabling our OS matrix builds on Apache's Jenkins. Today, I finally
> got my first all-green build on Jenkins and Travis at the same time. It
> was a LOT harder than
dev@couchdb.apache.org
> > Sent: Tuesday, March 21, 2017 12:26:29 PM
> > Subject: Re: Stabilizing our automated builds - help needed!
> >
> > Oops, well spotted Jan
> > Upgrading to node 6 should fix this
> >
> >
> > On Tue, 21 Mar 2017 at 4:07 PM Jan Lehn
work_queue_tests.erl, line 182)
**error:{badmatch,timeout}
Never seen this one before.
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Wednesday, March 22, 2017 6:02:55 PM
> Subject: Re: Stabilizing our automated builds -
Thanks for the info Jay!
Erlangers, I still need your help addressing the remaining eunit
failures.
-Joan
- Original Message -
> From: "Jay Doane"
> To: dev@couchdb.apache.org, "Joan Touzet"
> Sent: Monday, March 20, 2017 2:59:12 AM
> Subject: Re:
arren Smith"
> To: dev@couchdb.apache.org
> Sent: Tuesday, March 21, 2017 12:26:29 PM
> Subject: Re: Stabilizing our automated builds - help needed!
>
> Oops, well spotted Jan
> Upgrading to node 6 should fix this
>
>
> On Tue, 21 Mar 2017 at 4:07 PM Jan Lehnardt wrote:
&g
Oops, well spotted Jan
Upgrading to node 6 should fix this
On Tue, 21 Mar 2017 at 4:07 PM Jan Lehnardt wrote:
> Garren, the log shows
>
> npm ERR! node v4.2.6
> npm ERR! npm v2.14.12
>
> So yeah, npm 3 and node 6 would be preferable :)
>
> Joan, let me know if you need help with any of this.
>
Garren, the log shows
npm ERR! node v4.2.6
npm ERR! npm v2.14.12
So yeah, npm 3 and node 6 would be preferable :)
Joan, let me know if you need help with any of this.
Best
Jan
--
> On 21 Mar 2017, at 13:06, Garren Smith wrote:
>
> Hi Joan,
>
> What version of node and npm is on the build s
Hi Joan,
What version of node and npm is on the build server? I did some googling
around and the best I can find around that npm issue is that it might be an
older npm or there is some connection issues with npm.
We use node 6 with Travis and haven't seen this issue. Is it possible to
cache npm in
Great work Joan, thank you for putting up with all the crap we let pile up.
Let’s not have that happen again!
I think I fixed the JS test case here:
https://github.com/apache/couchdb/commit/69a71d976081cefb25903fd3165de821fc20c86c
Best
Jan
--
> On 20 Mar 2017, at 06:50, Joan Touzet wrote:
>
On Sun, Mar 19, 2017 at 10:50 PM, Joan Touzet wrote:
>
> --
> module 'couch_log_writer_syslog_test'
> couch_log_writer_syslog_test: couch_log_writer_syslog_test_...*timed
> out*
> undefined
>
> Not sure why this times out, can we increase the timeout maybe?
>
Another
Hello,
I've been getting our CI workflows cleaned up a bit, including
re-enabling our OS matrix builds on Apache's Jenkins. Today, I finally
got my first all-green build on Jenkins and Travis at the same time. It
was a LOT harder than it should have been.
Why? Because our test suite (and build pr
16 matches
Mail list logo
