Closed
Description
Describe the bug
AllocatorTest.CUDAAllocatorTest
hangs forever if build machine does not have GPU available (but with CUDA toolchain installed).
I think in this case CUDA test should be skipped or at least failed, hanging is not the right way.
[----------] 5 tests from AllocatorTest
[ RUN ] AllocatorTest.CPUAllocatorTest
[ OK ] AllocatorTest.CPUAllocatorTest (0 ms)
[ RUN ] AllocatorTest.MakeUniquePtrTest
[ OK ] AllocatorTest.MakeUniquePtrTest (0 ms)
[ RUN ] AllocatorTest.TestOverflowChecks
2020-07-29 10:33:20.7040916 [E:onnxruntime:Default, allocator.cc:28 onnxruntime::IAllocator::CalcMemSizeForArrayWithAlignment] D:\roaster-scratch\onnxruntime\onnxruntime\core/common/safeint.h:17 SafeIntExceptionHandler<class onnxruntime::OnnxRuntimeException>::SafeIntOnOverflow Integer overflow
2020-07-29 10:33:20.7048544 [E:onnxruntime:Default, allocator.cc:28 onnxruntime::IAllocator::CalcMemSizeForArrayWithAlignment] D:\roaster-scratch\onnxruntime\onnxruntime\core/common/safeint.h:17 SafeIntExceptionHandler<class onnxruntime::OnnxRuntimeException>::SafeIntOnOverflow Integer overflow
2020-07-29 10:33:20.7055700 [E:onnxruntime:Default, allocator.cc:28 onnxruntime::IAllocator::CalcMemSizeForArrayWithAlignment] D:\roaster-scratch\onnxruntime\onnxruntime\core/common/safeint.h:17 SafeIntExceptionHandler<class onnxruntime::OnnxRuntimeException>::SafeIntOnOverflow Integer overflow
2020-07-29 10:33:20.7063018 [E:onnxruntime:Default, allocator.cc:28 onnxruntime::IAllocator::CalcMemSizeForArrayWithAlignment] D:\roaster-scratch\onnxruntime\onnxruntime\core/common/safeint.h:17 SafeIntExceptionHandler<class onnxruntime::OnnxRuntimeException>::SafeIntOnOverflow Integer overflow
[ OK ] AllocatorTest.TestOverflowChecks (3 ms)
[ RUN ] AllocatorTest.CUDAAllocatorTest
System information
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Win Server 2019
- ONNX Runtime installed from (source or binary): source
- ONNX Runtime version: 1.4.0
- Python version: 3.8.5
- Visual Studio version (if applicable): 2019
- CUDA/cuDNN version: 11.0 (10.2 also have this issue)
- GPU model and memory: N/A