Skip to content

Conversation

@etiaro
Copy link
Contributor

@etiaro etiaro commented Aug 5, 2025

RTOS-736

Description

Tests results

Motivation and Context

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (refactoring, style fixes, git/CI config, submodule management, no code logic changes)

How Has This Been Tested?

  • Already covered by automatic testing.
  • New test added: (add PR link here).
  • Tested by hand on: (list targets here).

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing linter checks and tests passed.
  • My changes generate no new compilation warnings for any of the targets.

Special treatment

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @etiaro, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've added a comprehensive suite of new tests to the libc component, primarily focusing on signal handling and the sigaction system call. This includes tests for various signal dispositions, masked signal behavior, handler recursion, and the interaction of sigaction within signal handlers. Additionally, I've included a new test case for pthread_cancel to ensure proper cleanup handler execution.

Highlights

  • Pthread Cleanup Test: Added a new test case pthread_cleanup_push_pthread_cancel to verify the correct execution of pthread cleanup handlers when a thread is cancelled.
  • Comprehensive Signal Handling Tests: Introduced a new TEST_GROUP(sigaction) with numerous test cases to thoroughly validate the behavior of the sigaction system call, covering signal termination, default ignored signals, unmasking signals with changing actions, handler recursion, and sigaction calls from within signal handlers.
  • Signal Test Utilities: Implemented new helper functions (safe_fork, sighandlerRecursive, sighandlerReraise, sighandlerAction) to facilitate the creation of robust and diverse signal handling test scenarios.
  • Test Suite Integration: Integrated the newly added sigaction test group into the main libc signal test runner to ensure these new tests are executed as part of the standard test suite.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a comprehensive suite of tests for POSIX signals, particularly focusing on sigaction behaviors, and a new test for pthread_cancel with cleanup handlers. The changes are valuable for improving the test coverage of the C library. I've identified a couple of issues in the new test implementations: a race condition that could lead to test flakiness, and a logical flaw in one of the signal tests. My review includes suggestions to address these points to improve the robustness and correctness of the new tests.

@github-actions
Copy link

github-actions bot commented Aug 5, 2025

Unit Test Results

9 603 tests  +170   8 996 ✅ +152   51m 31s ⏱️ + 2m 3s
  545 suites ±  0     601 💤 + 12 
    1 files   ±  0       6 ❌ +  6 

For more details on these failures, see this check.

Results for commit 39de784. ± Comparison against base commit f646ce7.

♻️ This comment has been updated with latest results.

JIRA: RTOS-1076
Additional signal tests for phoenix-rtos/phoenix-rtos-kernel#670 moving signal handling to kernel

JIRA: RTOS-736
Adjust tests to signalPost removal

JIRA: RTOS-736
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.

2 participants