[Nova] Disable CircleCI Linux CPU Unittests

[osalpekar]

Linux CPU and GPU Unittests have been running smoothly for several weeks, so going ahead and removing the CircleCI Linux Unittest jobs. If we see any issues or high queueing, we can bring this back.

cc @seemethere

[pmeier]

@osalpekar I don't think this is the case for GPU: #6957. Could you look into this first?

@NicolasHug, AFAIK we want to skip the CPU tests on GPU machines, right? I think we need to update

vision/test/conftest.py

Lines 15 to 24 in 4a310f2

	def pytest_collection_modifyitems(items):
	# This hook is called by pytest after it has collected the tests (google its name to check out its doc!)
	# We can ignore some tests as we see fit here, or add marks, such as a skip mark.
	#
	# Typically here, we try to optimize CI time. In particular, the GPU CI instances don't need to run the
	# tests that don't need CUDA, because those tests are extensively tested in the CPU CI instances already.
	# This is true for both CircleCI and the fbcode internal CI.
	# In the fbcode CI, we have an additional constraint: we try to avoid skipping tests. So instead of relying on
	# pytest.mark.skip, in fbcode we literally just remove those tests from the `items` list, and it's as if
	# these tests never existed.

to also account for GHA. Do you want to send a patch or shall I?

[pmeier]

@osalpekar In #6970 I've confirmed that the GPU setup is incorrect and so far we have never run any CUDA tests on GHA. This needs to be addressed first. If you prefer, I'm also ok with moving this PR forward if we exclude the removal of the CUDA jobs.

[osalpekar]

@pmeier Sounds good, I've added back the Linux GPU CI jobs here, so this PR only disabled Linux CPU unittests.

[pmeier]

No concerns regarding CPU unittests from my side. Thanks Omkar!

[github-actions]

Hey @osalpekar!

You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py