Hello Linaro Toolchain Working Group,
Please connect your new bots to the staging first and make them reliably green there:
linaro-aarch64-flang-debug linaro-aarch64-flang-latest-clang linaro-aarch64-flang-latest-gcc
clang-cmake-aarch64-full is red for a month. https://lab.llvm.org/buildbot/#/builders/7?numbuilds=700
Could you move linaro-aarch64-full to the staging and make it green again, please?
Please let me know if I could help or you have questions.
Thanks
Galina
On Mar 13, 2021, at 11:03 AM, Galina Kistanova gkistanova@gmail.com wrote:
Hello Linaro Toolchain Working Group,
Hi Galina,
Please connect your new bots to the staging first and make them reliably green there:
linaro-aarch64-flang-debug linaro-aarch64-flang-latest-clang linaro-aarch64-flang-latest-gcc
We had these reliably green when connected to our internal testing buildmaster, but it's a good idea to let them cook for a week or two in upstream staging buildmaster anyway.
clang-cmake-aarch64-full is red for a month. https://lab.llvm.org/buildbot/#/builders/7?numbuilds=700
Could you move linaro-aarch64-full to the staging and make it green again, please?
Clang-cmake-aarch64-full is one of our most important (if not the most important) bot, and we pay constant attention to it. It has been red for a month, but only due to various patches actually breaking bits and pieces of LLVM for AArch64. We ping patch authors promptly, and give them a few days to correct the problems they caused before reverting their patches ourselves.
At the moment the last and only failure in clang-cmake-aarch64-full is FAIL: AddressSanitizer-aarch64-linux-dynamic::fgets_fputs.cpp which we are investigating. If we can't get it fixed and the bot green by Wednesday, we'll move it to staging. Sounds good?
Please let me know if I could help or you have questions.
Regards,
-- Maxim Kuvyrkov https://www.linaro.org
Thanks, Maxim!
If we can't get it fixed and the bot green by Wednesday, we'll move it to
staging. Sounds good?
This sounds good. I know how frustrating it could be to follow a chain of bugs and issues screening each other.
Though, longer a builder remains red - less trust developers have to its reliability - less attention they pay - more problems gets introduced - longer the builder in question remains broken. This is a catch 22, and this chain of events must be stopped somewhere. If this is important to you builder, maybe it is possible to add more workers to it to reduce the blame lists? I assume it couldn't be built faster. Or assign someone to check the failures, bisect, and escalate quickly? The first option seems more feasible, I guess...
Please let me know if I could help.
Galina
On Mon, Mar 15, 2021 at 3:07 AM Maxim Kuvyrkov maxim.kuvyrkov@linaro.org wrote:
On Mar 13, 2021, at 11:03 AM, Galina Kistanova gkistanova@gmail.com
wrote:
Hello Linaro Toolchain Working Group,
Hi Galina,
Please connect your new bots to the staging first and make them reliably green there:
linaro-aarch64-flang-debug linaro-aarch64-flang-latest-clang linaro-aarch64-flang-latest-gcc
We had these reliably green when connected to our internal testing buildmaster, but it's a good idea to let them cook for a week or two in upstream staging buildmaster anyway.
clang-cmake-aarch64-full is red for a month. https://lab.llvm.org/buildbot/#/builders/7?numbuilds=700
Could you move linaro-aarch64-full to the staging and make it green
again,
please?
Clang-cmake-aarch64-full is one of our most important (if not the most important) bot, and we pay constant attention to it. It has been red for a month, but only due to various patches actually breaking bits and pieces of LLVM for AArch64. We ping patch authors promptly, and give them a few days to correct the problems they caused before reverting their patches ourselves.
At the moment the last and only failure in clang-cmake-aarch64-full is FAIL: AddressSanitizer-aarch64-linux-dynamic::fgets_fputs.cpp which we are investigating. If we can't get it fixed and the bot green by Wednesday, we'll move it to staging. Sounds good?
Please let me know if I could help or you have questions.
Regards,
-- Maxim Kuvyrkov https://www.linaro.org
Hi
On Tue, 16 Mar 2021 at 04:07, Galina Kistanova gkistanova@gmail.com wrote:
Thanks, Maxim!
If we can't get it fixed and the bot green by Wednesday, we'll move it to
staging. Sounds good?
This sounds good. I know how frustrating it could be to follow a chain of bugs and issues screening each other.
Though, longer a builder remains red - less trust developers have to its reliability - less attention they pay - more problems gets introduced - longer the builder in question remains broken. This is a catch 22, and this chain of events must be stopped somewhere. If this is important to you builder, maybe it is possible to add more workers to it to reduce the blame lists? I assume it couldn't be built faster. Or assign someone to check the failures, bisect, and escalate quickly? The first option seems more feasible, I guess...
Please let me know if I could help.
I've disabled the test for AArch64 while we are investigating the real issue with it, the bot should be green again in 2hrs... Hopefully!
Yvan
Galina
On Mon, Mar 15, 2021 at 3:07 AM Maxim Kuvyrkov maxim.kuvyrkov@linaro.org wrote:
On Mar 13, 2021, at 11:03 AM, Galina Kistanova gkistanova@gmail.com
wrote:
Hello Linaro Toolchain Working Group,
Hi Galina,
Please connect your new bots to the staging first and make them
reliably
green there:
linaro-aarch64-flang-debug linaro-aarch64-flang-latest-clang linaro-aarch64-flang-latest-gcc
We had these reliably green when connected to our internal testing buildmaster, but it's a good idea to let them cook for a week or two in upstream staging buildmaster anyway.
clang-cmake-aarch64-full is red for a month. https://lab.llvm.org/buildbot/#/builders/7?numbuilds=700
Could you move linaro-aarch64-full to the staging and make it green
again,
please?
Clang-cmake-aarch64-full is one of our most important (if not the most important) bot, and we pay constant attention to it. It has been red
for a
month, but only due to various patches actually breaking bits and pieces
of
LLVM for AArch64. We ping patch authors promptly, and give them a few
days
to correct the problems they caused before reverting their patches ourselves.
At the moment the last and only failure in clang-cmake-aarch64-full is FAIL: AddressSanitizer-aarch64-linux-dynamic::fgets_fputs.cpp which we are investigating. If we can't get it fixed and the bot green
by
Wednesday, we'll move it to staging. Sounds good?
Please let me know if I could help or you have questions.
Regards,
-- Maxim Kuvyrkov https://www.linaro.org
linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
On Mar 16, 2021, at 6:06 AM, Galina Kistanova gkistanova@gmail.com wrote:
Thanks, Maxim!
If we can't get it fixed and the bot green by Wednesday, we'll move it to staging. Sounds good?
This sounds good. I know how frustrating it could be to follow a chain of bugs and issues screening each other.
Though, longer a builder remains red - less trust developers have to its reliability - less attention they pay - more problems gets introduced - longer the builder in question remains broken. This is a catch 22, and this chain of events must be stopped somewhere. If this is important to you builder, maybe it is possible to add more workers to it to reduce the blame lists? I assume it couldn't be built faster. Or assign someone to check the failures, bisect, and escalate quickly? The first option seems more feasible, I guess...
Hi Galina,
We are expecting new more powerful machines for our buildbots in few weeks time. Builds should become faster by around 50%.
-- Maxim Kuvyrkov https://www.linaro.org
Please let me know if I could help.
Galina
On Mon, Mar 15, 2021 at 3:07 AM Maxim Kuvyrkov maxim.kuvyrkov@linaro.org wrote:
On Mar 13, 2021, at 11:03 AM, Galina Kistanova gkistanova@gmail.com wrote:
Hello Linaro Toolchain Working Group,
Hi Galina,
Please connect your new bots to the staging first and make them reliably green there:
linaro-aarch64-flang-debug linaro-aarch64-flang-latest-clang linaro-aarch64-flang-latest-gcc
We had these reliably green when connected to our internal testing buildmaster, but it's a good idea to let them cook for a week or two in upstream staging buildmaster anyway.
clang-cmake-aarch64-full is red for a month. https://lab.llvm.org/buildbot/#/builders/7?numbuilds=700
Could you move linaro-aarch64-full to the staging and make it green again, please?
Clang-cmake-aarch64-full is one of our most important (if not the most important) bot, and we pay constant attention to it. It has been red for a month, but only due to various patches actually breaking bits and pieces of LLVM for AArch64. We ping patch authors promptly, and give them a few days to correct the problems they caused before reverting their patches ourselves.
At the moment the last and only failure in clang-cmake-aarch64-full is FAIL: AddressSanitizer-aarch64-linux-dynamic::fgets_fputs.cpp which we are investigating. If we can't get it fixed and the bot green by Wednesday, we'll move it to staging. Sounds good?
Please let me know if I could help or you have questions.
Regards,
-- Maxim Kuvyrkov https://www.linaro.org
linaro-toolchain@lists.linaro.org
-
Galina Kistanova -
Maxim Kuvyrkov -
Yvan Roux