Closed ezyang closed 7 years ago
The segfault you linked here was fixed in the SimpleEval PR: https://github.com/ezyang/pytorch/pull/215/files#diff-075c575cc319a2db2a532dcaeb93c403R23
Aaaand that's why I post things up like this :) Any idea why this isn't failing on ezyang/jit though?
It doesn't segfault anymore.
Yeah. Sam reverted a few of my changes, that made it more likely for certain graph edges to be NULL.
Can you just squash the Bug fix
commit into Add simple mode to Eval
? I put it as a separate commit just for the code review, but wanted to squash when merging
Bug fix squashed, and everything merged.
This rebases JIT onto master; most notably, it rebases onto the Variable/ATen changes from @colesbury.
Below is obsolete.
Unfortunately, the rebase segfaults.
I double checked the diff and it looked fine: https://phabricator.intern.facebook.com/P58196566 (this diff was created by diffing this PR against a merge of ezyang/jit (b4ad6de43c030f3bbbb85e21f52efe7c268de974) and origin/master (1290e586fbc3d6266423f3417723d6620267054b) for which we didn't resolve any conflicts and just took the conflict markers.) So some debugging seems to be in order.
The other tests that segfault are: