[TEST] increase logger level until we know what is going on

We have an issue for it too: https://github.com/elastic/elasticsearch/issues/18121
This commit is contained in:
Britta Weber 2016-05-13 12:59:41 +02:00
parent a40c397c67
commit e7c17fc9fb
1 changed files with 3 additions and 1 deletions

View File

@ -62,6 +62,7 @@ import org.elasticsearch.index.store.IndexStore;
import org.elasticsearch.indices.InvalidIndexNameException;
import org.elasticsearch.repositories.RepositoriesService;
import org.elasticsearch.repositories.RepositoryException;
import org.elasticsearch.test.junit.annotations.TestLogging;
import java.nio.channels.SeekableByteChannel;
import java.nio.file.Files;
@ -1289,9 +1290,10 @@ public class SharedClusterSnapshotRestoreIT extends AbstractSnapshotIntegTestCas
assertThat(getSnapshotsResponse.getSnapshots().size(), equalTo(0));
}
@TestLogging("_root:DEBUG") // this fails every now and then: https://github.com/elastic/elasticsearch/issues/18121 but without
// more logs we cannot find out why
public void testReadonlyRepository() throws Exception {
Client client = client();
logger.info("--> creating repository");
Path repositoryLocation = randomRepoPath();
assertAcked(client.admin().cluster().preparePutRepository("test-repo")