DISABLED Test_wrap_kwarg_only_dynamic_shapes (__main__.DynamicShapesHigherOrderOpTests)
DISABLED test_wrap_kwarg_only_dynamic_shapes (main.DynamicShapesHigherOrderOpTests)
The test test_wrap_kwarg_only_dynamic_shapes in the DynamicShapesHigherOrderOpTests suite has been disabled due to its failure in Continuous Integration (CI). This test is crucial for ensuring the correctness and reliability of PyTorch's dynamic shapes functionality. However, its flakiness has made it challenging to diagnose and resolve the issue.
Understanding the Flakiness
The test has been determined to be flaky over the past 3 hours, with 13 workflow failures and 13 successes. This indicates that the test is not consistently passing or failing, making it difficult to pinpoint the root cause of the issue. The recent examples of flaky test runs can be found on the PyTorch HUD, and the most recent workflow logs are available on the GitHub repository.
Debugging Instructions
To debug this issue, follow these steps:
- Click on the recent samples link: Visit the PyTorch HUD to view the recent examples of flaky test runs.
- Click on the workflow logs: Expand the Test step of the job to access the workflow logs.
- Grep for
test_wrap_kwarg_only_dynamic_shapes: Use the grep command to search for the test name in the logs. - Study the logs: Analyze the log snippets to identify patterns or clues that may indicate the cause of the flakiness.
Important Note
When debugging flaky tests, it's essential to remember that a green CI does not necessarily mean that the test is passing consistently. The CI may be shielding flaky tests, making it harder to diagnose issues. Therefore, it's crucial to carefully examine the logs and workflow history to understand the test's behavior.
Test File Path
The test file path for test_wrap_kwarg_only_dynamic_shapes is located in dynamo/test_dynamic_shapes.py.
CC List
The following individuals have been CC'd on this issue:
- @clee2000
- @voznesenskym
- @penguinwu
- @EikanWang
- @jgong5
- @Guobing-Chen
- @XiaobingSuper
- @zhuhaozhe
- @blzheng
- @wenzhe-nrv
- @jiayisunx
- @chenyang78
- @kadeng
- @chauhang
- @amjames
Conclusion
The test_wrap_kwarg_only_dynamic_shapes test has been disabled due to its flakiness in CI. To resolve this issue, it's essential to carefully debug the test by following the provided instructions and analyzing the workflow logs. The test file path and CC list are also provided for reference.
DISABLED test_wrap_kwarg_only_dynamic_shapes (main.DynamicShapesHigherOrderOpTests) - Q&A
Q: What is the current status of the test test_wrap_kwarg_only_dynamic_shapes?
A: The test has been disabled due to its flakiness in Continuous Integration (CI).
Q: What is the reason for the test's flakiness? A: The test is failing in CI, and the recent examples of flaky test runs can be found on the PyTorch HUD.
Q: How can I debug this issue? A: To debug this issue, follow these steps:
- Click on the recent samples link: Visit the PyTorch HUD to view the recent examples of flaky test runs.
- Click on the workflow logs: Expand the Test step of the job to access the workflow logs.
- Grep for
test_wrap_kwarg_only_dynamic_shapes: Use the grep command to search for the test name in the logs. - Study the logs: Analyze the log snippets to identify patterns or clues that may indicate the cause of the flakiness.
Q: Why is the CI shielding flaky tests? A: The CI is shielding flaky tests to prevent developers from assuming that the test is passing consistently. This makes it harder to diagnose issues, but it ensures that the CI remains green.
Q: What is the test file path for test_wrap_kwarg_only_dynamic_shapes?
A: The test file path is located in dynamo/test_dynamic_shapes.py.
Q: Who has been CC'd on this issue? A: The following individuals have been CC'd on this issue:
- @clee2000
- @voznesenskym
- @penguinwu
- @EikanWang
- @jgong5
- @Guobing-Chen
- @XiaobingSuper
- @zhuhaozhe
- @blzheng
- @wenzhe-nrv
- @jiayisunx
- @chenyang78
- @kadeng
- @chauhang
- @amjames
Q: What is the next step in resolving this issue? A: The next step is to carefully debug the test by following the provided instructions and analyzing the workflow logs. This will help identify the root cause of the flakiness and enable the test to be fixed.
Q: Can I contribute to resolving this issue? A: Yes, if you are interested in contributing to resolving this issue, please reach out to the individuals listed in the CC list. They will be able to provide more information and guidance on how to get involved.
Q: How can I stay up-to-date on the status of this issue? A: You can stay up-to-date on the status of this issue by following the PyTorch HUD and the GitHub repository. The issue will be updated regularly with new information and progress.