Hey there,
Failures with reason "eunit_replicator"
Replicator tests were fixed very recently and should be fine since *now*.
That's great news!
Failures with reason "eunit_compression"
Compression failure is something new and seems like we're rarely flaky
in this test. Need magic debug io:format/2 for the rescue.
Yes, sure, whatever that means ;D (I don't even Erlang...)
Failures with reason "network"
Failures with reason "docker"
Failures with reason "libdl"
I'd say this are one time incidents and can be ignored for now. If one
of these happen more often, we would need to investigate (or maybe ASF
infra), but not right now.
> Failures with reason "aborted"
Actual reason is:
/usr/src/couchdb/apache-couchdb-2.0.0-7e892d6/bin/couchjs: error while
loading shared libraries: libmozjs185.so.1.0: cannot open shared
object file: No such file or directory
So seems like SpiderMokey was not installed correctly.
Yes, the Docker container was not set up correctly when this build ran.
That's why I aborted it manually in Jenkins. As I said, the "abort"
builds can be ignored.
P.S. Also it would be nice to send a notification about build failure
to dev@ ML to let us be aware about.
Of course, this is the plan. I would like to get them stable first,
though. My experience is that people tend to ignore failing builds very
fast if they saw a few builds fail for the "wrong" reason.
Cheers
Bastian
