Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/31/37931/5 updated (a81976c65 -> bb7c9cc81)

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/31/37931/5 in repository toolchain/jenkins-scripts. discards a81976c65 tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] adds bb7c9cc81 tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] 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 (a81976c65) \ N -- N -- N refs/changes/31/37931/5 (bb7c9cc81) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/37931/4 updated (424cf6cbd -> bb05a3dbf)

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/31/37931/4 in repository toolchain/jenkins-scripts. discards 424cf6cbd tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] new bb05a3dbf tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] 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 (424cf6cbd) \ N -- N -- N refs/changes/31/37931/4 (bb05a3dbf) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/37931/3 updated (95e045359 -> 83c4c1a25)

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/31/37931/3 in repository toolchain/jenkins-scripts. discards 95e045359 tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] new 83c4c1a25 tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] 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 (95e045359) \ N -- N -- N refs/changes/31/37931/3 (83c4c1a25) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/37931/2 updated (5fb922800 -> 1ffa098ff)

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/31/37931/2 in repository toolchain/jenkins-scripts. discards 5fb922800 tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] new 1ffa098ff tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] 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 (5fb922800) \ N -- N -- N refs/changes/31/37931/2 (1ffa098ff) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/37931/1 updated (ca5fa43a8 -> e093ecda0)

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/31/37931/1 in repository toolchain/jenkins-scripts. discards ca5fa43a8 tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] new e093ecda0 tcwg-update-llvmbot-containers.sh: Move libcxx buildkite bots [...] 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 (ca5fa43a8) \ N -- N -- N refs/changes/31/37931/1 (e093ecda0) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/37231/2 updated (70e7ffd0d -> 09375b661)

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/31/37231/2 in repository toolchain/jenkins-scripts. discards 70e7ffd0d round-robin.sh: Update to follow ABE's new $builddir naming adds 09375b661 round-robin.sh: Update to follow ABE's new $builddir naming 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 (70e7ffd0d) \ N -- N -- N refs/changes/31/37231/2 (09375b661) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/37231/1 updated (b3b63c14c -> a22c321cc)

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/31/37231/1 in repository toolchain/jenkins-scripts. discards b3b63c14c round-robin.sh: Update to follow ABE's new $builddir naming adds a22c321cc round-robin.sh: Update to follow ABE's new $builddir naming 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 (b3b63c14c) \ N -- N -- N refs/changes/31/37231/1 (a22c321cc) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/35831/3 updated (9c4410c50 -> 0dfe8c027)

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/31/35831/3 in repository toolchain/jenkins-scripts. discards 9c4410c50 tcwg_bmk-build.sh: Workaround missing benchmarking results adds 0dfe8c027 tcwg_bmk-build.sh: Workaround missing benchmarking results 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 (9c4410c50) \ N -- N -- N refs/changes/31/35831/3 (0dfe8c027) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/35831/2 updated (6eb961998 -> e2ef1a07d)

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/31/35831/2 in repository toolchain/jenkins-scripts. discards 6eb961998 tcwg_bmk-build.sh: Workaround missing benchmarking results new e2ef1a07d tcwg_bmk-build.sh: Workaround missing benchmarking results 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 (6eb961998) \ N -- N -- N refs/changes/31/35831/2 (e2ef1a07d) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/31/35831/1 updated (3b116e04a -> 27fd57aa7)

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/31/35831/1 in repository toolchain/jenkins-scripts. discards 3b116e04a tcwg_bmk-build.sh: Workaround missing benchmarking results new 27fd57aa7 tcwg_bmk-build.sh: Workaround missing benchmarking results 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 (3b116e04a) \ N -- N -- N refs/changes/31/35831/1 (27fd57aa7) 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, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024