Skip to content

feature: Add pyzes support for info log APIs - #522

Open
aviralni wants to merge 6 commits into
oneapi-src:masterfrom
aviralni:pyzes_infolog
Open

aviralni wants to merge 6 commits into
oneapi-src:masterfrom
aviralni:pyzes_infolog

Conversation

@aviralni

@aviralni aviralni commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

feature: Add pyzes support for info log APIs
Add python bindings, unit tests, black box test coverage and README
entries for:

  1. zesDriverEnumInfoLogsExt
  2. zesInfoLogGetPropertiesExt
  3. zesInfoLogCreateInstanceExt
  4. zesInfoLogInstanceReadWithMetadataExt
  5. zesInfoLogInstancePeekWithMetadataExt
  6. zesInfoLogInstanceDeleteExt

Related-To: SYSM-432

Signed-off-by: Aviral Nigam aviral.nigam@intel.com

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot review overview

🟡 Changes recommended

Test failures are not propagated, warning results are mishandled, and the documented package version is inconsistent.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 3 Medium severity · 1 Low severity

Open (4)
What changed in this PR

Adds Python Sysman bindings and validation coverage for Info Log APIs.

Changes:

  • Adds Info Log handles, enums, structures, and API wrappers.
  • Adds unit and black-box tests.
  • Documents supported Info Log APIs.
File Description
pyzes.py Adds Info Log bindings.
test_info_log.py Adds wrapper unit tests.
pyzes_black_box_test.py Adds Info Log runtime tests and CLI option.
README.md Documents API support.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread bindings/sysman/python/source/examples/pyzes_black_box_test.py Outdated
Comment thread bindings/sysman/python/source/examples/pyzes_black_box_test.py Outdated
Comment thread bindings/sysman/python/source/examples/pyzes_black_box_test.py Outdated
Comment thread bindings/sysman/python/README.md
Add python bindings, unit tests, black box test coverage and README
entries for:
1. zesDriverEnumInfoLogsExt
2. zesInfoLogGetPropertiesExt
3. zesInfoLogCreateInstanceExt
4. zesInfoLogInstanceReadWithMetadataExt
5. zesInfoLogInstancePeekWithMetadataExt
6. zesInfoLogInstanceDeleteExt

Related-To: SYSM-432

Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Report info log properties by default and collect records only with
--instance-api, --instance-peek or --instance-read as root.
A failed zesDriverEnumInfoLogsExt call printed an error but both -a and
-l still exited with status 0. Aggregate the info log test result into
the exit status. Info logs are driver scoped, so also run them when
device enumeration fails or returns no devices.

Related-To: SYSM-432
Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
…ck box test

ZE_RESULT_WARNING_DROPPED_DATA can be returned by a query call and still
comes with a valid size and record count. The query helper passed no
read status and its callers failed on the warning. Pass a read status,
report the dropped record count and treat the warning as success, as
queryInfoLogRecords in zello_sysman does.

Related-To: SYSM-432
Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
…box test

zello_sysman runs the info log test with -L and takes --instanceapi,
--instancepeek, --instanceread and --buffersize. Use the same spellings
instead of -l, --instance-api, --instance-peek, --instance-read and
--buffer-size.

Related-To: SYSM-432
Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Add python bindings, unit tests, black box test coverage and README
entries for:
1. zesDriverEnumInfoLogsExt
2. zesInfoLogGetPropertiesExt
3. zesInfoLogCreateInstanceExt
4. zesInfoLogInstanceReadWithMetadataExt
5. zesInfoLogInstancePeekWithMetadataExt
6. zesInfoLogInstanceDeleteExt

Related-To: SYSM-432

Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants