Hi, thanks for this notification. It's a bit strange that patch 1/2 [1] failed 
and patch 2/2 [2] passed.

[1]: 
https://patchwork.sourceware.org/project/glibc/patch/[email protected]/
[2]: 
https://patchwork.sourceware.org/project/glibc/patch/[email protected]/

Is everything OK with the CI Job?

Thanks,
Yury


________________________________________
From: [email protected] <[email protected]>
Sent: 29 July 2026 10:55 AM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #140108: 3 regressions 111 fixes on arm

Dear contributor,

Our automatic CI has detected problems related to your patch(es). Please find 
some details below.

In glibc_check master-arm, after:
  | glibc patch https://patchwork.sourceware.org/patch/140108
  | Author: Yury Khrustalev <[email protected]>
  | Date:   Tue Jul 28 17:12:14 2026 +0100
  |
  |     [PATCH 1/2] malloc: Refactor malloc API into a separate header
  |
  |     This commit moves declarations for various malloc functions from
  |     the malloc.c file to a separate header that can be used to include
  |     these declarations in other source files.
  | ... 2 lines of the commit log omitted.
  | ... applied on top of baseline commit:
  | 26f0f2aa7d benchtests: Create objdir in the bench-%.c generation rule

Produces 3 regressions 111 fixes:
  |
  | regressions.sum:
  | Running glibc:posix ...
  | FAIL: posix/tst-affinity
  | FAIL: posix/tst-affinity-pid
  | FAIL: posix/tst-affinity-static
  |
  | fixes.sum:
  | Running glibc:debug ...
  | FAIL: debug/tst-fortify-syslog
  | Running glibc:dirent ...
  | FAIL: dirent/tst-readdir-long
  | ... and 123 more

<...>
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
_______________________________________________
linaro-toolchain mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to