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.p...@aiven.io&gt;;
????????:&nbsp;2022??9??2??(??????) ????7:29
??????:&nbsp;"Martijn Visser"<martijnvis...@apache.org&gt;;
????:&nbsp;"hjw"<1010445...@qq.com&gt;;"user"<user@flink.apache.org&gt;;
????:&nbsp;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]&nbsp;https://issues.apache.org/jira/browse/FLINK-29161&nbsp;


On Fri, Sep 2, 2022 at 10:51 AM Martijn Visser <martijnvis...@apache.org&gt; 
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 <1010445...@qq.com&gt;:

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.

Reply via email to