You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flink.apache.org by hjw <10...@qq.com> on 2022/09/02 06:39:33 UTC
flink ci build run longer than the maximum time of 310 minutes.
I commit a pr to Flink Github .
A error happened in building ci.
[error]The job running on agent Azure Pipelines 6 ran longer than the maximum time of 310 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
How to solve this problem?
How to triigle the ci building again?
thx.
回复： flink ci build run longer than the maximum time of 310 minutes.
Posted by hjw <10...@qq.com>.
Hi,Matthias
I have solved this problem as you say.The link to the PR [1] .thank you.
[1]https://github.com/apache/flink/pull/20671
Best,
Hjw
------------------ 原始邮件 ------------------
发件人: "Matthias Pohl" <user@flink.apache.org>;
发送时间: 2022年9月5日(星期一) 下午4:47
收件人: "hjw"<1010445050@qq.com>;
抄送: "Martijn Visser"<martijnvisser@apache.org>;"user"<user@flink.apache.org>;
主题: Re: flink ci build run longer than the maximum time of 310 minutes.
Usually, it would be more helpful to provide a link to the PR to get a better picture of the problem. I'm not 100% sure whether I grasp what's wrong.
It looks like your branch is based on apache/flink:release-1.15 [1]. Therefore, you should fetch the most recent version from upstream and then do a git rebase upstream/release-1.15. This will put your 4 commits which you've added to your local branch so far "on top" of everything that is already part of upstream/release-1.15. This should resolve your branch being 11 commits behind the 1.15 release branch. Force-pushing the changes in your local branch to your remote repo (your fork) will update the PR.
Keep in mind that you have to specify the right base branch in your Github PR (pointing to the 1.15 release branch in your case) as well to have the right diff.
I hope that helps. Best,
Matthias
[1] https://github.com/apache/flink/tree/release-1.15
On Sat, Sep 3, 2022 at 10:18 AM hjw <1010445050@qq.com> wrote:
Hi,Matthias
The ci build Error in e2e_1_ci job:
Sep 0211:01:51 ##[group]Top 15 biggest directories in terms of used disk space
Sep 02 11:01:52 Searching for .dump, .dumpstream and related files in '/home/vsts/work/1/s'
dmesg: read kernel buffer failed: Operation not permitted
Sep 02 11:01:53 No taskexecutor daemon to stop on host fv-az158-417.
Sep 02 11:01:53 No standalonesession daemon to stop on host fv-az158-417.
Sep 02 11:10:27 The command 'docker build --no-cache --network=host -t test_docker_embedded_job dev/test_docker_embedded_job-debian' (pid: 188432) did not finish after 600 seconds.
/home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/common.sh: line 900: kill: (188432) - No such process
Sep 02 11:11:06 The command 'docker build --no-cache --network=host -t test_docker_embedded_job dev/test_docker_embedded_job-debian' (pid: 188484) did not finish after 600 seconds.
/home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/common.sh: line 900: kill: (188484) - No such process
I think the issue applies to my case.
However, I have submited some commit to my fork repo and create a pr.The pr has not been merged in to flink repo. My fork repo status :This branch is 4 commits ahead, 11 commits behind apache:release-1.15.
When I rebase the branch from upstream and push to my fork repo, the 11 commits behind apache:release-1.15 also appear in my pr change files. How can I handle this situation? thx.
Best,
Hjw
------------------ 原始邮件 ------------------
发件人: "Matthias Pohl" <matthias.pohl@aiven.io>;
发送时间: 2022年9月2日(星期五) 晚上7:29
收件人: "Martijn Visser"<martijnvisser@apache.org>;
抄送: "hjw"<1010445050@qq.com>;"user"<user@flink.apache.org>;
主题: Re: flink ci build run longer than the maximum time of 310 minutes.
Not sure whether that applies to your case, but there was a recent issue [1] where the e2e_1_ci job ran into a timeout. If that's what you were observing, rebasing your branch might help.
Best,
Matthias
[1] https://issues.apache.org/jira/browse/FLINK-29161
On Fri, Sep 2, 2022 at 10:51 AM Martijn Visser <martijnvisser@apache.org> wrote:
You can ask the Flinkbot to run again by typing as comment
@flinkbot run azure
Best regards,
Martijn
Op vr 2 sep. 2022 om 08:40 schreef hjw <1010445050@qq.com>:
I commit a pr to Flink Github .
A error happened in building ci.
[error]The job running on agent Azure Pipelines 6 ran longer than the maximum time of 310 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
How to solve this problem?
How to triigle the ci building again?
thx.
Re: flink ci build run longer than the maximum time of 310 minutes.
Posted by Matthias Pohl via user <us...@flink.apache.org>.
Usually, it would be more helpful to provide a link to the PR to get a
better picture of the problem. I'm not 100% sure whether I grasp what's
wrong.
It looks like your branch is based on apache/flink:release-1.15 [1].
Therefore, you should fetch the most recent version from upstream and then
do a git rebase upstream/release-1.15. This will put your 4 commits which
you've added to your local branch so far "on top" of everything that is
already part of upstream/release-1.15. This should resolve your branch
being 11 commits behind the 1.15 release branch. Force-pushing the changes
in your local branch to your remote repo (your fork) will update the PR.
Keep in mind that you have to specify the right base branch in your Github
PR (pointing to the 1.15 release branch in your case) as well to have the
right diff.
I hope that helps. Best,
Matthias
[1] https://github.com/apache/flink/tree/release-1.15
On Sat, Sep 3, 2022 at 10:18 AM hjw <10...@qq.com> wrote:
> Hi,Matthias
> The ci build Error in e2e_1_ci job:
> Sep 0211:01:51 ##[group]Top 15 biggest directories in terms of used disk
> space
> Sep 02 11:01:52 Searching for .dump, .dumpstream and related files in
> '/home/vsts/work/1/s'
> dmesg: read kernel buffer failed: Operation not permitted
> Sep 02 11:01:53 No taskexecutor daemon to stop on host fv-az158-417.
> Sep 02 11:01:53 No standalonesession daemon to stop on host fv-az158-417.
> Sep 02 11:10:27 The command 'docker build --no-cache --network=host -t
> test_docker_embedded_job dev/test_docker_embedded_job-debian' (pid: 188432)
> did not finish after 600 seconds.
> /home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/common.sh: line
> 900: kill: (188432) - No such process
> Sep 02 11:11:06 The command 'docker build --no-cache --network=host -t
> test_docker_embedded_job dev/test_docker_embedded_job-debian' (pid: 188484)
> did not finish after 600 seconds.
> /home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/common.sh: line
> 900: kill: (188484) - No such process
>
> I think the issue applies to my case.
> However, I have submited some commit to my fork repo and create a pr.The
> pr has not been merged in to flink repo. My fork repo status :This
> branch is 4 commits ahead
> <https://github.com/SwimSweet/flink/compare/apache:flink:release-1.15...release-1.15>
> , 11 commits behind
> <https://github.com/SwimSweet/flink/compare/release-1.15...apache:flink:release-1.15>
> apache:release-1.15.
>
> When I rebase the branch from upstream and push to my fork repo, the 11
> commits
> <https://github.com/SwimSweet/flink/compare/release-1.15...apache:flink:release-1.15>
> behind
> <https://github.com/SwimSweet/flink/compare/release-1.15...apache:flink:release-1.15> apache:release-1.15
> also appear in my pr change files. How can I handle this situation? thx.
>
> ------------------------------
> Best,
> Hjw
>
>
>
> ------------------ 原始邮件 ------------------
> *发件人:* "Matthias Pohl" <ma...@aiven.io>;
> *发送时间:* 2022年9月2日(星期五) 晚上7:29
> *收件人:* "Martijn Visser"<ma...@apache.org>;
> *抄送:* "hjw"<10...@flink.apache.org>;
> *主题:* Re: flink ci build run longer than the maximum time of 310 minutes.
>
> Not sure whether that applies to your case, but there was a recent issue
> [1] where the e2e_1_ci job ran into a timeout. If that's what you were
> observing, rebasing your branch might help.
>
> Best,
> Matthias
>
> [1] https://issues.apache.org/jira/browse/FLINK-29161
>
> On Fri, Sep 2, 2022 at 10:51 AM Martijn Visser <ma...@apache.org>
> wrote:
>
>> You can ask the Flinkbot to run again by typing as comment
>>
>> @flinkbot run azure
>>
>> Best regards,
>>
>> Martijn
>>
>> Op vr 2 sep. 2022 om 08:40 schreef hjw <10...@qq.com>:
>>
>>> I commit a pr to Flink Github .
>>> A error happened in building ci.
>>> [error]The job running on agent Azure Pipelines 6 ran longer than the
>>> maximum time of 310 minutes. For more information, see
>>> https://go.microsoft.com/fwlink/?linkid=2077134
>>>
>>> How to solve this problem?
>>> How to triigle the ci building again?
>>> thx.
>>>
>>
回复： flink ci build run longer than the maximum time of 310 minutes.
Posted by hjw <10...@qq.com>.
Hi,Matthias
The ci build Error in e2e_1_ci job:
Sep 0211:01:51 ##[group]Top 15 biggest directories in terms of used disk space
Sep 02 11:01:52 Searching for .dump, .dumpstream and related files in '/home/vsts/work/1/s'
dmesg: read kernel buffer failed: Operation not permitted
Sep 02 11:01:53 No taskexecutor daemon to stop on host fv-az158-417.
Sep 02 11:01:53 No standalonesession daemon to stop on host fv-az158-417.
Sep 02 11:10:27 The command 'docker build --no-cache --network=host -t test_docker_embedded_job dev/test_docker_embedded_job-debian' (pid: 188432) did not finish after 600 seconds.
/home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/common.sh: line 900: kill: (188432) - No such process
Sep 02 11:11:06 The command 'docker build --no-cache --network=host -t test_docker_embedded_job dev/test_docker_embedded_job-debian' (pid: 188484) did not finish after 600 seconds.
/home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/common.sh: line 900: kill: (188484) - No such process
I think the issue applies to my case.
However, I have submited some commit to my fork repo and create a pr.The pr has not been merged in to flink repo. My fork repo status :This branch is 4 commits ahead, 11 commits behind apache:release-1.15.
When I rebase the branch from upstream and push to my fork repo, the 11 commits behind apache:release-1.15 also appear in my pr change files. How can I handle this situation? thx.
Best,
Hjw
------------------ 原始邮件 ------------------
发件人: "Matthias Pohl" <matthias.pohl@aiven.io>;
发送时间: 2022年9月2日(星期五) 晚上7:29
收件人: "Martijn Visser"<martijnvisser@apache.org>;
抄送: "hjw"<1010445050@qq.com>;"user"<user@flink.apache.org>;
主题: Re: flink ci build run longer than the maximum time of 310 minutes.
Not sure whether that applies to your case, but there was a recent issue [1] where the e2e_1_ci job ran into a timeout. If that's what you were observing, rebasing your branch might help.
Best,
Matthias
[1] https://issues.apache.org/jira/browse/FLINK-29161
On Fri, Sep 2, 2022 at 10:51 AM Martijn Visser <martijnvisser@apache.org> wrote:
You can ask the Flinkbot to run again by typing as comment
@flinkbot run azure
Best regards,
Martijn
Op vr 2 sep. 2022 om 08:40 schreef hjw <1010445050@qq.com>:
I commit a pr to Flink Github .
A error happened in building ci.
[error]The job running on agent Azure Pipelines 6 ran longer than the maximum time of 310 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
How to solve this problem?
How to triigle the ci building again?
thx.
Re: flink ci build run longer than the maximum time of 310 minutes.
Posted by Matthias Pohl via user <us...@flink.apache.org>.
Not sure whether that applies to your case, but there was a recent issue
[1] where the e2e_1_ci job ran into a timeout. If that's what you were
observing, rebasing your branch might help.
Best,
Matthias
[1] https://issues.apache.org/jira/browse/FLINK-29161
On Fri, Sep 2, 2022 at 10:51 AM Martijn Visser <ma...@apache.org>
wrote:
> You can ask the Flinkbot to run again by typing as comment
>
> @flinkbot run azure
>
> Best regards,
>
> Martijn
>
> Op vr 2 sep. 2022 om 08:40 schreef hjw <10...@qq.com>:
>
>> I commit a pr to Flink Github .
>> A error happened in building ci.
>> [error]The job running on agent Azure Pipelines 6 ran longer than the
>> maximum time of 310 minutes. For more information, see
>> https://go.microsoft.com/fwlink/?linkid=2077134
>>
>> How to solve this problem?
>> How to triigle the ci building again?
>> thx.
>>
>
Re: flink ci build run longer than the maximum time of 310 minutes.
Posted by Martijn Visser <ma...@apache.org>.
You can ask the Flinkbot to run again by typing as comment
@flinkbot run azure
Best regards,
Martijn
Op vr 2 sep. 2022 om 08:40 schreef hjw <10...@qq.com>:
> I commit a pr to Flink Github .
> A error happened in building ci.
> [error]The job running on agent Azure Pipelines 6 ran longer than the
> maximum time of 310 minutes. For more information, see
> https://go.microsoft.com/fwlink/?linkid=2077134
>
> How to solve this problem?
> How to triigle the ci building again?
> thx.
>