Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Bug 删除这条 ignore 后,
coverage_run.sh的收集阶段会导入并实际执行tests/distributed/test_fusedmoe_ep_entry.py。coverage_run.sh先执行python -m pytest --collect-only -q -c ${PYTEST_INI} tests来收集文件;被恢复的测试文件底部有未受if __name__ == "__main__"保护的test_fused_moe_launch(),导入时就会启动paddle.distributed.launch --gpus 0,1。后续run_test_with_logging再跑该文件时,pytest 导入会再执行一次,随后测试函数本身还会执行一次,导致覆盖率任务重复启动分布式子进程,并且第一次发生在收集阶段,绕过分类、重试和日志目录隔离。建议修复方式:
先保留这条 ignore,或在恢复前把
tests/distributed/test_fusedmoe_ep_entry.py的模块级调用移到if __name__ == "__main__":下,并给 pytest 入口补上显式的多 GPU 可用性 skip/gate,确保 collect-only 只收集、不执行分布式任务。