[JIRA] (JENKINS-58686) Syncing to revision 0 runs an invalid command

21 views
Skip to first unread message

williambrode@gmail.com (JIRA)

unread,
Jul 26, 2019, 4:55:02 PM7/26/19
to jenkinsc...@googlegroups.com
William Brode created an issue
 
Jenkins / Bug JENKINS-58686
Syncing to revision 0 runs an invalid command
Issue Type: Bug Bug
Assignee: Unassigned
Components: p4-plugin
Created: 2019-07-26 20:54
Environment: Jenkins 2.164.3
P4 plugin 1.10.3
Priority: Major Major
Reporter: William Brode

Found this in our logs for a pipeline that syncs its p4 workspace to CL 0:
p4 changes -m1 -ssubmitted //WORKSPACE_NAME/...@1,0
P4: no revisions under //WORKSPACE_NAME/...@1,0 using change: 0

This seems to be okay and not cause problems most of the time.  But occasionally we get:
p4 changes -m1 -ssubmitted //WORKSPACE_NAME/...@1,0
Too many rows scanned (over 300000000); see 'p4 help maxscanrows'.
Which does cause the sync to fail.  It looks to me like this is related to these recent changes: https://swarm.workshop.perforce.com/changes/25826
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

williambrode@gmail.com (JIRA)

unread,
Jul 26, 2019, 4:56:02 PM7/26/19
to jenkinsc...@googlegroups.com
William Brode updated an issue
Change By: William Brode
Found this in our logs for a pipeline that syncs its p4 workspace to CL 0:

{{ p4 changes -m1 -ssubmitted //WORKSPACE_NAME/...@1,0 }}
{{ P4: no revisions under //WORKSPACE_NAME/...@1,0 using change: 0 }}

 

 This seems to be okay and not cause problems most of the time.  But occasionally we get:

{{ p4 changes -m1 -ssubmitted //WORKSPACE_NAME/...@1,0 }}
{{ Too many rows scanned (over 300000000); see 'p4 help maxscanrows'. }}


Which does cause the sync to fail.  It looks to me like this is related to these recent changes: [https://swarm.workshop.perforce.com/changes/25826]
Add Comment Add Comment
 

williambrode@gmail.com (JIRA)

unread,
Jul 26, 2019, 4:57:02 PM7/26/19
to jenkinsc...@googlegroups.com
William Brode updated an issue
Found this in our logs for a pipeline that syncs its p4 workspace to CL 0:

  

{ { code:java}
p4 changes -m1 -ssubmitted //WORKSPACE_NAME/...@1,0 }}
{{ P4: no revisions under //WORKSPACE_NAME/...@1,0 using change: 0

{code } }

 

 This seems to be okay and not cause problems most of the time.  But occasionally we get:

{ { code:java}
p4 changes -m1 -ssubmitted //WORKSPACE_NAME/...@1,0 }}
{{ Too many rows scanned (over 300000000); see 'p4 help maxscanrows'. {code } }


Which does cause the sync to fail.  It looks to me like this is related to these recent changes: [https://swarm.workshop.perforce.com/changes/25826]

williambrode@gmail.com (JIRA)

unread,
Jul 29, 2019, 1:27:02 PM7/29/19
to jenkinsc...@googlegroups.com
William Brode assigned an issue to William Brode
Change By: William Brode
Assignee: William Brode

williambrode@gmail.com (JIRA)

unread,
Jul 29, 2019, 7:23:01 PM7/29/19
to jenkinsc...@googlegroups.com
William Brode started work on Bug JENKINS-58686
 
Change By: William Brode
Status: Open In Progress

williambrode@gmail.com (JIRA)

unread,
Jul 29, 2019, 7:24:02 PM7/29/19
to jenkinsc...@googlegroups.com

kwirth@perforce.com (JIRA)

unread,
Aug 12, 2019, 3:41:02 AM8/12/19
to jenkinsc...@googlegroups.com

Hi William Brode, Thanks for reporting this and providing a fix. As background, how is the job configured to sync to '0'?

Is this an explicit sync such as pin to changelist '0' or Groovy code that syncs to '0'? If it is then can you please explain how it's setup.

Or is this just a side effect of normal operation? If it is then can you please send me a bigger section of console log.

Thanks in advance,

Karl

williambrode@gmail.com (JIRA)

unread,
Aug 13, 2019, 7:20:02 PM8/13/19
to jenkinsc...@googlegroups.com

williambrode@gmail.com (JIRA)

unread,
Aug 13, 2019, 7:20:03 PM8/13/19
to jenkinsc...@googlegroups.com
Change By: William Brode
Status: In Progress Fixed but Unreleased
Resolution: Fixed

williambrode@gmail.com (JIRA)

unread,
Aug 13, 2019, 7:24:02 PM8/13/19
to jenkinsc...@googlegroups.com
 
Re: Syncing to revision 0 runs an invalid command

Karl Wirth - the pipeline is configured to take a Changelist as an input parameter.  The Changelist parameter is defaulted to 0 and we don't really change it.  That parameter is used with a syncOnly populate option for the pin setting: 

pin: '${Changelist}'

 

So we are essentially just pinning it to 0.  This is done to ensure no files are synced.

kwirth@perforce.com (JIRA)

unread,
Aug 14, 2019, 9:56:03 AM8/14/19
to jenkinsc...@googlegroups.com

Hi William Brode - Thanks.  Paul has already pulled in the code but I wanted to pass on the background to our QA team.

 

 

pallen@perforce.com (JIRA)

unread,
Oct 2, 2019, 10:54:04 AM10/2/19
to jenkinsc...@googlegroups.com
Paul Allen updated Bug JENKINS-58686
 

Released in 1.10.4
Change By: Paul Allen
Status: Fixed but Unreleased Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages