-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 2.164.3
P4 plugin 1.10.3
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