Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/52/30052/3 updated (0f3ca0a26 -> c7e601721)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/52/30052/3 in repository toolchain/jenkins-scripts. discards 0f3ca0a26 tcwg-benchmark-results.sh: Rework and cleanup. adds c7e601721 tcwg-benchmark-results.sh: Rework and cleanup. This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0f3ca0a26) \ N -- N -- N refs/changes/52/30052/3 (c7e601721) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30052/2 updated (e54e5eb47 -> 8d7946284)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/52/30052/2 in repository toolchain/jenkins-scripts. discards e54e5eb47 tcwg-benchmark-results.sh: Rework and cleanup. adds 8d7946284 tcwg-benchmark-results.sh: Rework and cleanup. This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e54e5eb47) \ N -- N -- N refs/changes/52/30052/2 (8d7946284) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30052/1 updated (4d50564b1 -> a8eb1a35e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/52/30052/1 in repository toolchain/jenkins-scripts. discards 4d50564b1 tcwg-benchmark-results.sh: Rework and cleanup. adds a8eb1a35e tcwg-benchmark-results.sh: Rework and cleanup. This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (4d50564b1) \ N -- N -- N refs/changes/52/30052/1 (a8eb1a35e) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[gcc] branch master updated (c9d61cff97b -> 6c22fe418cf)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from c9d61cff97b libstdc++: Remove duplicate include header from ranges_algobase.h new 5fc9c40fea2 libstdc++: Fix std::vector<bool> for -std=gnu++14 -fconcept [...] new 6c22fe418cf libstdc++: Fix <ostream> and <istream> for -std=gnu++14 -fc [...] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: libstdc++-v3/include/bits/stl_bvector.h | 2 +- libstdc++-v3/include/std/istream | 2 +- libstdc++-v3/include/std/ostream | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/29452/2 updated (794126987 -> cfc275515)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/52/29452/2 in repository toolchain/jenkins-scripts. discards 794126987 tcwg-rsync-dir.sh: Use "FAILED" instead of "FAIL" adds cfc275515 tcwg-rsync-dir.sh: Use "FAILED" instead of "FAIL" This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (794126987) \ N -- N -- N refs/changes/52/29452/2 (cfc275515) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/29452/1 updated (97fce7ae1 -> 6fea5241e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/52/29452/1 in repository toolchain/jenkins-scripts. discards 97fce7ae1 tcwg-rsync-dir.sh: Use "FAILED" instead of "FAIL" new 6fea5241e tcwg-rsync-dir.sh: Use "FAILED" instead of "FAIL" This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (97fce7ae1) \ N -- N -- N refs/changes/52/29452/1 (6fea5241e) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/29352/2 updated (5c0fc7c61 -> 4be80ada2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/52/29352/2 in repository toolchain/jenkins-scripts. discards 5c0fc7c61 tcwg_kernel-bisect.sh: Make sure artifacts contain "bad" logs discards 828a6b581 tcwg_kernel-bisect.sh: Tidy up artifacts discards 85425e8c4 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml discards e333a4e3d tcwg-update-llvmbot-containers.sh: New job script adds 4be80ada2 tcwg-update-llvmbot-containers.sh: New job script This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (5c0fc7c61) \ N -- N -- N refs/changes/52/29352/2 (4be80ada2) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: tcwg_kernel-bisect.sh | 244 -------------------------------------------------- 1 file changed, 244 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/29352/1 updated (ba317a795 -> ce794b80b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/52/29352/1 in repository toolchain/jenkins-scripts. discards ba317a795 tcwg_kernel-bisect.sh: Make sure artifacts contain "bad" logs discards 2ac388259 tcwg_kernel-bisect.sh: Tidy up artifacts discards 3cb94b357 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml discards a5c2d2aa0 tcwg_kernel-bisect.sh: Send emails only on successful bisects. discards 148291018 tcwg-update-llvmbot-containers.sh: New job script adds ce794b80b tcwg-update-llvmbot-containers.sh: New job script This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (ba317a795) \ N -- N -- N refs/changes/52/29352/1 (ce794b80b) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: tcwg_kernel-bisect.sh | 244 -------------------------------------------------- 1 file changed, 244 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/47251/1 updated (8e76ebdcb -> 39286005c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/51/47251/1 in repository toolchain/jenkins-scripts. discards 8e76ebdcb tcwg-config.sh: Fixed configs for tcwg_kernel/tcwg_aosp projects adds 39286005c tcwg-config.sh: Fixed configs for tcwg_kernel/tcwg_aosp projects This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8e76ebdcb) \ N -- N -- N refs/changes/51/47251/1 (39286005c) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/46951/8 updated (a09866093 -> 8f67fb2be)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/51/46951/8 in repository toolchain/jenkins-scripts. discards a09866093 round-robin-bisect.sh,round-robin-notify.sh: current project [...] discards 505cfb47a tcwg_gnu-build.sh (rr[major]): Bump adds 8f67fb2be tcwg_gnu-build.sh (rr[major]): Bump This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a09866093) \ N -- N -- N refs/changes/51/46951/8 (8f67fb2be) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. No new revisions were added by this update. Summary of changes: round-robin-baseline.sh | 624 ------------ round-robin-bisect.sh | 680 ------------- round-robin-notify.sh | 2416 ----------------------------------------------- 3 files changed, 3720 deletions(-) delete mode 100755 round-robin-baseline.sh delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024