Using process forking, the SQL generation (not the migration) starts looping on Mac. Using the regular build, no output is shown (only symptom is 100% cpu). A hard coded fail in the forked strategy allows for debugging output to be shown (yet does not solve the problem).

Submitted by Sander Vermolen on 6 April 2010 at 11:46

On 8 September 2010 at 14:40 Sander Vermolen commented:

Blocking this issue for now. Process forking is obsolete. Focus of platform has shifted to Java and focus of migration has shifted to SQL.


On 8 September 2010 at 14:40 Sander Vermolen closed this issue.

Log in to post comments