Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/62/43362/2 updated (539ced58f -> 6605cc195)

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/62/43362/2 in repository toolchain/jenkins-scripts. discards 539ced58f tcwg-cleanup-stale-containers.sh: Remove old stopped containers adds 6605cc195 tcwg-cleanup-stale-containers.sh: Remove old stopped containers 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 (539ced58f) \ N -- N -- N refs/changes/62/43362/2 (6605cc195) 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/62/43362/1 updated (37bb5b1f4 -> 4941b5ec5)

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/62/43362/1 in repository toolchain/jenkins-scripts. discards 37bb5b1f4 tcwg-cleanup-stale-containers.sh: Remove old stopped containers new 4941b5ec5 tcwg-cleanup-stale-containers.sh: Remove old stopped containers 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 (37bb5b1f4) \ N -- N -- N refs/changes/62/43362/1 (4941b5ec5) 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/62/42262/3 updated (99cede4a3 -> 338fa75be)

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/62/42262/3 in repository toolchain/jenkins-scripts. discards 99cede4a3 tcwg_bmk-build.sh: build llvm for flang for some projects adds 338fa75be tcwg_bmk-build.sh: build llvm for flang for some 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 (99cede4a3) \ N -- N -- N refs/changes/62/42262/3 (338fa75be) 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/62/42262/2 updated (0c5d77892 -> 249776dc1)

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/62/42262/2 in repository toolchain/jenkins-scripts. discards 0c5d77892 tcwg_bmk-build.sh: build llvm for flang for some projects adds 249776dc1 tcwg_bmk-build.sh: build llvm for flang for some 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 (0c5d77892) \ N -- N -- N refs/changes/62/42262/2 (249776dc1) 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/62/42262/1 updated (5401da778 -> f402ab18c)

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/62/42262/1 in repository toolchain/jenkins-scripts. discards 5401da778 tcwg_bmk-build.sh: build llvm for flang for some projects new f402ab18c tcwg_bmk-build.sh: build llvm for flang for some 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 (5401da778) \ N -- N -- N refs/changes/62/42262/1 (f402ab18c) 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/62/42162/1 updated (ae0c89f2f -> 38b6cf928)

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/62/42162/1 in repository toolchain/jenkins-scripts. discards ae0c89f2f build_llvm_package.bat: Use absolute path for builtins lib adds 38b6cf928 build_llvm_package.bat: Use absolute path for builtins lib 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 (ae0c89f2f) \ N -- N -- N refs/changes/62/42162/1 (38b6cf928) 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/62/42062/1 updated (3fa17655e -> f36c42f80)

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/62/42062/1 in repository toolchain/jenkins-scripts. discards 3fa17655e round-robin.sh: Small fix for dashboard adds f36c42f80 round-robin.sh: Small fix for dashboard 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 (3fa17655e) \ N -- N -- N refs/changes/62/42062/1 (f36c42f80) 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/62/41962/3 updated (44fbfe2c8 -> 493aba66d)

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/62/41962/3 in repository toolchain/jenkins-scripts. discards 44fbfe2c8 round-robin.sh, dashboard.sh: factorize all dashboard routines adds 493aba66d round-robin.sh, dashboard.sh: factorize all dashboard routines 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 (44fbfe2c8) \ N -- N -- N refs/changes/62/41962/3 (493aba66d) 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/62/41962/2 updated (eeac6dd5a -> 2b228cf74)

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/62/41962/2 in repository toolchain/jenkins-scripts. discards eeac6dd5a round-robin.sh, dashboard.sh: factorize all dashboard routines adds 2b228cf74 round-robin.sh, dashboard.sh: factorize all dashboard routines 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 (eeac6dd5a) \ N -- N -- N refs/changes/62/41962/2 (2b228cf74) 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/62/41962/1 updated (56feba5d8 -> 38541f712)

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/62/41962/1 in repository toolchain/jenkins-scripts. discards 56feba5d8 round-robin.sh, dashboard.sh: factorize all dashboard routines new 38541f712 round-robin.sh, dashboard.sh: factorize all dashboard routines 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 (56feba5d8) \ N -- N -- N refs/changes/62/41962/1 (38541f712) 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