Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Run flaky tests separately

See original GitHub issue

We have a handful of flaky tests which, when failed, require running the whole Travis job.

This rerun will run all the test suite so it’ll be very inefficient.

Instead, we could mark the flaky tests and run them separately so the flaky-test-job is faster to run and a job failure easier to diagnose.

Examples of flaky tests:

com.lightbend.lagom.scaladsl.testkit.ServiceTestSpec (also javadsl)
com.lightbend.lagom.internal.cluster.ClusterDistributionSpec
com.lightbend.lagom.scaladsl.persistence.cassandra.CassandraClusteredPersistentEntitySpec (also javadsl)

Issue Analytics

State:
Created 5 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

patriknwcommented, Feb 11, 2020

When moving forward I suggest that we create one issue for each test class (or category of tests) that is failing and then ping that issue when it fails again. In that way we can get a feeling for how often it fails.

Collecting (linking to) logs is also very important to be able to fix test failures.

0reactions

patriknwcommented, Mar 3, 2020

Closing this ticket in favor of the more specific tickets.