chore: remove test_hub for now

[tarekziade]

What does this PR do?

Removing test_hub from CI for now

[ydshieh]

OK, let's get rid of it for now.

In you opinion, would it be better to simply let "test_hub" to do nothing, but keep all other places to untouched (like test fetcher etc.), if we are ever to bring it back?

I mean around this block

            {"run": {
                "name": "Run tests",
                "command": f"({timeout_cmd} python3 -m pytest {marker_cmd} -n {self.pytest_num_workers} {junit_flags} {repeat_on_failure_flags} {' '.join(pytest_flags)} $(cat splitted_tests.txt) | tee tests_output.txt)"}
            },

But I am happy to keep what you have done in this PR. It's just another thought for you to judge

[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.

[github-actions]

View the CircleCI Test Summary for this PR:

https://huggingface.co/spaces/transformers-community/circle-ci-viz?pr=45337&sha=9bfb97

[tarekziade]

OK, let's get rid of it for now.

In you opinion, would it be better to simply let "test_hub" to do nothing, but keep all other places to untouched (like test fetcher etc.), if we are ever to bring it back?

I mean around this block

            {"run": {
                "name": "Run tests",
                "command": f"({timeout_cmd} python3 -m pytest {marker_cmd} -n {self.pytest_num_workers} {junit_flags} {repeat_on_failure_flags} {' '.join(pytest_flags)} $(cat splitted_tests.txt) | tee tests_output.txt)"}
            },

But I am happy to keep what you have done in this PR. It's just another thought for you to judge

Thanks ! My hope is that once we've fixed the issues we could simply fully revert that change, so I have not focused on the how.