Hi Linaro Toolchain Team,
I got this regression email for one of my patch but failure does not look like related to the change. Also this look like a false positive to me as test is failing in baseline also.
From the logs regression is shown in | Running gdb:gdb.cp/nextoverthrow.exp ... | FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact...
But the baseline file also has the same failure in sum file and somehow not shown in xfail file: The list of [ignored] baseline and flaky failures are in https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact...
Thanks & Best Regards Abdul Basit
-----Original Message----- From: ci_notify@linaro.org ci_notify@linaro.org Sent: Saturday, October 26, 2024 4:29 AM To: Ijaz, Abdul B abdul.b.ijaz@intel.com Subject: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 regressions on arm
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
In gdb_check master-arm after:
| gdb patch https://patchwork.sourceware.org/patch/99582 | Author: Ijaz, Abdul B abdul.b.ijaz@intel.com | Date: Fri Oct 25 16:37:46 2024 +0200 | | [PATCH v8 1/1] fortran: Fix arrays of variable length strings for FORTRAN | | Before this change resolve_dynamic_array_or_string was called for | all TYPE_CODE_ARRAY and TYPE_CODE_STRING types, but, in the end, | this function always called create_array_type_with_stride, which | ... 65 lines of the commit log omitted. | ... applied on top of baseline commit: | 3d17c881721 [gdb] Handle bad alloc in gdb_rl_callback_read_char_wrapper_noexcept
FAIL: 1 regressions
regressions.sum: | === gdb tests === | | Running gdb:gdb.cp/nextoverthrow.exp ... | FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout) | The configuration of this build is: CI config tcwg_gdb_check master-arm configure and test flags: --target arm-linux-gnueabihf
You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact... The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact... The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact...
The configuration of this build is: CI config tcwg_gdb_check master-arm configure and test flags: --target arm-linux-gnueabihf
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact... Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1919/artifact/art...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files. Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
Hi Maxim,
Can you please have a look at my email below and please confirm me if it is false positive. I have mentioned the details of the issue in my email below. Waiting for your feedback. Thanks,
Best Regards Abdul Basit
-----Original Message----- From: Ijaz, Abdul B Sent: Saturday, October 26, 2024 12:03 PM To: linaro-toolchain@lists.linaro.org Subject: RE: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 regressions on arm
Hi Linaro Toolchain Team,
I got this regression email for one of my patch but failure does not look like related to the change. Also this look like a false positive to me as test is failing in baseline also.
From the logs regression is shown in | Running gdb:gdb.cp/nextoverthrow.exp ... | FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact...
But the baseline file also has the same failure in sum file and somehow not shown in xfail file: The list of [ignored] baseline and flaky failures are in https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact...
Thanks & Best Regards Abdul Basit
-----Original Message----- From: ci_notify@linaro.org ci_notify@linaro.org Sent: Saturday, October 26, 2024 4:29 AM To: Ijaz, Abdul B abdul.b.ijaz@intel.com Subject: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 regressions on arm
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
In gdb_check master-arm after:
| gdb patch https://patchwork.sourceware.org/patch/99582 | Author: Ijaz, Abdul B abdul.b.ijaz@intel.com | Date: Fri Oct 25 16:37:46 2024 +0200 | | [PATCH v8 1/1] fortran: Fix arrays of variable length strings for FORTRAN | | Before this change resolve_dynamic_array_or_string was called for | all TYPE_CODE_ARRAY and TYPE_CODE_STRING types, but, in the end, | this function always called create_array_type_with_stride, which | ... 65 lines of the commit log omitted. | ... applied on top of baseline commit: | 3d17c881721 [gdb] Handle bad alloc in gdb_rl_callback_read_char_wrapper_noexcept
FAIL: 1 regressions
regressions.sum: | === gdb tests === | | Running gdb:gdb.cp/nextoverthrow.exp ... | FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout) | The configuration of this build is: CI config tcwg_gdb_check master-arm configure and test flags: --target arm-linux-gnueabihf
You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact... The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact... The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact...
The configuration of this build is: CI config tcwg_gdb_check master-arm configure and test flags: --target arm-linux-gnueabihf
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact... Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1919/artifact/art...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files. Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
Hi Abdul,
Sorry for the delay.
Indeed, the report seems wrong. I see the test failing in the baseline results, but the xfails file generated from those results does not include the test. We will investigate.
Thanks!
-- Maxim Kuvyrkov https://www.linaro.org
On Oct 29, 2024, at 11:33, Ijaz, Abdul B abdul.b.ijaz@intel.com wrote:
Hi Maxim,
Can you please have a look at my email below and please confirm me if it is false positive. I have mentioned the details of the issue in my email below. Waiting for your feedback. Thanks,
Best Regards Abdul Basit
-----Original Message----- From: Ijaz, Abdul B Sent: Saturday, October 26, 2024 12:03 PM To: linaro-toolchain@lists.linaro.org Subject: RE: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 regressions on arm
Hi Linaro Toolchain Team,
I got this regression email for one of my patch but failure does not look like related to the change. Also this look like a false positive to me as test is failing in baseline also.
From the logs regression is shown in | Running gdb:gdb.cp/nextoverthrow.exp ... | FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
You can find the failure logs in *.log.1.xz files in
But the baseline file also has the same failure in sum file and somehow not shown in xfail file: The list of [ignored] baseline and flaky failures are in https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact...
Thanks & Best Regards Abdul Basit
-----Original Message----- From: ci_notify@linaro.org ci_notify@linaro.org Sent: Saturday, October 26, 2024 4:29 AM To: Ijaz, Abdul B abdul.b.ijaz@intel.com Subject: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 regressions on arm
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
In gdb_check master-arm after:
| gdb patch https://patchwork.sourceware.org/patch/99582 | Author: Ijaz, Abdul B abdul.b.ijaz@intel.com | Date: Fri Oct 25 16:37:46 2024 +0200 | | [PATCH v8 1/1] fortran: Fix arrays of variable length strings for FORTRAN | | Before this change resolve_dynamic_array_or_string was called for | all TYPE_CODE_ARRAY and TYPE_CODE_STRING types, but, in the end, | this function always called create_array_type_with_stride, which | ... 65 lines of the commit log omitted. | ... applied on top of baseline commit: | 3d17c881721 [gdb] Handle bad alloc in gdb_rl_callback_read_char_wrapper_noexcept
FAIL: 1 regressions
regressions.sum: | === gdb tests === | | Running gdb:gdb.cp/nextoverthrow.exp ... | FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout) | The configuration of this build is: CI config tcwg_gdb_check master-arm configure and test flags: --target arm-linux-gnueabihf
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
The configuration of this build is: CI config tcwg_gdb_check master-arm configure and test flags: --target arm-linux-gnueabihf
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifact... Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1919/artifact/art...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files. Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
linaro-toolchain@lists.linaro.org
-
Ijaz, Abdul B -
Maxim Kuvyrkov