[jira] [Work logged] (BEAM-4051) python postcommit failure in docker-compose
[
https://issues.apache.org/jira/browse/BEAM-4051?focusedWorklogId=90171=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-90171
]
ASF GitHub Bot logged work on BEAM-4051:
Author: ASF GitHub Bot
Created on: 11/Apr/18 21:23
Start Date: 11/Apr/18 21:23
Worklog Time Spent: 10m
Work Description: aaltay closed pull request #5100: [BEAM-4051] Clean up
docker networks generated by hdfs integration tests.
URL: https://github.com/apache/beam/pull/5100
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
b/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
index 3e756da237c..6f527471d87 100755
--- a/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
+++ b/sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
@@ -35,6 +35,8 @@ cp -r ${ROOT_DIR}/model ${CONTEXT_DIR}/
PROJECT_NAME=$(echo hdfs_IT-${BUILD_TAG:-non-jenkins})
cd ${CONTEXT_DIR}
+# Clean up leftover unused networks. BEAM-4051
+docker network prune --force
time docker-compose -p ${PROJECT_NAME} build
time docker-compose -p ${PROJECT_NAME} up --exit-code-from test \
--abort-on-container-exit
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 90171)
Time Spent: 50m (was: 40m)
> python postcommit failure in docker-compose
> ---
>
> Key: BEAM-4051
> URL: https://issues.apache.org/jira/browse/BEAM-4051
> Project: Beam
> Issue Type: Bug
> Components: testing
>Reporter: Udi Meiri
>Assignee: Udi Meiri
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Python_Verify/4661/consoleText]
> Error is:
> Creating network
> "hdfs_it-jenkins-beam_postcommit_python_verify-4661_test_net" with the
> default driver
> could not find an available, non-overlapping IPv4 address pool among the
> defaults to assign to the network
>
> I assume that the issue is that the networks being created are not being
> cleaned up.
> Looking briefly online the solution seems to be something like "docker
> network prune --force".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (BEAM-4051) python postcommit failure in docker-compose
[ https://issues.apache.org/jira/browse/BEAM-4051?focusedWorklogId=90166=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-90166 ] ASF GitHub Bot logged work on BEAM-4051: Author: ASF GitHub Bot Created on: 11/Apr/18 20:57 Start Date: 11/Apr/18 20:57 Worklog Time Spent: 10m Work Description: udim commented on issue #5100: [BEAM-4051] Clean up docker networks generated by hdfs integration tests. URL: https://github.com/apache/beam/pull/5100#issuecomment-380593272 R: @aaltay Postcommit passes: https://builds.apache.org/job/beam_PostCommit_Python_Verify/4666/console This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 90166) Time Spent: 40m (was: 0.5h) > python postcommit failure in docker-compose > --- > > Key: BEAM-4051 > URL: https://issues.apache.org/jira/browse/BEAM-4051 > Project: Beam > Issue Type: Bug > Components: testing >Reporter: Udi Meiri >Assignee: Udi Meiri >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > [https://builds.apache.org/job/beam_PostCommit_Python_Verify/4661/consoleText] > Error is: > Creating network > "hdfs_it-jenkins-beam_postcommit_python_verify-4661_test_net" with the > default driver > could not find an available, non-overlapping IPv4 address pool among the > defaults to assign to the network > > I assume that the issue is that the networks being created are not being > cleaned up. > Looking briefly online the solution seems to be something like "docker > network prune --force". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-4051) python postcommit failure in docker-compose
[ https://issues.apache.org/jira/browse/BEAM-4051?focusedWorklogId=90106=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-90106 ] ASF GitHub Bot logged work on BEAM-4051: Author: ASF GitHub Bot Created on: 11/Apr/18 18:41 Start Date: 11/Apr/18 18:41 Worklog Time Spent: 10m Work Description: udim commented on issue #5100: [BEAM-4051] Clean up docker networks generated by hdfs integration tests. URL: https://github.com/apache/beam/pull/5100#issuecomment-380555021 run python postcommit This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 90106) Time Spent: 0.5h (was: 20m) > python postcommit failure in docker-compose > --- > > Key: BEAM-4051 > URL: https://issues.apache.org/jira/browse/BEAM-4051 > Project: Beam > Issue Type: Bug > Components: testing >Reporter: Udi Meiri >Assignee: Udi Meiri >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > [https://builds.apache.org/job/beam_PostCommit_Python_Verify/4661/consoleText] > Error is: > Creating network > "hdfs_it-jenkins-beam_postcommit_python_verify-4661_test_net" with the > default driver > could not find an available, non-overlapping IPv4 address pool among the > defaults to assign to the network > > I assume that the issue is that the networks being created are not being > cleaned up. > Looking briefly online the solution seems to be something like "docker > network prune --force". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-4051) python postcommit failure in docker-compose
[
https://issues.apache.org/jira/browse/BEAM-4051?focusedWorklogId=90103=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-90103
]
ASF GitHub Bot logged work on BEAM-4051:
Author: ASF GitHub Bot
Created on: 11/Apr/18 18:32
Start Date: 11/Apr/18 18:32
Worklog Time Spent: 10m
Work Description: udim commented on a change in pull request #5100:
[BEAM-4051] Clean up docker networks generated by hdfs integration tests.
URL: https://github.com/apache/beam/pull/5100#discussion_r180855485
##
File path:
sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
##
@@ -35,6 +35,8 @@ cp -r ${ROOT_DIR}/model ${CONTEXT_DIR}/
PROJECT_NAME=$(echo hdfs_IT-${BUILD_TAG:-non-jenkins})
cd ${CONTEXT_DIR}
+# TODO: prune?
+docker network ls
Review comment:
I first needed to prove my hunch, and I don't know of a way to run
postcommits on jenkins without creating a PR.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 90103)
Time Spent: 20m (was: 10m)
> python postcommit failure in docker-compose
> ---
>
> Key: BEAM-4051
> URL: https://issues.apache.org/jira/browse/BEAM-4051
> Project: Beam
> Issue Type: Bug
> Components: testing
>Reporter: Udi Meiri
>Assignee: Udi Meiri
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Python_Verify/4661/consoleText]
> Error is:
> Creating network
> "hdfs_it-jenkins-beam_postcommit_python_verify-4661_test_net" with the
> default driver
> could not find an available, non-overlapping IPv4 address pool among the
> defaults to assign to the network
>
> I assume that the issue is that the networks being created are not being
> cleaned up.
> Looking briefly online the solution seems to be something like "docker
> network prune --force".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (BEAM-4051) python postcommit failure in docker-compose
[
https://issues.apache.org/jira/browse/BEAM-4051?focusedWorklogId=90096=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-90096
]
ASF GitHub Bot logged work on BEAM-4051:
Author: ASF GitHub Bot
Created on: 11/Apr/18 18:12
Start Date: 11/Apr/18 18:12
Worklog Time Spent: 10m
Work Description: alanmyrvold commented on a change in pull request
#5100: [BEAM-4051] Clean up docker networks generated by hdfs integration tests.
URL: https://github.com/apache/beam/pull/5100#discussion_r180849168
##
File path:
sdks/python/apache_beam/io/hdfs_integration_test/hdfs_integration_test.sh
##
@@ -35,6 +35,8 @@ cp -r ${ROOT_DIR}/model ${CONTEXT_DIR}/
PROJECT_NAME=$(echo hdfs_IT-${BUILD_TAG:-non-jenkins})
cd ${CONTEXT_DIR}
+# TODO: prune?
+docker network ls
Review comment:
Maybe
docker network prune -f
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 90096)
Time Spent: 10m
Remaining Estimate: 0h
> python postcommit failure in docker-compose
> ---
>
> Key: BEAM-4051
> URL: https://issues.apache.org/jira/browse/BEAM-4051
> Project: Beam
> Issue Type: Bug
> Components: testing
>Reporter: Udi Meiri
>Assignee: Udi Meiri
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Python_Verify/4661/consoleText]
> Error is:
> Creating network
> "hdfs_it-jenkins-beam_postcommit_python_verify-4661_test_net" with the
> default driver
> could not find an available, non-overlapping IPv4 address pool among the
> defaults to assign to the network
>
> I assume that the issue is that the networks being created are not being
> cleaned up.
> Looking briefly online the solution seems to be something like "docker
> network prune --force".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
