Closing the loop, a change was checked into master that reduces the
Elixir suite to run against an n=1 CouchDB cluster, permanently. This
should help significantly for now.
Any remaining Elixir test failures should have issues opened on them.
On 2019-12-14 12:29 p.m., Garren Smith wrote:
I’m
> On 14. Dec 2019, at 18:29, Garren Smith wrote:
>
> I’m a bit nervous to remove the full elixir test suite. The only partition
> tests are in the elixir suite. So we would have no test coverage for any of
> that if we remove this. Given that we want to make this the best CouchDB
> release
I’m a bit nervous to remove the full elixir test suite. The only partition
tests are in the elixir suite. So we would have no test coverage for any of
that if we remove this. Given that we want to make this the best CouchDB
release ever it feels counter-intuitive to them be removing tests.
I also
On Thu, Dec 12, 2019 at 11:27 PM Joan Touzet wrote:
> Jay, consider this a +1 to remove those if you can get to them before I do.
>
Joan, I don't think I was clear, but when I said
> I'm +1 to removing these tests temporarily.
by "these tests" I actually meant all the elixir tests, not just the
Jay, consider this a +1 to remove those if you can get to them before I do.
If this makes the Elixir tests useful again, then it's a good compromise.
-Joan
On 2019-12-13 2:18 a.m., Jay Doane wrote:
I've been trying to merge into master for the last 24+ hours, and have
restarted the build
I've been trying to merge into master for the last 24+ hours, and have
restarted the build about 10 times so far, but it has yet to pass.
I kept track of failures, and these came up numerous times:
1) test GET /dbname/_design_docs (PartitionDDocTest)
Hi Adam,
As long as someone is working on fixing the Elixir tests, fine. They
*are* failing significantly more often on Jenkins than on Travis, for
what it's worth.
All our work to build a much better setup for Jenkins may be lost if
people don't fix these tests promptly.
Would a suitable
Hi Joan,
I’ve seen the Elixir suite implicated more frequently as well. I haven’t done
the analysis to see if the failures are concentrated in one or two flakes or if
they’re more evenly distributed. If it’s a small number of flaky tests I think
we have time to fix/disable them rather than
Hi again,
As I've been looking more closely at the CI suite for the Jenkins
transition, I've noticed that our Elixir test cases are actually the
most likely to fail. In 6 consecutive CI runs, 5 runs failed due to
failures in the Elixir suite. (The 6th failed due to a JS test failure.)
We
