+1 to periodic cleanups of the workers. I do not know what would be a good
frequency daily or a different one. Do we have a jira for this?
On Thu, Apr 30, 2020 at 2:22 PM Udi Meiri wrote:
> I summarized my idea here: https://issues.apache.org/jira/browse/BEAM-9865
>
+1 to this idea as well.
>
I summarized my idea here: https://issues.apache.org/jira/browse/BEAM-9865
On Thu, Apr 30, 2020 at 2:01 PM Maximilian Michels wrote:
> On 30.04.20 21:48, Hannah Jiang wrote:
> > --info tag was passed to docker image build commands with PythonDocker
> > Precommit to capture more logs. Without th
On 30.04.20 21:48, Hannah Jiang wrote:
> --info tag was passed to docker image build commands with PythonDocker
> Precommit to capture more logs. Without the tag, errors from
> DockerFile step are not printed out to the console.
Thanks for the info (pun intended).
On 30.04.20 21:48, Hannah Jiang
Is the issue that the workspace grows over time? Couldn't we delete it
daily to ensure it does not grow too much? Always deleting it on
successful runs may be too costly because we have to recreate the
workspace every time.
Logs are stored separately. I suppose they could also add up over time.
O
>
> Indeed, I can see the no space left on device in the following but not in
> the log above:
--info tag was passed to docker image build commands with PythonDocker
Precommit to capture more logs. Without the tag, errors from DockerFile
step are not printed out to the console.
On Thu, Apr 30, 20
I checked node 8 and it had over 40GB space available. Does your job
require more than that?
Long term, I'm thinking we could clean up workspaces for successful jobs.
This should free up additional space (I guess at least 100GB).
https://plugins.jenkins.io/ws-cleanup/ - we already use this plugin
*It's working again, probably because it's running on a different
machine now.
Who can check the disk space of the Jenkins hosts?
Thanks,
Max
On 30.04.20 11:55, Maximilian Michels wrote:
> Sorry, I meant to include the Jenkins log:
> https://builds.apache.org/job/beam_LoadTests_Python_ParDo_Flin
Sorry, I meant to include the Jenkins log:
https://builds.apache.org/job/beam_LoadTests_Python_ParDo_Flink_Streaming_PR/5/console
Thanks for investigating Hannah! Indeed, I can see the no space left on
device in the following but not in the log above:
https://builds.apache.org/job/beam_PreCommit_P
Max, I found a link from your PR and noticed below errors. This would be
the true error.
*07:57:03* >* Task :sdks:python:container:py37:docker**07:57:03*
[91mERROR: Could not install packages due to an EnvironmentError:
[Errno 28] No space left on device*07:57:03* *07:57:03* [0m*07:57:03*
>* Task
There is a PythonDocker Precommit test running for PRs with Python changes.
It seems running well.[1]
Max, can you please give me a link so I can check more details? Do other
images with different Python versions fail as well?
1. https://builds.apache.org/job/beam_PreCommit_PythonDocker_Commit/
+Valentyn Tymofieiev +Hannah Jiang
-- in case they have relevant information.
On Wed, Apr 29, 2020 at 12:35 PM Maximilian Michels wrote:
> Hi,
>
> has anyone noticed the Python 3.7 Docker container fails to build? I
> haven't been able to build the Python 3.7 container, neither locally nor
> o
11 matches
Mail list logo
