Skip to content

[DO NOT MERGE] Add debug output for flaky struct deep copy test#3927

Closed
huaweil-nv wants to merge 3 commits intoNVIDIA:mainfrom
huaweil-nv:debug/cudaq-492-flaky-test
Closed

[DO NOT MERGE] Add debug output for flaky struct deep copy test#3927
huaweil-nv wants to merge 3 commits intoNVIDIA:mainfrom
huaweil-nv:debug/cudaq-492-flaky-test

Conversation

@huaweil-nv
Copy link
Collaborator

Description

Signed-off-by: huaweil <huaweil@nvidia.com>
@copy-pr-bot
Copy link

copy-pr-bot bot commented Feb 11, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@huaweil-nv
Copy link
Collaborator Author

huaweil-nv commented Feb 11, 2026

/ok to test a592f21

Command Bot: Processing...

@huaweil-nv
Copy link
Collaborator Author

huaweil-nv commented Feb 11, 2026

/ok to test a592f21

Command Bot: Processing...

@huaweil-nv
Copy link
Collaborator Author

huaweil-nv commented Feb 11, 2026

/ok to test 7553182

Command Bot: Processing...

@github-actions
Copy link

CUDA Quantum Docs Bot: A preview of the documentation can be found here.

Signed-off-by: huaweil <93200147+huaweil-nv@users.noreply.github.com>
@huaweil-nv
Copy link
Collaborator Author

huaweil-nv commented Feb 12, 2026

/ok to test 781d0a8

Command Bot: Processing...

@schweitzpgi
Copy link
Collaborator

Are you only seeing this on Python 3.11?

@huaweil-nv
Copy link
Collaborator Author

Are you only seeing this on Python 3.11?

Hi @schweitzpgi
Yes, it's only been seen on Python 3.11, but more precisely, only on the Python 3.11 + arm64 + cuda12.6 + Fedora 42 configuration. Other Python 3.11 configurations (e.g. different architectures or OS) have not shown this failure.
The issue was initially seen in two separate CI runs on this specific configuration(refer: https://nvidia.slack.com/archives/C03KV6A81HT/p1770744080083629), which led to the test being disabled. However, I've since re-run the CI about 4 times on this configuration and have been unable to reproduce the failure. At this point, I suspect it's more likely a CI environment issue rather than a code bug.

@huaweil-nv huaweil-nv closed this Feb 24, 2026
github-actions bot pushed a commit that referenced this pull request Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants