![]() Read : clients/service.engweb_bccm-jenkinsĪll the stuck jobs are in one of those clients:ġ233 T buildmaste 24:59:48 sync -f T buildmaste 71:58:02 sync R buildmaste 01:59:12 sync T drew.marol 48:54:17 client -d aem_gemĦ058 R buildmaste 24:19:19 sync -f T service.en 71:17:37 sync R buildmaste 01:51:15 sync -f T drew.marol 50:07:47 change -iĢ9045 T drew.marol 71:40:59 sync c:\p4\aem_gem\.#head Ok, so it looks like the clients database is the problem here: Please click here to see the post in its original format: ![]() There were 4 identical entries each for 23:01:14 & 23:01:15. Looking at the proxy's log I see a bunch of these: Least a couple are caused by starting a sync, then killing it with ^C. It seems like our office is particularly prone to this problem, one of theĭevelopers here has at least half a dozen processes that are running forever. Like we're using a broker as well based on p4 info: Posted on behalf of forum user 'UnstoppableDrew'.įor additional data points, I'm going through a local proxy, and it looks
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |