One case in Integrated test sometimes fails (GPU tests)

[Critsium-xy]

Describe the bug

It happens very randomly and seldom happens, so it is hard to spot. But I met this in one of my pull requests, so I just recorded this problem. No clear way to reproduce.

Expected behavior

No response

To Reproduce

No response

Environment

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

• [ ] Verify the issue is not a duplicate.
• [ ] Describe the bug.
• [ ] Steps to reproduce.
• [ ] Expected behavior.
• [ ] Error message.
• [ ] Environment details.
• [ ] Additional context.
• [ ] Assign a priority level (low, medium, high, urgent).
• [ ] Assign the issue to a team member.
• [ ] Label the issue with relevant tags.
• [ ] Identify possible related issues.
• [ ] Create a unit test or automated test to reproduce the bug (if applicable).
• [ ] Fix the bug.
• [ ] Test the fix.
• [ ] Update documentation (if necessary).
• [ ] Close the issue and inform the reporter (if applicable).

[Critsium-xy]

Not reproduceable at all. It will disappear when I rerun the tests.

[Critsium-xy]

Another one

[Flying-dragon-boxing]

Another one

I also met this in my PR recently

[Cstandardlib]

Another one

This is CPU lcao, different from the first PW GPU. The PW_OW_GPU is undergoing a refactor process and still has bug when output wfc on GPU, pending for the output function to be rewrite for GPU use.