helloNext292 commented on issue #524: j...@apache.org
URL: https://github.com/apache/couchdb/issues/524#issuecomment-301379449
@janl
This is an automated message from the Apache Git Service.
To respond to the message,
helloNext292 commented on issue #524: j...@apache.org
URL: https://github.com/apache/couchdb/issues/524#issuecomment-301379449
@janl
This is an automated message from the Apache Git Service.
To respond to the message,
helloNext292 opened a new issue #524: j...@apache.org
URL: https://github.com/apache/couchdb/issues/524
if you ever crossed my path again, I promise you I will beat you to death
with a rod like I would have had we been in highschool together. Never ever do
this again - don't shove your
nickva commented on issue #519: chore: double test timeout see COUCHDB-3408
URL: https://github.com/apache/couchdb/pull/519#issuecomment-301369649
+1
This is an automated message from the Apache Git Service.
To respond to
nickva commented on issue #517: chore: add debugging for failing test case, see
COUCHDB-3415
URL: https://github.com/apache/couchdb/pull/517#issuecomment-301369616
+1
Though as mentioned in other PR ?debugFmt I think the preferred way to print
during EUnit tests. Minor nit though.
nickva commented on issue #518: chore: add debugging for failing test case, see
COUCHDB-3413
URL: https://github.com/apache/couchdb/pull/518#issuecomment-301369355
+1
At first I was about to mention that EUnit captures and hides all the stdout
output but then noticed we send output
redgeoff commented on issue #9: Understanding how to run a cluster
URL: https://github.com/apache/couchdb-docker/issues/9#issuecomment-301363800
Thanks to @janl's help, I've managed to get around the sticky sessions by
using the exact same line (including the pbkdf2 hash) in the [admins]
wohali commented on issue #9: Understanding how to run a cluster
URL: https://github.com/apache/couchdb-docker/issues/9#issuecomment-301362406
Again, sticky sessions are not required and will definitely affect your
performance.
>> A session cookie acquired on one node is
nickva commented on issue #521: chore: increase timeout for pausing writer
COUCHDB-3384
URL: https://github.com/apache/couchdb/pull/521#issuecomment-301362118
+1
This is an automated message from the Apache Git Service.
To
nickva commented on issue #522: chore: increase timeout for compaction daemon
tests COUCHDB-3344
URL: https://github.com/apache/couchdb/pull/522#issuecomment-301362008
>
```
--define(TIMEOUT, 6).
+-define(TIMEOUT, 120).
```
Meant to do 12 (x2) probably not
redgeoff commented on issue #9: Understanding how to run a cluster
URL: https://github.com/apache/couchdb-docker/issues/9#issuecomment-301319482
Update as there are 2 threads :). From
https://github.com/klaemo/docker-couchdb/issues/93#issuecomment-301318230:
@peanutpi you rock! I
[
https://issues.apache.org/jira/browse/COUCHDB-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009681#comment-16009681
]
Jan Lehnardt commented on COUCHDB-3343:
---
Added PR for debugging:
janl opened a new pull request #523: chore: add dedbugging for failing test
COUCHDB-3343
URL: https://github.com/apache/couchdb/pull/523
## Overview
Added debug out to failing test.
## Testing recommendations
## JIRA issue number
[
https://issues.apache.org/jira/browse/COUCHDB-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009675#comment-16009675
]
Jan Lehnardt commented on COUCHDB-3344:
---
PR to bump timeout yet again:
janl opened a new pull request #522: chore: increase timeout for compaction
daemon tests COUCHDB-3344
URL: https://github.com/apache/couchdb/pull/522
## Overview
Increased test timeout, trying to reduce flakyness.
## Testing recommendations
##
[
https://issues.apache.org/jira/browse/COUCHDB-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009674#comment-16009674
]
Jan Lehnardt commented on COUCHDB-3348:
---
Possibly same 500 or other error on db create as in
[
https://issues.apache.org/jira/browse/COUCHDB-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009673#comment-16009673
]
Jan Lehnardt commented on COUCHDB-3352:
---
I there any way to get a trace/core dump file for this?
[
https://issues.apache.org/jira/browse/COUCHDB-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009671#comment-16009671
]
Jan Lehnardt commented on COUCHDB-3356:
---
possibly the spurious 500 again
> JS: jsonp test fail
>
[
https://issues.apache.org/jira/browse/COUCHDB-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009670#comment-16009670
]
Jan Lehnardt commented on COUCHDB-3382:
---
I bet this is another spurious 500 error.
> EUnit:
[
https://issues.apache.org/jira/browse/COUCHDB-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009669#comment-16009669
]
Jan Lehnardt commented on COUCHDB-3384:
---
PR to double timeout:
janl opened a new pull request #521: chore: increase timeout for pausing writer
COUCHDB-3384
URL: https://github.com/apache/couchdb/pull/521
## Overview
Double the timeout for pausing the source writer.
## Testing recommendations
## JIRA issue number
[
https://issues.apache.org/jira/browse/COUCHDB-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009668#comment-16009668
]
Jan Lehnardt commented on COUCHDB-3396:
---
cursory glance at application:start() et.al. docs didn’t
[
https://issues.apache.org/jira/browse/COUCHDB-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009665#comment-16009665
]
Jan Lehnardt commented on COUCHDB-3401:
---
Server logs will help to see what causes the 500 here and
[
https://issues.apache.org/jira/browse/COUCHDB-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009664#comment-16009664
]
Jan Lehnardt commented on COUCHDB-3405:
---
I think we have to wait for the server log PR to land
janl opened a new pull request #520: chore: more robust test
URL: https://github.com/apache/couchdb/pull/520
## Overview
Looks like replication can finish before we get the status, or that the task
api doesn?t get populated by the time we ask for the status.
The
[
https://issues.apache.org/jira/browse/COUCHDB-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009663#comment-16009663
]
Jan Lehnardt commented on COUCHDB-3406:
---
Added PR for a potential fix:
[
https://issues.apache.org/jira/browse/COUCHDB-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009650#comment-16009650
]
Jan Lehnardt commented on COUCHDB-3408:
---
PR to double timeout:
janl opened a new pull request #519: chore: double test timeout see COUCHDB-3408
URL: https://github.com/apache/couchdb/pull/519
## Overview
Increase timeout for test case that has timed out in CI before.
## Testing recommendations
Needs to run
[
https://issues.apache.org/jira/browse/COUCHDB-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009648#comment-16009648
]
Jan Lehnardt commented on COUCHDB-3413:
---
I opened a PR that adds debugging for this case:
janl opened a new pull request #518: chore: add debugging for failing test
case, see COUCHDB-3413
URL: https://github.com/apache/couchdb/pull/518
## Overview
Add test case to see what trips up this test case in COUCHDB 3413.
I assume it is one where the cluster
[
https://issues.apache.org/jira/browse/COUCHDB-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009647#comment-16009647
]
Jan Lehnardt commented on COUCHDB-3415:
---
I filed a PR that helps with debugging:
janl opened a new pull request #517: chore: add debugging for failing test
case, see COUCHDB-3415
URL: https://github.com/apache/couchdb/pull/517
## Overview
Add test case to see what trips up this test case in COUCHDB 3415.
This could be as simple as a newline
32 matches
Mail list logo
