RTEMS Tools | tester: Read the RTEMS ELF notes (!99)

[Sebastian Huber (@sebhub)]

Sebastian Huber created a merge request: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/99

Project:Branches: sebhub/rtems-tools:up/elf-notes to rtems/tools/rtems-tools:main
Author: Sebastian Huber

## Summary

Issue rtems/rtos/rtems#4888: Add support for ELF notes

**Problem:** With rtems/rtos/rtems!1561, an RTEMS executable carries its version, build options, tools and test state as ELF notes and no longer prints them. `rtems-test` took these values from the output alone. It counted an expected fail as a failure, and it counted a user input or benchmark program as a pass and ran it to its end.

**Fix:** `tester/rt/elfnotes.py` reads the RTEMS notes of an executable before it runs. The report takes the values from the notes, and an output line of an older RTEMS overrides a note. A user input or benchmark program stops after its begin line.

**Review hints:**

- The note reader is pure Python and handles 32 and 64 bit ELF files in both byte orders.
- `tests/test_rt_elfnotes.py` holds the unit tests.

## Test

`sparc/gr740` on SIS, 678 tests:

| Tester | RTEMS | Result |
| --- | --- | --- |
| this MR | `main` | same result as unchanged tester for each test |
| this MR | !1561 | same result as unchanged tester on `main` for each test |
| this MR | !1561, clang 21 | notes and test states as with GCC |
| unchanged | !1561 | 25 expected fails as failures |

## AI Details
<!-- Make sure you have read our statement at https://www.rtems.org/generative-ai/ -->

### Prompt used

None as a single prompt.  The work was done in an interactive Claude Code session on the RTEMS Tools tree.  Each change was directed and reviewed.

### AI model used

Claude Opus 5.5 (claude-opus-5-5), through Claude Code.

### How AI was used for the contribution

- ( ) Formatting
- (x) Test creation.
- (x) Code comments.
- ( ) The entire contribution was generated using AI
- ( ) AI code completion such as Copilot in VSCode.

The implementation, the unit tests and the commit message were produced in that session under my direction.

### Access

I have not used a product which claims copyright in its output, and I have legitimate access to the one I used.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/99
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/13/sent_notifications/6-3onrwfheq35vzfoks0cbyo15x-d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20261105/50320d8b/attachment-0001.htm>