Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/12/41512/1 updated (ffcf4a38a -> 6b9c1cc4f)

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/12/41512/1 in repository toolchain/jenkins-scripts. discards ffcf4a38a LLDB Arm buildbot temporarily disabled adds 6b9c1cc4f LLDB Arm buildbot temporarily disabled 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 (ffcf4a38a) \ N -- N -- N refs/changes/12/41512/1 (6b9c1cc4f) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/39612/2 updated (d77a7103d -> 0eb4db505)

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/12/39612/2 in repository toolchain/jenkins-scripts. discards d77a7103d build_llvm_package.bat: Support doing test builds adds 0eb4db505 build_llvm_package.bat: Support doing test builds 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 (d77a7103d) \ N -- N -- N refs/changes/12/39612/2 (0eb4db505) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/39612/1 updated (e342c6ccb -> 22d3cccca)

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/12/39612/1 in repository toolchain/jenkins-scripts. discards e342c6ccb build_llvm_package.bat: Support doing test builds new 22d3cccca build_llvm_package.bat: Support doing test builds 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 (e342c6ccb) \ N -- N -- N refs/changes/12/39612/1 (22d3cccca) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/39312/2 updated (ec981d37f -> 3822f9bb5)

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/12/39312/2 in repository toolchain/jenkins-scripts. discards ec981d37f tcwg-update-llvmbot-containers.sh: Move buildkite bots to Jade 04 adds 3822f9bb5 tcwg-update-llvmbot-containers.sh: Move buildkite bots to Jade 04 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 (ec981d37f) \ N -- N -- N refs/changes/12/39312/2 (3822f9bb5) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/39312/1 updated (49aea7da3 -> 9457069df)

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/12/39312/1 in repository toolchain/jenkins-scripts. discards 49aea7da3 tcwg-update-llvmbot-containers.sh: Move buildkite bots to Jade 04 adds 9457069df tcwg-update-llvmbot-containers.sh: Move buildkite bots to Jade 04 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 (49aea7da3) \ N -- N -- N refs/changes/12/39312/1 (9457069df) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/34312/5 updated (7bc655b54 -> 209678ef3)

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/12/34312/5 in repository toolchain/jenkins-scripts. discards 7bc655b54 tcwg_gnu-build.sh: Fix check_binutils comparison adds 209678ef3 tcwg_gnu-build.sh: Fix check_binutils comparison 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 (7bc655b54) \ N -- N -- N refs/changes/12/34312/5 (209678ef3) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/34312/4 updated (8bf42416b -> dba1be8b2)

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/12/34312/4 in repository toolchain/jenkins-scripts. discards 8bf42416b tcwg_gnu-build.sh: Fix check_binutils comparison new dba1be8b2 tcwg_gnu-build.sh: Fix check_binutils comparison 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 (8bf42416b) \ N -- N -- N refs/changes/12/34312/4 (dba1be8b2) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/34312/3 updated (8cd1cbf13 -> 2e0615546)

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/12/34312/3 in repository toolchain/jenkins-scripts. discards 8cd1cbf13 tcwg_gnu-build.sh: Fix check_binutils comparison new 2e0615546 tcwg_gnu-build.sh: Fix check_binutils comparison 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 (8cd1cbf13) \ N -- N -- N refs/changes/12/34312/3 (2e0615546) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/34312/2 updated (977025fc1 -> 009c630f7)

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/12/34312/2 in repository toolchain/jenkins-scripts. discards 977025fc1 tcwg_gnu-build.sh: Fix check_binutils comparison new 009c630f7 tcwg_gnu-build.sh: Fix check_binutils comparison 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 (977025fc1) \ N -- N -- N refs/changes/12/34312/2 (009c630f7) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/34312/1 updated (66adf4af9 -> 71fad9948)

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/12/34312/1 in repository toolchain/jenkins-scripts. discards 66adf4af9 tcwg_gnu-build.sh: Fix check_binutils comparison new 71fad9948 tcwg_gnu-build.sh: Fix check_binutils comparison 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 (66adf4af9) \ N -- N -- N refs/changes/12/34312/1 (71fad9948) 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, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024