infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-18408) docker-related failure on ubuntu-1
Date Tue, 21 May 2019 05:16:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-18408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-18408:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

> docker-related failure on ubuntu-1
> ----------------------------------
>
>                 Key: INFRA-18408
>                 URL: https://issues.apache.org/jira/browse/INFRA-18408
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Julian Reschke
>            Priority: Major
>
> We see frequent but non-reproducable test failures related to instantiating Docker images.
> A recent example is on ubuntu-1 in <https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/2431/consoleText>:
> [ERROR] oak6423(org.apache.jackrabbit.oak.plugins.document.mongo.MongoDocumentStoreTest)
 Time elapsed: 0.461 s  <<< ERROR!
> java.lang.RuntimeException: Unable to start docker container: DockerConfig{name=MongoDB}
> 	at com.arakelian.docker.junit.DockerRule$StatementWithDockerRule.evaluate(DockerRule.java:79)
> 	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> 	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> 	at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> Caused by: org.junit.internal.runners.model.MultipleFailureException: There were 2 errors:
>   com.mongodb.MongoNodeIsRecoveringException(Command failed with error 11600 (InterruptedAtShutdown):
'interrupted at shutdown' on server localhost:33543. The full response is { "ok" : 0.0, "errmsg"
: "interrupted at shutdown", "code" : 11600, "codeName" : "InterruptedAtShutdown" })
>   java.lang.NullPointerException(null)
> 	at org.junit.runners.model.MultipleFailureException.assertEmpty(MultipleFailureException.java:67)
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:39)
> 	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> 	at com.arakelian.docker.junit.DockerRule$StatementWithDockerRule.evaluate(DockerRule.java:76)
> 	... 19 more
> Any idea what's wrong here?
> FWIW, I recently had a similar issue on my local machine, and deleting all docker images
apparently fixed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message