Generally,the seed is 1234 in testing. When I was debugging the test code  (test_ops.py),  I find in Linux (Ubuntu 16:04, Geforce 1080), when the op is acos and device is cuda:0, the seed is changed.
The function of make_tensor, which in testing\common_utils.py result is.
input:tensor([-0.7754+0.9690j, -0.2091-0.4136j,  0.9258+0.6882j, -0.8382-0.4225j,
0.8441-0.1108j, -0.5019+0.6919j, -0.1726+0.5296j,  0.3494-0.6687j,
-0.2975+0.4149j, -0.3018-0.2714j, -0.8510+0.9209j,  0.8011-0.6919j,
-0.9471-0.7434j, -0.2749+0.2165j, -0.9148-0.3147j,  0.4287-0.4181j,
-0.7237-0.8627j, -0.9948+0.8622j,  0.9395+0.6238j, -0.0843-0.6137j],
device=‘cuda:0’, dtype=torch.complex128, requires_grad=True)
If the seed is 1234, the result is.
tensor([ 0.7069-0.7754j, -0.3517-0.2091j,  0.8470+0.9258j,  0.4945-0.8382j,
0.2541+0.8441j,  0.4346-0.5019j,  0.6110-0.1726j, -0.7419+0.3494j,
0.2255-0.2975j,  0.7646-0.3018j, -0.9519-0.8510j,  0.5869+0.8011j,
-0.5018-0.9471j,  0.0435-0.2749j, -0.8904-0.9148j, -0.8258+0.4287j,
0.2637-0.7237j,  0.7252-0.9948j, -0.5960+0.9395j, -0.8582-0.0843j],
device=‘cuda:0’, dtype=torch.complex128, requires_grad=True)
I debugged in Linux CPU, windows CPU and GPU. The input tensors are all generated by seed of 1234 in the same condition.
So far, I don’t find when the seed is changed and bad impacts of this change.