Skip to content
Closed
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 23 additions & 4 deletions project-infrastructure/project-ci-documentation.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,23 +78,42 @@ Representative: Timmie Smith

Support contact for CI:

| Maintainers |
| ------------------------- |
| Dan Hoeflinger @danhoeflinger |
| Dmitriy Sobolev @dmitriy-sobolev |
| Timmie Smith @timmiesmith |

*Existing public CI*
Copy link

@dmitriy-sobolev dmitriy-sobolev Apr 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be nice to mention how to run this CI, e.g. that it is automatically triggered in oneDPL repository when a PR is opened and a new commit is made.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is too much detail for what is being requested at this time.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.


| Owner | Type | OS | Number | Active? | How to access logs |
| --- | --- | --- | --- | --- | --- |
| ? | ? | ? | ? | ? | ? |
| GitHub | CPU x86 | Ubuntu | 11 | Yes | Via CI Testing Workflow view |
| GitHub | CPU x86 | Windows | 3 | Yes | Via CI Testing Workflow view |
| GitHub | AArch64 | Mac OS | 1 | Yes | Via CI Testing Workflow view |

*Required Public CI Infrastruture Needed To Confidently Accept Contributions*

| Instruction set architecture | Hardware Vendor | Processor Type | Operating System |
| --- | --- | --- | --- |
| x86 | Intel | CPU | Ubuntu |
| AArch64 | Arm | CPU | Ubuntu |
| Xe, Xe2, Xe3 | Intel | GPU | Ubuntu, Windows |
| | NVIDIA | GPU | Ubuntu, Windows |
| | AMD | GPU | Ubuntu, Windows |

Software Versions:
* CMake
* glibc
* ...
| Windows | Linux | MacOS (Arm CPU testing) |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be more readable to have "Software" or "Tool" as a first column. The cells may contain for example: minimal version number, "any" or "-" (not needed).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

version information is too much detail in my opinion.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Different product on one line still bothers me (such as dpc++ compiler and clang++ compiler). I suggest making a bullet list.

You can ignore this comment though - it is a matter of taste.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the Software column.

| --- | --- | --- |
| CMake 3.20 | CMake 3.11 | CMake 3.11 |
| git | git | git |
| python | python | python |
| miniforge-python | miniforge-python | miniforge-python |
| DPC++ Compiler | DPC++ Compiler | clang++ compiler |
| gmake | clang++ compiler | |
| ninja | g++ | |
| Visual Studio 2019 | | |
| Visual Studio 2022 | | |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should also mention the supported GPU driver and their versions. It is a yet another tool oneDPL depends on.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is too much detail at this point.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The question of how much detail is needed in this document was discussed in the UXL Open Source Working Group meeting. The feedback received is that any details on configurations teams can provide is useful, so I will add the details suggested.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

oneDAL
------
Expand Down