Should have been reported as follows.
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In tcwg_flang_test/main-aarch64-O0-debug, after:
| commit fujitsu_testsuite#a0e269d5d
| Author: KAWASHIMA Takahiro
| Date: Tue Nov 1
Should have been reported as follows.
Some regressions and some improvements after this commit in fujitsu
testsuite.
Regards,
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla
Should have been reported as below.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please
find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after:
| commit llvmorg-20-init-13009-g3f594741cf8e
| Author: Peter Klausler
| Date: Th
It should have been reported as below. This is after this commit in
llvm-test-suite.
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after:
| commit llvmorg-19.1.1-16-g9f743a87e
This report should have been as below.
We are checking what went wrong on our side.
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after:
| commit llvmorg-20-init-12914-g5d38e6e
Yes, I reported to Christophe yesterday, he confirmed this comes from his
linker commit and he's looking at it.
Laurent
On Thu, 12 Sept 2024 at 04:38, Maxim Kuvyrkov
wrote:
> Hi Mark,
>
> I believe this was caused by Christophe's binutils patch, which has now
> been fixed.
>
> Christophe, please
Thiago,
This is a false alarm.. Sorry about that.
This has nothing to do with gdb, it complains about a spec2006
benchmark. not even a gcc testsuite issue.
It is just a benchmark instability build issue.
tonto benchmark was unstable due to an issue when parallelizing make,
with remote compil