It's causing problems when wiping the database. The fix is comming in cp-0.5.16-1. Enabling this test again after new CP release.
Only marketing products must deal with deleting product - content assignment in CP. For engineering products there are repositories created, which delete the content when they are removed. This change prevents trying to delete the content twice while deleting product. The other posibility would be to prevent deleting of conent in repository in case product is being deleted and let product handle it all, but there would be necessary a mechanism for finding out if the repo orchestration happens during product orchestration or not - when not repo should handle content deletion itself.
When running the dealyed jobs with commend: ./script/delayed_job run the logs of delayed job worker (including Rails.logger) are written into log/development_delayed_jobs.log and sql logs go into log/development_delayed_jobs_sql.log. This helpes better track what happnes while runnin async operation, especially calling of remote services.