We ran into an issue where we used the world partition commandlet to duplicate a map and it mostly worked except that during multiprocess cook we every once in a while kept running into this issue just like someone else has ran into it in 5.5:
[Content removed]
The issue occurs because sometimes multicookprocess A cooks Map A and multicookprocess B cooks map B, but sometimes
they both end up in the same process and the warning occurs.
I was able to do some debugging and discover that there exists a code path that will *fix* this up by running the savepackage packages commandlet and doing both of the maps at the same time using -resaveondemand=bulkdataduplicates -AllowCommandletBulkDataRegistry *however* its pretty clear to me that this same process should happen to the landscape bulk data when the world partition commandlet runs to rename/resave the map.
Hopefully this helps anyone else but it would great to see this adjusted in a future release, so we dont have to run a 2nd script after the first one.
Can you clarify how you duplicated the level and in which version? I created a new level using the default WP template and duplicated from the editor& the commandlet. I’m not getting the warning when I cook. I made sure the GC doesn’t run between the 3 levels.
I found that this warning was downgraded to version of the Main stream. The team has determined that this is benign and will not cause more problems as the code can properly deal with this case. The output of the cook should be correct.
We duplicated it in 5.6 branch using the world partition commandlet but than we started seeing the warning in 5.7 *but* the map that was duplicated was *not* resaved in 5.6 since that was changed i posted in the fix above, so I assume to run into this, i assume you need to make a map into 5.4 or something, duplicate it using the commandlet and than run it like I posted and it would have this issue