[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Paul Allen closed an issue as Fixed Jenkins / JENKINS-57870 Request too large for server memory since 10.1.0 Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.9615.1570015380346%40Atlassian.JIRA.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Paul Allen commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 Released in 1.10.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.18979.1563892020293%40Atlassian.JIRA.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth resolved as Fixed Test patch released. Jenkins / JENKINS-57870 Request too large for server memory since 10.1.0 Change By: Karl Wirth Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.14585.1563380460566%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 Have released a test patch version to fix the "Request too large for memory" problem. Instead of running 'p4 changes -m1' it now runs for the last N changes: p4 changes m1 -ssubmitted //jenkins-masterJENKINS-57870-changes-m1-0/...@27+23784,273+3784 N is a configurable variable that can be set under: Jenkins > Manage Jenkins > Configure System > Head change query limit The test patch can be downloaded from: https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.14583.1563380460544%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-57870 Request too large for server memory since 10.1.0 Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.13186.1561993200437%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57870 Request too large for server memory since 10.1.0 Change By: Karl Wirth Labels: P4_SUPPORT P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.13182.1561993200370%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Paul Allen commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 For reference: The code to query the change was added to deal with issue JENKINS-57534 https://github.com/jenkinsci/p4-plugin/commit/c1ed873be0d988d12619b1072bb41a0580aa3bd2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.11717.1561734420178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 Mateusz Delikat - I have been working with this with Paul and it looks like Jenkins is going through an unexpected path to trigger the command (we provide hooks and jenkins chooses which one's to call). We are still looking into this but it may be that we don't have enough contextually information when Jenkins calls the second instance to decide if the command needs to be run or not. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.11576.1561718580156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title
Mateusz Delikat edited a comment on JENKINS-57870
Re: Request too large for server memory since 10.1.0
[~p4karl]{color:#172b4d}, {color}[~p4paul]{color:#172b4d}: Why are we actually seeing {color}{code:java}02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...02:02:59 02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg'{code} {color:#009100}and then{color}{ color:#172b4d} {color}{ code:java}02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516*{code}{color:#172b4d} when we already know the change number from the first call? On our end we don't have "Request too large" errors but the first command on our stream takes about 1 second to complete and the second often takes more than 10 minutes. Does the plugin really needs to re-verify that changelist? Won't it be always the same?{color}{color:#172b4d} {color:#009100} {color} {color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.11569.1561718040532%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title
Mateusz Delikat edited a comment on JENKINS-57870
Re: Request too large for server memory since 10.1.0
[~p4karl] {color:#172b4d} , {color} [~p4paul] {color : #172b4d}: Why are we actually seeing {color} {code:java} 02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...02:02:59 02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg' {code} {color:#009100} and then {color }{color :#172b4d} and then {color}{ color code:java }02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516* {code} {color:#172b4d} when we already know the change number from the first call?On our end we don't have "Request too large" errors but the first command on our stream takes about 1 second to complete and the second often takes more than 10 minutes. Does the plugin really needs to re-verify that changelist? Won't it be always the same?{color}{color:# 172b4d}{color:# 009100} {color} {color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.11565.1561717980580%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Mateusz Delikat commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 Karl Wirth, Paul Allen: Why are we actually seeing 02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...02:02:59 02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg' and then 02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516* when we already know the change number from the first call? On our end we don't have "Request too large" errors but the first command on our stream takes about 1 second to complete and the second often takes more than 10 minutes. Does the plugin really needs to re-verify that changelist? Won't it be always the same? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.11561.1561717980419%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57870 Request too large for server memory since 10.1.0 Change By: Karl Wirth Summary: populate: previewOnly(quiet: true) fail Request too large for server memory since 10.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.4715.1561046341163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
