Skip to content

Conversation

@dashielb1010
Copy link

The backburner_job_completion setting should default to something
other than "delete". It is possible for the "Create Preview" job to
complete and delete itself before the "Upload Preview" job gets created
by tk-flame. Backburner will fail because the job dependency no longer
exists. Eliminate this race condition.

The `backburner_job_completion` setting should default to something
other than "delete". It is possible for the "Create Preview" job to
complete and delete itself before the "Upload Preview" job gets created
by tk-flame. Backburner will fail because the job dependency no longer
exists. Eliminate this race condition.
@alatteri
Copy link

alatteri commented Jun 3, 2019

I don't want that junk hanging out for a day. That was the original problem. All the ancillary Shotgun jobs create a huge amount of noise in the queue on large publish jobs.

@jpbrault
Copy link
Contributor

jpbrault commented Jun 3, 2019

Which version of the backburner manager are you running?
There is a fix for this issue on the backburner manager side that should resolve that issue.

@dashielb1010
Copy link
Author

I don't want that junk hanging out for a day. That was the original problem. All the ancillary Shotgun jobs create a huge amount of noise in the queue on large publish jobs.

I agree! It'd be nice if the 'delete after' setting was minutes or seconds.

@dashielb1010
Copy link
Author

Which version of the backburner manager are you running?
There is a fix for this issue on the backburner manager side that should resolve that issue.

Autodesk Backburner Manager v2019.1 (build 2)

@dashielb1010
Copy link
Author

Here are debug logs that I used to track down the issue.
backburner.log
backburnerServer.log
tk-flame.log

@dashielb1010
Copy link
Author

Which version of the backburner manager are you running?
There is a fix for this issue on the backburner manager side that should resolve that issue.

Autodesk Backburner Manager v2019.1 (build 2)

So this is fixed in Flame 2020 then?

@jpbrault
Copy link
Contributor

It was not part of 2020 release.
The fix will be in the next 2020 Service Pack for BackBurner (2020.0.1)
You can contact support to get it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants