Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] branch omair/release/16.0.0 updated (a0f5cfaf8 -> 72e8032b6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch omair/release/16.0.0 in repository toolchain/jenkins-scripts. discards a0f5cfaf8 Set COMPILER_RT_BUILD_GWP_ASAN=OFF new 72e8032b6 Set COMPILER_RT_BUILD_GWP_ASAN=OFF This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (a0f5cfaf8) \ N -- N -- N refs/heads/omair/release/16.0.0 (72e8032b6) 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.

4 months

[toolchain/jenkins-scripts] branch omair/release/14.0.0 updated (34220798e -> f7dc7afb0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch omair/release/14.0.0 in repository toolchain/jenkins-scripts. discards 34220798e Add compatibility version to second stage too new f7dc7afb0 Add compatibility version to second stage too This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (34220798e) \ N -- N -- N refs/heads/omair/release/14.0.0 (f7dc7afb0) 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.

4 months

[toolchain/jenkins-scripts] branch omair/release/13.0.0 updated (595d403a9 -> 52e69d059)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch omair/release/13.0.0 in repository toolchain/jenkins-scripts. discards 595d403a9 tcwg-llvm-release.sh: Fix compiler typo new 52e69d059 tcwg-llvm-release.sh: Fix compiler typo This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (595d403a9) \ N -- N -- N refs/heads/omair/release/13.0.0 (52e69d059) 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.

4 months

[toolchain/jenkins-scripts] branch new-flaky updated (e17676c07 -> dc0b2d431)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch new-flaky in repository toolchain/jenkins-scripts. discards e17676c07 [WIP] Precommit support new dc0b2d431 [WIP] Precommit support This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (e17676c07) \ N -- N -- N refs/heads/new-flaky (dc0b2d431) 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.

4 months

[toolchain/jenkins-scripts] branch maxim updated (148a356dd -> 444754f14)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch maxim in repository toolchain/jenkins-scripts. discards 148a356dd tcwg_kernel-bisect.sh: Better handle regressions in merges commits discards e0b5b8901 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests new 444754f14 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (148a356dd) \ N -- N -- N refs/heads/maxim (444754f14) 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: tcwg_kernel-bisect.sh | 403 -------------------------------------------------- 1 file changed, 403 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months

[toolchain/jenkins-scripts] branch master updated (49dc24809 -> 8437865af)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch master in repository toolchain/jenkins-scripts. discards 49dc24809 round-robin-notify.sh: Replace "progression" with "improvement" discards bc3441401 Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent" adds 8437865af Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent" This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (49dc24809) \ N -- N -- N refs/heads/master (8437865af) 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 | 650 ------------- round-robin-bisect.sh | 735 -------------- round-robin-notify.sh | 2429 ----------------------------------------------- 3 files changed, 3814 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.

4 months

[toolchain/jenkins-scripts] branch luporl/release/16.0.0 updated (081a348cd -> 54310ef1f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch luporl/release/16.0.0 in repository toolchain/jenkins-scripts. discards 081a348cd tcwg-llvm-release.sh: Use gzip on ARMv7 new 54310ef1f tcwg-llvm-release.sh: Use gzip on ARMv7 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (081a348cd) \ N -- N -- N refs/heads/luporl/release/16.0.0 (54310ef1f) 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.

4 months

[toolchain/jenkins-scripts] branch laurent updated (33a4338f5 -> 58857830c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch laurent in repository toolchain/jenkins-scripts. discards 33a4338f5 WIP new 58857830c WIP This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (33a4338f5) \ N -- N -- N refs/heads/laurent (58857830c) 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.

4 months

[toolchain/jenkins-scripts] branch diana/release/python2%wip updated (ec9f93517 -> 509e73933)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch diana/release/python2%wip in repository toolchain/jenkins-scripts. discards ec9f93517 Install python2 so we can build llvm 11.1.0-rc2 etc new 509e73933 Install python2 so we can build llvm 11.1.0-rc2 etc This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (ec9f93517) \ N -- N -- N refs/heads/diana/release/python2%wip (509e73933) 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.

4 months

[toolchain/jenkins-scripts] branch diana/release/15.0.0 updated (f22997bcf -> 34c6470ff)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch diana/release/15.0.0 in repository toolchain/jenkins-scripts. discards f22997bcf Disable running lldb tests new 34c6470ff Disable running lldb tests This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (f22997bcf) \ N -- N -- N refs/heads/diana/release/15.0.0 (34c6470ff) 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.

4 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024