Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/52/42352/3 updated (edb03a734 -> 065a051ed)

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/52/42352/3 in repository toolchain/jenkins-scripts. discards edb03a734 tcwg_bmk-build.sh: Rewriting adds 065a051ed tcwg_bmk-build.sh: Rewriting 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 (edb03a734) \ N -- N -- N refs/changes/52/42352/3 (065a051ed) 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/52/42352/2 updated (085853304 -> ff21dfbef)

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/52/42352/2 in repository toolchain/jenkins-scripts. discards 085853304 tcwg_bmk-build.sh: Rewriting new ff21dfbef tcwg_bmk-build.sh: Rewriting 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 (085853304) \ N -- N -- N refs/changes/52/42352/2 (ff21dfbef) 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/52/42352/1 updated (f168458d6 -> 98b281e9d)

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/52/42352/1 in repository toolchain/jenkins-scripts. discards f168458d6 tcwg_bmk-build.sh: Rewriting new 98b281e9d tcwg_bmk-build.sh: Rewriting 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 (f168458d6) \ N -- N -- N refs/changes/52/42352/1 (98b281e9d) 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/52/41852/1 updated (96f91382c -> 1e4b762db)

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/52/41852/1 in repository toolchain/jenkins-scripts. discards 96f91382c round-robin.sh: Handle partial/bisect builds in set_current_git() adds 1e4b762db round-robin.sh: Handle partial/bisect builds in set_current_git() 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 (96f91382c) \ N -- N -- N refs/changes/52/41852/1 (1e4b762db) 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/52/41752/4 updated (5f2932344 -> 66bd4dab9)

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/52/41752/4 in repository toolchain/jenkins-scripts. discards 5f2932344 tcwg_bmk-build.sh: Add support for SVE metric. adds 66bd4dab9 tcwg_bmk-build.sh: Add support for SVE metric. 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 (5f2932344) \ N -- N -- N refs/changes/52/41752/4 (66bd4dab9) 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/52/41752/3 updated (2bef9ff2c -> 366bf7f23)

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/52/41752/3 in repository toolchain/jenkins-scripts. discards 2bef9ff2c tcwg_bmk-build.sh: Add support for SVE metric. new 366bf7f23 tcwg_bmk-build.sh: Add support for SVE metric. 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 (2bef9ff2c) \ N -- N -- N refs/changes/52/41752/3 (366bf7f23) 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/52/41752/2 updated (8d2199de3 -> fa5390648)

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/52/41752/2 in repository toolchain/jenkins-scripts. discards 8d2199de3 tcwg_bmk-build.sh: Add support for SVE metric. new fa5390648 tcwg_bmk-build.sh: Add support for SVE metric. 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 (8d2199de3) \ N -- N -- N refs/changes/52/41752/2 (fa5390648) 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/52/41752/1 updated (653e28b96 -> 15561d7c2)

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/52/41752/1 in repository toolchain/jenkins-scripts. discards 653e28b96 tcwg_bmk-build.sh: Add support for SVE metric. new 15561d7c2 tcwg_bmk-build.sh: Add support for SVE metric. 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 (653e28b96) \ N -- N -- N refs/changes/52/41752/1 (15561d7c2) 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/52/41352/4 updated (9ba018fab -> fb803dfd7)

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/52/41352/4 in repository toolchain/jenkins-scripts. discards 9ba018fab tcwg-update-bmk-containers.sh: New script adds fb803dfd7 tcwg-update-bmk-containers.sh: New script 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 (9ba018fab) \ N -- N -- N refs/changes/52/41352/4 (fb803dfd7) 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/52/41352/3 updated (b2599d2aa -> f2096f914)

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/52/41352/3 in repository toolchain/jenkins-scripts. discards b2599d2aa tcwg-update-bmk-containers.sh: New script adds f2096f914 tcwg-update-bmk-containers.sh: New script 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 (b2599d2aa) \ N -- N -- N refs/changes/52/41352/3 (f2096f914) 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