Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/66/31666/3 updated (3d6680a22 -> 6d0ac5971)

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/66/31666/3 in repository toolchain/jenkins-scripts. discards 3d6680a22 tcwg_bmk-build.sh: Track code size of top 5 symbols. adds 6d0ac5971 tcwg_bmk-build.sh: Track code size of top 5 symbols. 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 (3d6680a22) \ N -- N -- N refs/changes/66/31666/3 (6d0ac5971) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/31666/2 updated (36b144db4 -> f925351ad)

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/66/31666/2 in repository toolchain/jenkins-scripts. discards 36b144db4 tcwg_bmk-build.sh: Track code size of top 5 symbols. new f925351ad tcwg_bmk-build.sh: Track code size of top 5 symbols. 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 (36b144db4) \ N -- N -- N refs/changes/66/31666/2 (f925351ad) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/31666/1 updated (3d3510c80 -> 490ddd7ea)

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/66/31666/1 in repository toolchain/jenkins-scripts. discards 3d3510c80 tcwg_bmk-build.sh: Track code size of top 5 symbols. adds 490ddd7ea tcwg_bmk-build.sh: Track code size of top 5 symbols. 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 (3d3510c80) \ N -- N -- N refs/changes/66/31666/1 (490ddd7ea) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/30866/1 updated (66a7ba1f7 -> 83c2094e7)

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/66/30866/1 in repository toolchain/jenkins-scripts. discards 66a7ba1f7 round-robin.sh: Build LLVMgold.so plugin in build_llvm() new 83c2094e7 round-robin.sh: Build LLVMgold.so plugin in build_llvm() 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 (66a7ba1f7) \ N -- N -- N refs/changes/66/30866/1 (83c2094e7) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/30666/2 updated (d7f15cdb0 -> 7d0f64976)

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/66/30666/2 in repository toolchain/jenkins-scripts. discards d7f15cdb0 tcwg_kernel-bisect.sh: Match GCC ICEs in the logs discards 04ed7f8fe tcwg_kernel-bisect.sh: Use llvm@ and tcwg-gcc@ groups in emai [...] discards f91cadd37 tcwg-cleanup-stale-containers.sh: Make output easier to understand. adds 7d0f64976 tcwg-cleanup-stale-containers.sh: Make output easier to understand. 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 (d7f15cdb0) \ N -- N -- N refs/changes/66/30666/2 (7d0f64976) 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 | 383 -------------------------------------------------- 1 file changed, 383 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/30666/1 updated (e3adb4754 -> 7441f94fc)

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/66/30666/1 in repository toolchain/jenkins-scripts. discards e3adb4754 tcwg_kernel-bisect.sh: Match GCC ICEs in the logs discards a930c737b round-robin.sh: Workaround re-writes of base-artifacts.git history new 7441f94fc round-robin.sh: Workaround re-writes of base-artifacts.git history 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 (e3adb4754) \ N -- N -- N refs/changes/66/30666/1 (7441f94fc) 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 | 383 -------------------------------------------------- 1 file changed, 383 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/30266/1 updated (622d45406 -> ea0786cf2)

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/66/30266/1 in repository toolchain/jenkins-scripts. discards 622d45406 Revert "[tcwg_gnu] Merge branch 'master' into tcwg_gnu" new ea0786cf2 Revert "[tcwg_gnu] Merge branch 'master' into tcwg_gnu" 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 (622d45406) \ N -- N -- N refs/changes/66/30266/1 (ea0786cf2) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/29866/5 updated (8cef89477 -> b3fc9d7fb)

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/66/29866/5 in repository toolchain/jenkins-scripts. discards 8cef89477 jenkins-helpers.sh: Improve run_step functionality. adds b3fc9d7fb jenkins-helpers.sh: Improve run_step functionality. 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 (8cef89477) \ N -- N -- N refs/changes/66/29866/5 (b3fc9d7fb) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/29866/4 updated (60a6d746d -> fe96bb760)

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/66/29866/4 in repository toolchain/jenkins-scripts. discards 60a6d746d jenkins-helpers.sh: Improve run_step functionality. adds fe96bb760 jenkins-helpers.sh: Improve run_step functionality. 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 (60a6d746d) \ N -- N -- N refs/changes/66/29866/4 (fe96bb760) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/66/29866/3 updated (e093e3d74 -> 981dbede9)

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/66/29866/3 in repository toolchain/jenkins-scripts. discards e093e3d74 jenkins-helpers.sh: Improve run_step functionality. new 981dbede9 jenkins-helpers.sh: Improve run_step functionality. 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 (e093e3d74) \ N -- N -- N refs/changes/66/29866/3 (981dbede9) 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024