Fix wrong initialisation error message

[qin-yu]

Attempt to fix #603

Before fix:

Error: Exception while generating log record in module CUDA at 
/home/qyu/.julia/dev/CUDA/src/initialization.jl:34
│   exception =
│    UndefVarError: ex not defined
│    Stacktrace:
...

After fix:

┌ Error: Recursion during initialization of CUDA.jl
└ @ CUDA ~/.julia/dev/CUDA/src/initialization.jl:38
┌ Error: Error during initialization of CUDA.jl
│   exception =
│    CUDA error (code 999, CUDA_ERROR_UNKNOWN)
│    Stacktrace:
...

[qin-yu]

Hi @vchuravy @maleadt ! Do you know why "All checks have failed" though I only fixed one line of code 😮

[maleadt]

Thanks for the fix! Something was wrong with CI, so I fixed that and rebased your PR. Should be good to go then.

[qin-yu]

Thanks for the fix! Something was wrong with CI, so I fixed that and rebased your PR. Should be good to go then.

Looks like some Error During Test at /root/.julia/packages/GPUArrays/jhRU7/test/testsuite/mapreduce.jl were making the Julia 1.6 (debug) fail (either OOM or illegal assess) in the first run. May I ask what happened? Just out of curiosity.

[codecov]

Codecov Report

Merging #604 (99b24e6) into master (c085721) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #604      +/-   ##
==========================================
+ Coverage   79.95%   79.98%   +0.02%     
==========================================
  Files         116      116              
  Lines        6866     6866              
==========================================
+ Hits         5490     5492       +2     
+ Misses       1376     1374       -2     

Impacted Files	Coverage Δ
src/initialization.jl	78.78% <ø> (ø)
lib/cudadrv/stream.jl	89.47% <0.00%> (+2.63%)	⬆️
lib/cudadrv/module.jl	73.33% <0.00%> (+3.33%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c085721...99b24e6. Read the comment docs.

[maleadt]

I'm not sure what happened, to be honest. I didn't see a sign of OOM, but that often corrupts internal state of libraries which can lead to spurious errors like execution failures. Either way, definitely unrelated to your PR.