Hmm. I have had similar problems with this before, and I don’t think I ever discovered a root cause. Perhaps changing TVM version to the more stable 0.7 could help, unless there’s a key feature in 0.8 that you need.
You mentioned local runner, so it won’t be network issues.
Otherwise, another approach could be a binary search of commenting out half of the network, seeing if it crashes. If not, uncomment the 3rd quarter, if it does, comment out the 2nd quarter, etc. Maybe it’s a single layer that is breaking TVM, and could serve as a bug report.
Thank you. I will check the network next… It’s so weird because I know some CUDA schedules can be invalid, but such cases are so rare with LLVM target which does not requires launch parameters, etc.
But I will check the model if something wrong. Thank you again…
Yeah, my experience was also with an LLVM target. I don’t recall there being an obvious error cause. Good luck, sorry I couldn’t bring more illumination.