Hi Maxim,
> On 15 Jan 2024, at 09:51, Maxim Kuvyrkov wrote:
> [Apologies for late reply, your email got caught in moderation queue.]
ah…
> Do you still need help in reproducing the build?
No; I believe that it was figured out with some help on IRC and the issue fixed.
Thanks for checking.
>
Hi Ian,
[Apologies for late reply, your email got caught in moderation queue.]
Do you still need help in reproducing the build?
On our side we are working to include configure/make lines into reports to
simplify reproduction.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Oct 22
Hi Lehua,
[Apologies for late reply, your email got caught in moderation queue.]
Do you still need help in reproducing the build?
On our side we are working to include configure/make lines into reports to
simplify reproduction.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov
Hi Rainer,
[Apologies for late reply, your reply got caught in moderation queue.]
We have considered automatically regenerating autoconf, etc. files, but have
decided against that, at least for now. My logic is that developers should
receive feedback for the verbatim patches they posted, not f
At 08:36 + on Friday, 2024-01-12, wrote ci_not...@linaro.org：
> 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 pro
Hi, Christophe
Yes, I assumed that it was a false error, but I was not certain how to
acknowledge that in the CI infrastructure and reporting system that Linaro
has deployed.
Thanks, David
On Tue, Jan 9, 2024 at 9:19 AM Christophe Lyon
wrote:
> Hi David,
>
> As you have probably guessed, this
> -Original Message-
> From: ci_not...@linaro.org
> Sent: Friday, December 29, 2023 7:40 AM
> To: Andrew Pinski (QUIC)
> Cc: gcc-regress...@gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: FAIL: 1 regressions
> on arm
>
> Dear contributor, our automatic CI has detected p
ci_not...@linaro.org writes:
> 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 favo
Hi,
I received an error reported by CI for my patchs, I would like to ask
how I have to reproduce it locally? I looked at the logs and didn't find
the way how it compiles. Thanks in advance.
On 2023/11/8 16:59, ci_not...@linaro.org wrote:
Dear contributor, our automatic CI has detected probl
I will look at this. I did not show up in my tests though
and seems unrelated to the change (maybe surfaced because of it)
Martin
Am Montag, dem 06.11.2023 um 08:48 + schrieb Jiang, Haochen:
> It also caused x86 backend regression. Please help verify it.
>
> Thx,
> Haochen
>
> > -Ori
On Tue, Oct 24, 2023 at 10:24 AM Christophe Lyon
wrote:
>
> Sorry, there was a temporary breakage in our CI scripts, you can
> ignore this bogus report.
>
Thank you for letting me know!
> On Tue, 24 Oct 2023 at 18:25, wrote:
> >
> > Dear contributor, our automatic CI has detected problems relat
Hi
So, I have a ci fail email, and it seems likely to be a valid complaint -
but the reproduce instructions do not work on my platform (bash is not new
enough)
and also do not work on cfarm186 (../jenkins-scripts/jenkins-helpers.sh: line
1762: ts: command not found)
For the record, the patch
On 02/10/2023 18:12, Wilco Dijkstra wrote:
Hi Ramana,
I used --target=arm-none-linux-gnueabihf --host=arm-none-linux-gnueabihf
--build=arm-none-linux-gnueabihf --with-float=hard. However it seems that the
default armhf settings are incorrect. I shouldn't need the --with-float=hard
since
tha
13 matches
Mail list logo
