[SOT] Always use dummy_guard when fallback error occurred

[SigureMo]

PR Category

Execute Infrastructure

PR Types

Bug fixes

Description

这里针对 disable_eval_frame = True 逻辑不确定原因，可能是过去有别的场景，但目前代码是没有 disable_eval_frame = True 的，一旦真的 disable_eval_frame = True 会在外部首次 translate guard 不为 None 的检查处挂掉，所以这里应该是可以安全删掉的

[paddle-bot]

你的PR提交成功，感谢你对开源项目的贡献!
请关注后续CI自动化测试结果，详情请参考Paddle-CI手册。
Your PR has been submitted. Thanks for your contribution!
Please wait for the result of CI firstly. See Paddle CI Manual for details.

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

python/paddle/jit/sot/opcode_translator/executor/executor_cache.py:295

• The removal of the condition checking 'e.disable_eval_frame is False' in strict mode now causes a raise for every case where strict mode is enabled. Please double-check if this behavior is intended in all scenarios; if not, reintroducing a condition or adding a clarifying comment may be appropriate.

if is_strict_mode():

python/paddle/jit/sot/opcode_translator/executor/executor_cache.py:304

• Since the conditional assignment of the guard function has been removed, 'dummy_guard' is always used. Consider verifying that components downstream do not rely on the previous behavior using simulator.guard_fn, and if needed, update the documentation or add a comment explaining this change.

dummy_guard,