Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/02/41102/5 updated (83feec22b -> 122a06d64)

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/02/41102/5 in repository toolchain/jenkins-scripts. discards 83feec22b tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] adds 122a06d64 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] 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 (83feec22b) \ N -- N -- N refs/changes/02/41102/5 (122a06d64) 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/02/41102/4 updated (b7e039de0 -> d5d525235)

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/02/41102/4 in repository toolchain/jenkins-scripts. discards b7e039de0 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] new d5d525235 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] 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 (b7e039de0) \ N -- N -- N refs/changes/02/41102/4 (d5d525235) 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/02/41102/3 updated (032f2c2d5 -> 74baeb261)

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/02/41102/3 in repository toolchain/jenkins-scripts. discards 032f2c2d5 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] new 74baeb261 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] 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 (032f2c2d5) \ N -- N -- N refs/changes/02/41102/3 (74baeb261) 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/02/41102/2 updated (e9ab77ab3 -> 19bbdfc4c)

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/02/41102/2 in repository toolchain/jenkins-scripts. discards e9ab77ab3 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] new 19bbdfc4c tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] 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 (e9ab77ab3) \ N -- N -- N refs/changes/02/41102/2 (19bbdfc4c) 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/02/41102/1 updated (881f649c7 -> 209d7e226)

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/02/41102/1 in repository toolchain/jenkins-scripts. discards 881f649c7 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] new 209d7e226 tcwg-benchmark-results.sh: Refactor to call bmk-scripts/gathe [...] 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 (881f649c7) \ N -- N -- N refs/changes/02/41102/1 (209d7e226) 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/02/39702/1 updated (692947065 -> 6d3dffd62)

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/02/39702/1 in repository toolchain/jenkins-scripts. discards 692947065 tcwg_bmk-build.sh: Rework compare_results_perf to generate re [...] adds 6d3dffd62 tcwg_bmk-build.sh: Rework compare_results_perf to generate re [...] 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 (692947065) \ N -- N -- N refs/changes/02/39702/1 (6d3dffd62) 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/02/39602/2 updated (5cfb5d511 -> 04c811b47)

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/02/39602/2 in repository toolchain/jenkins-scripts. discards 5cfb5d511 build_llvm_package.bat: Add local changes adds 04c811b47 build_llvm_package.bat: Add local changes 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 (5cfb5d511) \ N -- N -- N refs/changes/02/39602/2 (04c811b47) 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/02/39602/1 updated (c9416b293 -> 599a166c6)

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/02/39602/1 in repository toolchain/jenkins-scripts. discards c9416b293 build_llvm_package.bat: Add local changes new 599a166c6 build_llvm_package.bat: Add local changes 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 (c9416b293) \ N -- N -- N refs/changes/02/39602/1 (599a166c6) 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/02/37402/1 updated (8bdc7c170 -> e1b7cb695)

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/02/37402/1 in repository toolchain/jenkins-scripts. discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE 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 (8bdc7c170) \ N -- N -- N refs/changes/02/37402/1 (e1b7cb695) 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 | 661 -------------------------------------------------- 1 file changed, 661 deletions(-) delete mode 100755 round-robin-bisect.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/02/36402/1 updated (17335c2ff -> 996f1b8a8)

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/02/36402/1 in repository toolchain/jenkins-scripts. discards 17335c2ff tcwg_gnu-build.sh: Reduce pass threshold adds 996f1b8a8 tcwg_gnu-build.sh: Reduce pass threshold 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 (17335c2ff) \ N -- N -- N refs/changes/02/36402/1 (996f1b8a8) 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024