Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/91/38991/1 updated (d8d21bab7 -> 209198d23)

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/91/38991/1 in repository toolchain/jenkins-scripts. discards d8d21bab7 jenkins-helpers.sh: Bind-mount benchmark git cache for bmk co [...] adds 209198d23 jenkins-helpers.sh: Bind-mount benchmark git cache for bmk co [...] 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 (d8d21bab7) \ N -- N -- N refs/changes/91/38991/1 (209198d23) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/38191/3 updated (4922ec826 -> 224158a71)

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/91/38191/3 in repository toolchain/jenkins-scripts. discards 4922ec826 tcwg-benchmark.sh: Pass --image DOCKER_IMAGE to prepare-board.sh adds 224158a71 tcwg-benchmark.sh: Pass --image DOCKER_IMAGE to prepare-board.sh 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 (4922ec826) \ N -- N -- N refs/changes/91/38191/3 (224158a71) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/38191/2 updated (09b5df7df -> 487dd8c9c)

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/91/38191/2 in repository toolchain/jenkins-scripts. discards 09b5df7df tcwg-benchmark.sh: Pass --image DOCKER_IMAGE to prepare-board.sh new 487dd8c9c tcwg-benchmark.sh: Pass --image DOCKER_IMAGE to prepare-board.sh 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 (09b5df7df) \ N -- N -- N refs/changes/91/38191/2 (487dd8c9c) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/38191/1 updated (e8c37084b -> 01b3c4381)

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/91/38191/1 in repository toolchain/jenkins-scripts. discards e8c37084b tcwg-benchmark.sh: Pass --image DOCKER_IMAGE to prepare-board.sh new 01b3c4381 tcwg-benchmark.sh: Pass --image DOCKER_IMAGE to prepare-board.sh 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 (e8c37084b) \ N -- N -- N refs/changes/91/38191/1 (01b3c4381) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/35391/3 updated (606fe7b4f -> 223f20bb6)

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/91/35391/3 in repository toolchain/jenkins-scripts. discards 606fe7b4f tcwg_bmk-build.sh: Fix loop waiting for benchmarking to finish adds 223f20bb6 tcwg_bmk-build.sh: Fix loop waiting for benchmarking to finish 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 (606fe7b4f) \ N -- N -- N refs/changes/91/35391/3 (223f20bb6) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/35391/2 updated (7da1a0a92 -> ce95fb1dd)

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/91/35391/2 in repository toolchain/jenkins-scripts. discards 7da1a0a92 tcwg_bmk-build.sh: Fix loop waiting for benchmarking to finish new ce95fb1dd tcwg_bmk-build.sh: Fix loop waiting for benchmarking to finish 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 (7da1a0a92) \ N -- N -- N refs/changes/91/35391/2 (ce95fb1dd) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/35391/1 updated (bf135c878 -> e22d2a28d)

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/91/35391/1 in repository toolchain/jenkins-scripts. discards bf135c878 tcwg_bmk-build.sh: Fix loop waiting for benchmarking to finish new e22d2a28d tcwg_bmk-build.sh: Fix loop waiting for benchmarking to finish 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 (bf135c878) \ N -- N -- N refs/changes/91/35391/1 (e22d2a28d) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/32991/7 updated (680859d62 -> 6a161f8eb)

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/91/32991/7 in repository toolchain/jenkins-scripts. discards 680859d62 tcwg_bmk-build.sh: Rework result comparison adds 6a161f8eb tcwg_bmk-build.sh: Rework result comparison 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 (680859d62) \ N -- N -- N refs/changes/91/32991/7 (6a161f8eb) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/32991/6 updated (15c73dee8 -> a475809c9)

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/91/32991/6 in repository toolchain/jenkins-scripts. discards 15c73dee8 tcwg_bmk-build.sh: Rework result comparison adds a475809c9 tcwg_bmk-build.sh: Rework result comparison 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 (15c73dee8) \ N -- N -- N refs/changes/91/32991/6 (a475809c9) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/32991/5 updated (447f694ae -> 967ff8de9)

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/91/32991/5 in repository toolchain/jenkins-scripts. discards 447f694ae tcwg_bmk-build.sh: Rework result comparison adds 967ff8de9 tcwg_bmk-build.sh: Rework result comparison 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 (447f694ae) \ N -- N -- N refs/changes/91/32991/5 (967ff8de9) 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024