fbgemm-xpu: add CI workflow

[flezaalv]

cc: @aagalleg, @manuelhsantana, @luis-real

[dvrogozh]

There are couple attempts to break current CI workflow into dedicated torchcodec and fbgemm parts (#86 and #88). Unfortunately we will have some issues with this approach centered around the fact that we have one more package to take care about - torchlib-xpu which is a virtual package depending on other. If you will think thru that you will see that it's not quite trivial to satisfy all the requirements at once such as aligned pytorch version to use across the whole project and having CI in separate workflows for each project.

Overall, I suggest a little bit different strategy. I think we should not break current monolithic CI workflow. I believe that it's better to have single pass to build all the components - this part is cheap enough and 90% the same across both projects. What we need to do is to optimize test time. For that I suggest to add skips of the test jobs depending on the modified paths. Here is respective PR, please, take a look:

• See ci: restrict tests to changes in respective directories #93

@flezaalv , can you, please, modify the PR building on top of #93?

[flezaalv]

There are couple attempts to break current CI workflow into dedicated torchcodec and fbgemm parts (#86 and #88). Unfortunately we will have some issues with this approach centered around the fact that we have one more package to take care about - torchlib-xpu which is a virtual package depending on other. If you will think thru that you will see that it's not quite trivial to satisfy all the requirements at once such as aligned pytorch version to use across the whole project and having CI in separate workflows for each project.

Overall, I suggest a little bit different strategy. I think we should not break current monolithic CI workflow. I believe that it's better to have single pass to build all the components - this part is cheap enough and 90% the same across both projects. What we need to do is to optimize test time. For that I suggest to add skips of the test jobs depending on the modified paths. Here is respective PR, please, take a look:

• See ci: restrict tests to changes in respective directories #93

@flezaalv , can you, please, modify the PR building on top of #93?

I will do

[dvrogozh]

You need to rebase the

[dvrogozh]

Can you, please, move packages/fbgemm-xpu/test/patches/.gitkeep‎ to packages/fbgemm-xpu/patches/.gitkeep‎? This will correlate with the placement of the patches for torchcodec.

[flezaalv]

Can you, please, move packages/fbgemm-xpu/test/patches/.gitkeep‎ to packages/fbgemm-xpu/patches/.gitkeep‎? This will correlate with the placement of the patches for torchcodec.

Done.

[dvrogozh]

@flezaalv , I think this PR is almost ready. Please, take a look and reply at last couple comments and mark as ready for review.

[dvrogozh]

LGTM

[luis-real]

LGTM

[aagalleg]

LGTM