davisp commented on a change in pull request #2367: Rework CI setup
URL: https://github.com/apache/couchdb/pull/2367#discussion_r362668442
##########
File path: build-aux/Jenkinsfile.full
##########
@@ -486,21 +457,92 @@ pipeline {
} // post
} // stage
+ /*
+ *
+ * This is just taking too long to run. Right now, the khash tests are
timing out
+ * on the IBM servers:
+ *
+ * [2019-12-31T20:58:48.704Z] khash randomized test
+ * [2019-12-31T20:59:04.869Z] khash_test:103: randomized_test_
(State matches dict implementation)...*timed out*
Review comment:
Sorry, I don't think I was clear enough earlier. What I was asking/proposing
was that we create a new type of nightly build that is something like "Nightly
Soak Test" where we jack up all of the values for our property/long unit tests
that runs once a day on only a single platform.
My current approach is the opposite in that we tune down some parameters on
PRs only as opposed to everything except the soak test build.
Also to be clear, these long running tests are actually not entirely
supposed to be "unit tests" per se. The property based testing is (in my
experience) supposed to *generate* unit tests. The workflow would basically be
something like, design your property, run it for many hours, any failures are
added as regression tests. And the "run for hours" part is executed before
major events like large PRs and releases and so on.
And alternatively, something else we could do is pull all of those tests out
into a separate manual build that *only* runs the property tests and actually
does run them for hours on a manual button push.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
