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 care now, not
whenever you can get around to it. Please, if you can help, do!
Again, if we don't get these ironed out, our CI workflow will continue
to be less than useful. If builds fail, for instance, we can't
auto-generate packages for testing. And if manual intervention is
required to restart builds that fail for validation, the workflow is
slowed down - each build and test run takes 15-20 minutes, and in ASF
Jenkins we can't run all of our builds in parallel due to limited
resources.
My last resort is to simply disable unreliable test cases, or move them
out of the default build-and-test workflow. I really don't want to have
to do this...but it remains an option.
-Joan
# Open Issues
COUCHDB-3344: EUnit: compaction_daemon_tests timing out
COUCHDB-3343: JS: show_documents failure
COUCHDB-3342: JS: design_docs expected '"ok"', got '"ko"'
COUCHDB-3341: EUnit: config listener unknown failure
COUCHDB-3340: EUnit: syslog timeout
COUCHDB-3339: EUnit: couch_mrview_red_views_tests throw:error
# Recently Closed Issues
1. test/javascript/tests/reduce_builtin.js
Error: {exit_status,139}
Exit code 139 is a SIGSEGV which may have been related to a libc bug
on or around 2017-03-21. Going to ignore this one unless it pops up
again.
2. Documentation build failure on CentOS 6
I've tweaked the couchdb user in the Docker CentOS 6 image to see
/usr/local/bin/python ahead of /usr/bin/python, and symlinked
/usr/bin/python34 to /usr/local/bin/python. This allows the build to
succeed, though 2 "Python 2-isms" that sneaked into our run scripts
needed to be fixed first. You can see the small tweaks necessary here:
https://gitbox.apache.org/repos/asf?p=couchdb.git;a=commitdiff;h=5bfedc49b8b1c8a68d39e81a31b3f522d30292e7
3. npm-related build failure
All Docker images have been upgraded to node 6 / npm 3 which has
eliminated the problem.
