Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/53/41353/3 updated (502dd1f7b -> d509e3c03)

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/53/41353/3 in repository toolchain/jenkins-scripts. discards 502dd1f7b tcwg-benchmark.sh: Update after changes to dockerfiles and bm [...] new d509e3c03 tcwg-benchmark.sh: Update after changes to dockerfiles and bm [...] 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 (502dd1f7b) \ N -- N -- N refs/changes/53/41353/3 (d509e3c03) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/41353/2 updated (2e6b1d9c4 -> b14ca19e6)

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/53/41353/2 in repository toolchain/jenkins-scripts. discards 2e6b1d9c4 tcwg-benchmark.sh: Update after changes to dockerfiles and bm [...] new b14ca19e6 tcwg-benchmark.sh: Update after changes to dockerfiles and bm [...] 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 (2e6b1d9c4) \ N -- N -- N refs/changes/53/41353/2 (b14ca19e6) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/41353/1 updated (51d99cd6b -> a39ac7d36)

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/53/41353/1 in repository toolchain/jenkins-scripts. discards 51d99cd6b tcwg-benchmark.sh: Update after changes to dockerfiles and bm [...] new a39ac7d36 tcwg-benchmark.sh: Update after changes to dockerfiles and bm [...] 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 (51d99cd6b) \ N -- N -- N refs/changes/53/41353/1 (a39ac7d36) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/39753/1 updated (b22d3a7ef -> 0afa7c528)

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/53/39753/1 in repository toolchain/jenkins-scripts. discards b22d3a7ef Pass -fdump-tree-vect-details instead of -fmetric-vect. adds 0afa7c528 Pass -fdump-tree-vect-details instead of -fmetric-vect. 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 (b22d3a7ef) \ N -- N -- N refs/changes/53/39753/1 (0afa7c528) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/39653/3 updated (10b16478e -> 15ca1c93b)

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/53/39653/3 in repository toolchain/jenkins-scripts. discards 10b16478e round-robin-bisect.sh: Simplify discards be2c4b0f3 round-robin-bisect.sh: Update email settings discards d2e36cbb6 tcwg-llvm-release.bat: Fix path to the toolchain package adds 15ca1c93b tcwg-llvm-release.bat: Fix path to the toolchain package 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 (10b16478e) \ N -- N -- N refs/changes/53/39653/3 (15ca1c93b) 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 | 862 -------------------------------------------------- 1 file changed, 862 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/39653/2 updated (8a89b129b -> c38028e6c)

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/53/39653/2 in repository toolchain/jenkins-scripts. discards 8a89b129b round-robin-bisect.sh: Simplify discards 1727db400 round-robin.sh: Remove obsolete workarounds new c38028e6c round-robin.sh: Remove obsolete workarounds 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 (8a89b129b) \ N -- N -- N refs/changes/53/39653/2 (c38028e6c) 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: round-robin-bisect.sh | 862 -------------------------------------------------- 1 file changed, 862 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/39653/1 updated (003d3d9cb -> c38028e6c)

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/53/39653/1 in repository toolchain/jenkins-scripts. discards 003d3d9cb round-robin-bisect.sh: Simplify discards 1727db400 round-robin.sh: Remove obsolete workarounds new c38028e6c round-robin.sh: Remove obsolete workarounds 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 (003d3d9cb) \ N -- N -- N refs/changes/53/39653/1 (c38028e6c) 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: round-robin-bisect.sh | 863 -------------------------------------------------- 1 file changed, 863 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/33553/3 updated (95147987b -> ed10384d9)

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/53/33553/3 in repository toolchain/jenkins-scripts. discards 95147987b round-robin.sh: Try to fix print_updated_components() for 3'r [...] adds ed10384d9 round-robin.sh: Try to fix print_updated_components() for 3'r [...] 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 (95147987b) \ N -- N -- N refs/changes/53/33553/3 (ed10384d9) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/33553/2 updated (731b56d41 -> 541d45f4d)

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/53/33553/2 in repository toolchain/jenkins-scripts. discards 731b56d41 round-robin.sh: Try to fix print_updated_components() for 3'r [...] new 541d45f4d round-robin.sh: Try to fix print_updated_components() for 3'r [...] 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 (731b56d41) \ N -- N -- N refs/changes/53/33553/2 (541d45f4d) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/33553/1 updated (0e5373d62 -> e8c06a1e9)

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/53/33553/1 in repository toolchain/jenkins-scripts. discards 0e5373d62 round-robin.sh: Try to fix print_updated_components() fro 3'r [...] adds e8c06a1e9 round-robin.sh: Try to fix print_updated_components() fro 3'r [...] 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 (0e5373d62) \ N -- N -- N refs/changes/53/33553/1 (e8c06a1e9) 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, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024