This error was present the last 3 times we upgraded to a newer version of Tuleap.
ForgeUpgrade fails and it does not show any error, so I have to execute already-applied script: /usr/lib/forgeupgrade/bin/forgeupgrade --config=/etc/codendi/forgeupgrade/config.ini already-applied and it shows an output that contains those scripts that were not successfully applied due an error. ex. 2016-03-19 14:41:52 Error 239 /usr/share/tuleap/plugins/tracker/db/mysql/updates/2016/201602081457_add_is_child_into_existing_data.php

Solution: I have to open the php file (those with error), run the sql script manually and update forge_upgrade_bucket table and rerun ForgeUpgrade script again.

We would like to know why we are getting those errors and how to avoid that behaviour in future upgrades. We have a short time window to upgrade our server and this error increases considerably upgrade time.

I attached a file with the output we get after running forgeupgrade --config=/etc/codendi/forgeupgrade/config.ini already-applied script.