Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/12/45612/2 updated (f3785dfda -> 996c00e3c)

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/45612/2 in repository toolchain/jenkins-scripts. discards f3785dfda jenkins-helpers.sh (git_annex_upload): Fix corner-case adds 996c00e3c jenkins-helpers.sh (git_annex_upload): Fix corner-case 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 (f3785dfda) \ N -- N -- N refs/changes/12/45612/2 (996c00e3c) 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/45612/1 updated (58278bcd6 -> c0fd43d42)

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/45612/1 in repository toolchain/jenkins-scripts. discards 58278bcd6 jenkins-helpers.sh (git_annex_upload): Fix corner-case new c0fd43d42 jenkins-helpers.sh (git_annex_upload): Fix corner-case 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 (58278bcd6) \ N -- N -- N refs/changes/12/45612/1 (c0fd43d42) 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/45512/1 updated (f665b453e -> 97d17c9ea)

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/45512/1 in repository toolchain/jenkins-scripts. discards f665b453e round-robin-bisect.sh: Remove unneeded override discards a0f52b969 round-robin-bisect.sh: Improve trigger for subsequent builds adds 97d17c9ea round-robin-bisect.sh: Improve trigger for subsequent 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 (f665b453e) \ N -- N -- N refs/changes/12/45512/1 (97d17c9ea) 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 | 413 ------------- round-robin-bisect.sh | 655 -------------------- round-robin-notify.sh | 1572 ----------------------------------------------- 3 files changed, 2640 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/12/45412/1 updated (4e20ed1dc -> a49b4916e)

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/45412/1 in repository toolchain/jenkins-scripts. discards 4e20ed1dc Revert "Revert "Revert "tcwg-update-llvmbot-containers.sh: Ad [...] adds a49b4916e Revert "Revert "Revert "tcwg-update-llvmbot-containers.sh: Ad [...] 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 (4e20ed1dc) \ N -- N -- N refs/changes/12/45412/1 (a49b4916e) 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/44712/8 updated (b0681edc6 -> 2011e9e7a)

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/44712/8 in repository toolchain/jenkins-scripts. discards b0681edc6 tcwg_bmk-build.sh: Fix place where to store the bmk results adds 2011e9e7a tcwg_bmk-build.sh: Fix place where to store the bmk 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 (b0681edc6) \ N -- N -- N refs/changes/12/44712/8 (2011e9e7a) 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/44712/7 updated (45762acd5 -> 9113950fe)

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/44712/7 in repository toolchain/jenkins-scripts. discards 45762acd5 tcwg_bmk-build.sh: Fix place where to store the bmk results new 9113950fe tcwg_bmk-build.sh: Fix place where to store the bmk 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 (45762acd5) \ N -- N -- N refs/changes/12/44712/7 (9113950fe) 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/44712/6 updated (0dd96d313 -> 5eb4ee1c9)

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/44712/6 in repository toolchain/jenkins-scripts. discards 0dd96d313 tcwg_bmk-build.sh: Fix place where to store the bmk results new 5eb4ee1c9 tcwg_bmk-build.sh: Fix place where to store the bmk 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 (0dd96d313) \ N -- N -- N refs/changes/12/44712/6 (5eb4ee1c9) 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/44712/5 updated (177b95122 -> 4d67c6cf3)

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/44712/5 in repository toolchain/jenkins-scripts. discards 177b95122 tcwg_bmk-build.sh: Fix place where to store the bmk results new 4d67c6cf3 tcwg_bmk-build.sh: Fix place where to store the bmk 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 (177b95122) \ N -- N -- N refs/changes/12/44712/5 (4d67c6cf3) 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/44712/4 updated (fe3b7f351 -> 838aeb712)

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/44712/4 in repository toolchain/jenkins-scripts. discards fe3b7f351 tcwg_bmk-build.sh: Fix place where to store the bmk results new 838aeb712 tcwg_bmk-build.sh: Fix place where to store the bmk 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 (fe3b7f351) \ N -- N -- N refs/changes/12/44712/4 (838aeb712) 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/44712/3 updated (2c54b6629 -> af0a4b50c)

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/44712/3 in repository toolchain/jenkins-scripts. discards 2c54b6629 tcwg_bmk-build.sh: Fix place where to store the bmk results new af0a4b50c tcwg_bmk-build.sh: Fix place where to store the bmk 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 (2c54b6629) \ N -- N -- N refs/changes/12/44712/3 (af0a4b50c) 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