| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |\
| |
| |
| | |
jenkins-junit-reports-and-jenkins-env
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
It doesn't work on Jenkins but worked locally.
Noticed that we started chttpd even though the clustered port was never used.
Add a wait function in `db_url/1` to make sure to wait until the db is
available via the HTTP interface before continuing.
|
| | |
| |
| |
| | |
This reverts commit 174105e6ae2c644fa0c5b52c265471ce12045160.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Needed to avoid timeouts on ASF Jenkins build farm.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This improves reliability because that time isn't charged to the test,
and also speeds up the test.
|
| | |
| |
| |
| |
| | |
The "Should copy local docs after split in four" test was occasionally
timing out in CI.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This work moves the builds back into the workspace, using a separate
sub-directory per platform to avoid clashes between builds caused by
JENKINS-57454. It also breaks out the steps into a pair of sequential
stages within each each parallel stage of the build, which gives us
better visibility into the progress of the build, and also sets us up
to capture test results and expose them directly via Jenkins UI for
faster problem determination.
|
| |/ |
|
| |
|
|
| |
Bash has `let` but other shells might not have it.
|
| |
|
|
|
|
|
| |
And remove the js version. Elixir test has been running decently on Travis from
what I observed. However, it was disabled on jenkins runs. With a recent
hardware upgrade, perhaps there is chance this test will start passing there
too.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`local` replication endpoints do something completely unexpected from a user's
point of view -- they replicate to and from node local databases on a random
node. The only way this worked correctly was if someone used the backend port
(:5986) with a single node database. However, that port is getting closed for 3.x
release as well, so it makes even less sense to keep this functionality around.
For more discussion and voting results see ML list:
https://lists.apache.org/thread.html/ddcd9db93cee363db7da571f5cbc7f2bd24b881a34e1ef734d6a0a1c@%3Cdev.couchdb.apache.org%3E
The `_replicate` HTTP "hack" was left as is, since it does work more or less,
However it is inconsistent with what _replicator docs do so we should probably
deprecated it and remove it in 4.x.
|
| |
|
|
|
| |
Fix a race condition in state matching, also parameterize the state
field in wait_state.
|
| |
|
|
|
|
|
| |
Whole app is retried 2 extra times if it fails.
Added to *nix Makefile only for now. May not be needed for Windows as this is
for CI flakiness mostly.
|
| |\
| |
| | |
Exunit simplified
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Proactively increase timeout for PBKDF2 test
This test was taking 134s in a recent run, which is uncomfortably close
to the threshold.
* Extend timeouts for all reshard API tests
We're observing timeouts on various tests in this suite so let's keep
it consistent and increase timeouts across the board.
* Bump default timeout for all mem3_reshard tests
A couple of these tests were exceeding the default timeout under normal
circumstances, but many of them do a significant amount of work, so for
simplicity we set a module-wide timeout and apply it consistently
throughout.
* Modernize the sync_security test setup/teardown
This test actually doesn't do much real work, but I think what was
happening is that the setup and teardown time was being charged to the
test itself. I've refactored it to use a more modern scaffolding
following some of our more recent additions to the test suite, but have
left the timeout at the default to test this hypothesis.
* Increase timeouts on more heavyweight mem3 tests
* Extend timeouts for replication tests
|
| |
|
|
|
|
|
|
| |
Config setting was asynchronous and the waiting function was not
waiting for the actual state value to change just that the state
function was returning.
The fix is to wait for the config value to propagate to the state.
|
| |
|
|
|
|
| |
These two tests are reliably timing out on ARM hardware in Jenkins.
They do a lot of individual btree operations so this is not entirely
surprising. Appropriate course of action here is to raise the timeout.
|
| |
|
|
|
|
|
|
|
| |
This changes `couch_file` to ensure that errors are raised when a call
to `fsync` fails. It will also stop the couch_file process to ensure
that anything handling a failed `fsync` won't attempt to retry the
operation and experience issues discovered by Postgres [1].
[1] http://danluu.com/fsyncgate/
|
| | |
|
| |
|
|
|
|
| |
The code has "infinity" as the default value and not 0
See src/couch_replicator/src/couch_replicator_changes_reader.erl
|
| |
|
|
|
|
|
|
|
|
|
| |
Bumped elixir version to 1.7.4 as 1.6.6 wasn't built with Erlang 22
support.
Also moving straight to 22.0.5 since 22.0 in travis crashed with a
segmentation fault. Some of the release comments in the point release
mention VM crashes, so it seems to check out.
Fixes https://github.com/apache/couchdb/issues/2069
|
| |\
| |
| | |
Update ioq to 2.1.2
|
| |/
|
|
| |
* Fix the case when we call log10 with 0
|
| |\
| |
| | |
Add "Dreyfus" (Erlang side of Search) to CouchDB
|
| | |\
| |/
|/| |
|
| | | |
|
