Fix CUPTI Range Profiler test (pytorch#1091)

Summary:
Pull Request resolved: pytorch#1091

Simple fix that was causing a test failure earlier. The test mocks the object but the destructor calls CUDA deinit() API. This should have been fused out basically.

https://github.com/pytorch/kineto/blob/main/libkineto/src/CuptiRangeProfilerApi.cpp#L716-L719

Reviewed By: sraikund16

Differential Revision: D75494874

fbshipit-source-id: 1426e7ee82592c57a4e5716fd423625819da2918

Author: briancoutinho

libkineto/src/CuptiRangeProfilerApi.cpp

@@ -336,6 +336,7 @@ CuptiRBProfilerSession::CuptiRBProfilerSession(
   // used in unittests only
   if (opts.unitTest) {
     initSuccess_ = true;
+    unitTest_ = true;
     profiler_map[deviceId_] = this;
     return;
   }
@@ -714,7 +715,7 @@ bool CuptiRBProfilerSession::createCounterDataImage() {
 }
 
 CuptiRBProfilerSession::~CuptiRBProfilerSession() {
-  if (initSuccess_) {
+  if (initSuccess_ && !unitTest_) {
     CuptiRBProfilerSession::deInitCupti();
   }
 }

libkineto/src/CuptiRangeProfilerApi.h

@@ -209,6 +209,7 @@ class CuptiRBProfilerSession {
 
   bool initSuccess_ = false;
   bool profilingActive_ = false;
+  bool unitTest_ = false;
 
   friend void __trackCudaKernelLaunch(CUcontext ctx, const char* kernelName);
 };