Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Environment:
      Docker Jenkins as master, Windows Server 2016 + Java 1.8.0 144 b0 and Gentoo as slaves
    • Similar Issues:

      Description

      Client is created and sync of client appears in log but the files are not there. I need to log into node and issue p4 sync manually.

        Attachments

          Activity

          mpiechotka Maciej Piechotka created issue -
          Hide
          wbrode William Brode added a comment -

          I saw this same issue - everything looks normal but no files are synced.  In our case it was a problem with our p4 edge server and parallel syncing in p4java (IIRC).  This was affecting us even though I had parallel syncing disabled.  The workaround was to set the parallel sync options to the following:

          parallel: [enable: true, minbytes: '0', minfiles: '0', threads: '0']

          Thought I would comment just in case you have the same cause.

          Show
          wbrode William Brode added a comment - I saw this same issue - everything looks normal but no files are synced.  In our case it was a problem with our p4 edge server and parallel syncing in p4java (IIRC).  This was affecting us even though I had parallel syncing disabled.  The workaround was to set the parallel sync options to the following: parallel: [enable: true, minbytes: '0', minfiles: '0', threads: '0'] Thought I would comment just in case you have the same cause.
          Hide
          mpiechotka Maciej Piechotka added a comment -

          Yes. I forgot to update that I find out that parallel sync is the problematic setting.

          Show
          mpiechotka Maciej Piechotka added a comment - Yes. I forgot to update that I find out that parallel sync is the problematic setting.
          p4karl Karl Wirth made changes -
          Field Original Value New Value
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Not A Defect [ 7 ]
          p4karl Karl Wirth made changes -
          Labels checkout P4_SUPPORT checkout
          Hide
          mpiechotka Maciej Piechotka added a comment - - edited
          • I started reproducing it with non-parallel sync
          • How is this 'Not a defect'? I'm assuming it was closed by accident as no comment was made and reopen
          Show
          mpiechotka Maciej Piechotka added a comment - - edited I started reproducing it with non-parallel sync How is this 'Not a defect'? I'm assuming it was closed by accident as no comment was made and reopen
          mpiechotka Maciej Piechotka made changes -
          Resolution Not A Defect [ 7 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          Hide
          robilott Rob Ilott added a comment -

          We have recently been hit quite badly by this issue. Using William's work around seems to have fixed it for us. Any chance this is going to be looked at soon?

          Show
          robilott Rob Ilott added a comment - We have recently been hit quite badly by this issue. Using William's work around seems to have fixed it for us. Any chance this is going to be looked at soon?
          Hide
          tsackett Tom Sackett added a comment -

          I'm running into this problem with parallel sync. The log output shows the files being added, but the workspace on the build machine is empty. The sync succeeds if I disable parallel syncing. However, we really need parallel sync to work.

          Show
          tsackett Tom Sackett added a comment - I'm running into this problem with parallel sync. The log output shows the files being added, but the workspace on the build machine is empty. The sync succeeds if I disable parallel syncing. However, we really need parallel sync to work.
          Hide
          wbrode William Brode added a comment -

          Tom Sackett - I think we found that the issue was partially related to proxy or edge servers and how they were set up with regards to parallel syncing.  So you could look at your p4 server configuration to get it to work properly.  Perhaps you could reply here if you figure out the steps that work for you.

          Show
          wbrode William Brode added a comment - Tom Sackett - I think we found that the issue was partially related to proxy or edge servers and how they were set up with regards to parallel syncing.  So you could look at your p4 server configuration to get it to work properly.  Perhaps you could reply here if you figure out the steps that work for you.
          Hide
          douglasawh Doug Whitfield added a comment -

          What versions of P4Jenkins is everybody here running? Some versions of P4Java do not support parallel sync, so that's possibly an issue for some of you.

          Show
          douglasawh Doug Whitfield added a comment - What versions of P4Jenkins is everybody here running? Some versions of P4Java do not support parallel sync, so that's possibly an issue for some of you.
          Hide
          philmcardlecg Phil McArdle added a comment -

          I was reproducing the parallel sync issue on p4-plugin 1.8.12

          Show
          philmcardlecg Phil McArdle added a comment - I was reproducing the parallel sync issue on p4-plugin 1.8.12
          p4karl Karl Wirth made changes -
          Assignee Doug Whitfield [ douglasawh ]
          Hide
          arkady_english Arkady English added a comment -

          I've found this with p4-plugin 1.8.15. and Jenkins version 2.143.

          It happens with parallel sync on with default settings, on with William Brode's suggested settings, and off.

          Show
          arkady_english Arkady English added a comment - I've found this with p4-plugin 1.8.15. and Jenkins version 2.143. It happens with parallel sync on with default settings, on with William Brode's suggested settings, and off.
          Hide
          douglasawh Doug Whitfield added a comment -

          Arkady English do you have a ticket open with support@perforce.com? If not, please open one. I'd like to get a screenshot of your build triggers.

           

          We have not been able to replicate this in house.

          Show
          douglasawh Doug Whitfield added a comment - Arkady English do you have a ticket open with support@perforce.com ? If not, please open one. I'd like to get a screenshot of your build triggers.   We have not been able to replicate this in house.
          Hide
          arkady_english Arkady English added a comment -

          Doug Whitfield I've opened ticket #00342618.

          Show
          arkady_english Arkady English added a comment - Doug Whitfield I've opened ticket #00342618.
          Hide
          matthew_dews Matthew Dews added a comment -

          Also ran into this issue recently. William's workaround works for us at the moment. According to our admin the Perforce server has parallel sync on unless a client requests otherwise.

          Windows 10 x86 (virtualized)
          Jenkins Service runs as a local user
          Job that that had failing p4 sync was run locally
          1 macOS slave which we have observed no sync issues on
          P4 Plugin 1.9.3
          Jenkins 2.138.2
          java.runtime.version 1.8.0_144-b01

          Show
          matthew_dews Matthew Dews added a comment - Also ran into this issue recently. William's workaround works for us at the moment. According to our admin the Perforce server has parallel sync on unless a client requests otherwise. Windows 10 x86 (virtualized) Jenkins Service runs as a local user Job that that had failing p4 sync was run locally 1 macOS slave which we have observed no sync issues on P4 Plugin 1.9.3 Jenkins 2.138.2 java.runtime.version 1.8.0_144-b01
          Hide
          newtopian Eric Daigneault added a comment -

          Still an issue, 

          Jenkins 2.176.2

          p4 plugin: 1.10.3

          perforce server: Server version: P4D/LINUX26X86_64/2018.1/1673397 (2018/06/21)

          simply changed the job to put false in the parallel sync and it worked

          Show
          newtopian Eric Daigneault added a comment - Still an issue,  Jenkins 2.176.2 p4 plugin: 1.10.3 perforce server: Server version: P4D/LINUX26X86_64/2018.1/1673397 (2018/06/21) simply changed the job to put false in the parallel sync and it worked
          Hide
          wbrode William Brode added a comment -

          Doug Whitfield or Arkady English - what was the resolution of your issue?  We are seeing similar behavior so it could help us.

          Show
          wbrode William Brode added a comment - Doug Whitfield or Arkady English - what was the resolution of your issue?  We are seeing similar behavior so it could help us.
          Hide
          douglasawh Doug Whitfield added a comment -

          William Brode we did not get the logs in that particular case.

           

          Show
          douglasawh Doug Whitfield added a comment - William Brode we did not get the logs in that particular case.  
          Hide
          kroutley Kurt Routley added a comment -

          One of our teammates is seeing this again, although their automation stack is on an older version of the p4 plugin and p4d, but based on the p4java release notes it should have sufficient parallel sync support. They hit the issue where sync would run and report success in automation, however the files were not actually sync'd, and it wasn't resolved until they explicitly set the sync configuration to have parallel sync enabled, but with threads, minimum files, and minimum bytes all set to 0.

          Environment information:

          Running Jenkins 2.164.2 with P4 Plugin 1.7.4 (uses p4java 2017.2.1535715) and SCM API Plugin 2.6.3.
          Client VMs (Jenkins agents) are syncing from a P4D Commit server on 2017.2.1650199.
          P4V is not installed on the client VMs
          Client VMs are an assortment of Windows Server 2016 (8-core, 32GB RAM) and Mac Mojave (4-core, 16GB RAM) VMs

          Let me know if you need any more information

          Show
          kroutley Kurt Routley added a comment - One of our teammates is seeing this again, although their automation stack is on an older version of the p4 plugin and p4d, but based on the p4java release notes it should have sufficient parallel sync support. They hit the issue where sync would run and report success in automation, however the files were not actually sync'd, and it wasn't resolved until they explicitly set the sync configuration to have parallel sync enabled, but with threads, minimum files, and minimum bytes all set to 0. Environment information: Running Jenkins 2.164.2 with P4 Plugin 1.7.4 (uses p4java 2017.2.1535715) and SCM API Plugin 2.6.3. Client VMs (Jenkins agents) are syncing from a P4D Commit server on 2017.2.1650199. P4V is not installed on the client VMs Client VMs are an assortment of Windows Server 2016 (8-core, 32GB RAM) and Mac Mojave (4-core, 16GB RAM) VMs Let me know if you need any more information

            People

            • Assignee:
              douglasawh Doug Whitfield
              Reporter:
              mpiechotka Maciej Piechotka
            • Votes:
              13 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

              • Created:
                Updated: