-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin occasionally fails to sync backwards #191
Comments
On a more interesting note: I made two builds with the exact same parameters as above, and only one of them in failing with this issue: see: https://buildkite.com/improbable/midwinter-build/builds/2698 vs https://buildkite.com/improbable/midwinter-build/builds/2697 |
improbable-mattchurch
changed the title
Plugin fails to sync backwards
Plugin occasionally fails to sync backwards
Oct 8, 2020
PEBCAK, cascade.umap was being modified in a shelf and wasn't being marked for edit so future jobs were spoiled |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Agent bless used: https://buildkite.com/improbable/midwinter-bless/builds/92, note CL 68063
Specified CL 68005 for build, with a patch of 68241
Note errors:
Asset 'Cascade.umap' has been saved with engine version newer than current and therefore can't be loaded. CurrEngineVersion: 4.24.3-67998+++midwinter+main AssetEngineVersion: 4.24.3-68054+++midwinter+main
(CL 67998 was editor version compatible with CL 68005)
This would only be present if Cascade.umap wasn't synched to CL 68005. It turns out that the agent running the step was previously synced to CL 68054 from the last build it ran.
https://buildkite.com/improbable/midwinter-build/builds/2697#3a9cc5c2-d324-42b3-8d17-21d32316d055/6-7
Plugin version: perforce-buildkite-plugin#v4.3.2
The text was updated successfully, but these errors were encountered: