Skip to content

Run complete test set#501

Draft
ayoopierre wants to merge 1 commit into
masterfrom
ayopierre/libm
Draft

Run complete test set#501
ayoopierre wants to merge 1 commit into
masterfrom
ayopierre/libm

Conversation

@ayoopierre

Copy link
Copy Markdown

Description

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

  • This PR needs additional PRs to work (list the PRs, preferably in merge-order).
  • I will merge this PR by myself when appropriate.

@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown

Unit Test Results (nightly)

     1 files   3 100 suites   6h 8m 38s ⏱️
26 700 tests 22 753 ✅ 3 946 💤 1 ❌
26 886 runs  22 900 ✅ 3 985 💤 1 ❌

For more details on these failures, see this check.

Results for commit 06145e4.

♻️ This comment has been updated with latest results.

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.

1 participant