Fix CI due to pytest

[muellerzr]

Pytest released a new version that broke our CI because:

Files and directories are now collected in alphabetical order jointly, unless changed by a plugin. Previously, files were collected before directories. See below for an example.

The failures were coming from deepspeed being the first one being ran instead of later on. This PR change make test to run in the following order:

test:
	$(MAKE) test_core
	$(MAKE) test_cli
	$(MAKE) test_big_modeling
	$(MAKE) test_deepspeed
	$(MAKE) test_fsdp

Instead of the prior:

python -m pytest -s -v ./tests/ --ignore=./tests/test_examples.py $(if $(IS_GITHUB_CI),--report-log "$(PYTORCH_VERSION)_all.log",)

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[SunMarc]

It's great that we manage to fix the issue without having to pin pytest ! LGTM !

[akx]

Hold on, why is the order of tests significant for the test suite to pass? 😳

[SunMarc]

Yeah, this is definitely strange, but the deepspeed tests seems to mess up with our env. Very simple tests were failing because of that. We will investigate this further when we get the time !