Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/33/39933/1 updated (d49d354a4 -> 6a4741e26)

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/33/39933/1 in repository toolchain/jenkins-scripts. discards d49d354a4 tcwg_bmk-build.sh: Adjust workaround for new "console" behavior adds 6a4741e26 tcwg_bmk-build.sh: Adjust workaround for new "console" behavior 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 (d49d354a4) \ N -- N -- N refs/changes/33/39933/1 (6a4741e26) 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/33/39233/1 updated (ff69267fd -> 4e5c5a3af)

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/33/39233/1 in repository toolchain/jenkins-scripts. discards ff69267fd round-robin-bisect.sh: Fix pushes to interesting-commits discards f9df16b38 tcwg_gnu-build.sh: Add type_of_test:check_gcc adds 4e5c5a3af tcwg_gnu-build.sh: Add type_of_test:check_gcc 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 (ff69267fd) \ N -- N -- N refs/changes/33/39233/1 (4e5c5a3af) 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-bisect.sh | 822 -------------------------------------------------- 1 file changed, 822 deletions(-) delete mode 100755 round-robin-bisect.sh -- 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/33/35833/2 updated (b57d48a0a -> 4fe4fc610)

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/33/35833/2 in repository toolchain/jenkins-scripts. discards b57d48a0a round-robin.sh: Fix check_regression adds 4fe4fc610 round-robin.sh: Fix check_regression 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 (b57d48a0a) \ N -- N -- N refs/changes/33/35833/2 (4fe4fc610) 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/33/35833/1 updated (c49cb3286 -> 31307add0)

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/33/35833/1 in repository toolchain/jenkins-scripts. discards c49cb3286 round-robin.sh: Fix check_regression new 31307add0 round-robin.sh: Fix check_regression 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 (c49cb3286) \ N -- N -- N refs/changes/33/35833/1 (31307add0) 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/33/35233/5 updated (6f022a741 -> 5c2c69ef9)

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/33/35233/5 in repository toolchain/jenkins-scripts. discards 6f022a741 tcwg_bmk-build.sh: Always write benchmark results_id file adds 5c2c69ef9 tcwg_bmk-build.sh: Always write benchmark results_id file 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 (6f022a741) \ N -- N -- N refs/changes/33/35233/5 (5c2c69ef9) 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/33/35233/4 updated (5f31212ea -> 36cb6a661)

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/33/35233/4 in repository toolchain/jenkins-scripts. discards 5f31212ea tcwg_bmk-build.sh: Always write benchmark results_id file adds 36cb6a661 tcwg_bmk-build.sh: Always write benchmark results_id file 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 (5f31212ea) \ N -- N -- N refs/changes/33/35233/4 (36cb6a661) 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/33/35233/3 updated (0754e4b09 -> df70827e0)

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/33/35233/3 in repository toolchain/jenkins-scripts. discards 0754e4b09 tcwg_bmk-build.sh: Always write benchmark results_id file adds df70827e0 tcwg_bmk-build.sh: Always write benchmark results_id file 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 (0754e4b09) \ N -- N -- N refs/changes/33/35233/3 (df70827e0) 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/33/35233/2 updated (0308dee99 -> abfffcd99)

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/33/35233/2 in repository toolchain/jenkins-scripts. discards 0308dee99 tcwg_bmk-build.sh: Always write benchmark results_id file new abfffcd99 tcwg_bmk-build.sh: Always write benchmark results_id file 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 (0308dee99) \ N -- N -- N refs/changes/33/35233/2 (abfffcd99) 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/33/35233/1 updated (c75c8946b -> 02afa7705)

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/33/35233/1 in repository toolchain/jenkins-scripts. discards c75c8946b tcwg_bmk-build.sh: Always write benchmark results_id file new 02afa7705 tcwg_bmk-build.sh: Always write benchmark results_id file 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 (c75c8946b) \ N -- N -- N refs/changes/33/35233/1 (02afa7705) 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/33/35033/1 updated (e5712005c -> ea6992110)

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/33/35033/1 in repository toolchain/jenkins-scripts. discards e5712005c abe-bisect*: Fix grep invocations adds ea6992110 abe-bisect*: Fix grep invocations 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 (e5712005c) \ N -- N -- N refs/changes/33/35033/1 (ea6992110) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024