I have kicked off a build using the pin job at label functionality, not sure if that is related or not. The job appears to kick off just fine as I see this output:

10:47:59 [EnvInject] - Loading node environment variables.
10:47:59 Building remotely on rsmsnbuild114 in workspace c:\trees
10:48:56 SCM Task: cleanup workspace: RSMSNBUILD114
10:48:57 SCM Task: syncing files at label: my_label
10:48:57 ... sync c:\trees/...@my_label
10:48:57 ... force update false
10:48:57 ... bypass have false

It appears the sync works, but I see the machine that runs the Jenkins server under heavy CPU load and the monitor running a 'p4 files'.

Is this expected?