Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/05/30005/2 updated (bd85ea4a3 -> e411384f6)

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/05/30005/2 in repository toolchain/jenkins-scripts. discards bd85ea4a3 tcwg_bmk-build: Do not hardcode HW type in results_id adds e411384f6 tcwg_bmk-build: Do not hardcode HW type in results_id 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 (bd85ea4a3) \ N -- N -- N refs/changes/05/30005/2 (e411384f6) 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/05/30005/1 updated (7605e0419 -> 3986fc7ef)

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/05/30005/1 in repository toolchain/jenkins-scripts. discards 7605e0419 tcwg_bmk-build: Do not hardcode HW type in results_id new 3986fc7ef tcwg_bmk-build: Do not hardcode HW type in results_id 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 (7605e0419) \ N -- N -- N refs/changes/05/30005/1 (3986fc7ef) 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/04/47304/1 updated (82dbc454f -> 78bd2abb0)

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/04/47304/1 in repository toolchain/jenkins-scripts. discards 82dbc454f tcwg-cleanup-stale-results.sh: use remote get_git_history, fi [...] adds 78bd2abb0 tcwg-cleanup-stale-results.sh: use remote get_git_history, fi [...] 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 (82dbc454f) \ N -- N -- N refs/changes/04/47304/1 (78bd2abb0) 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/04/47204/2 updated (fabb45bf9 -> 2d86ec62d)

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/04/47204/2 in repository toolchain/jenkins-scripts. discards fabb45bf9 round-robin-*.sh: Add rr_stage jenkins job parameter adds 2d86ec62d round-robin-*.sh: Add rr_stage jenkins job parameter 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 (fabb45bf9) \ N -- N -- N refs/changes/04/47204/2 (2d86ec62d) 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/04/47204/1 updated (8d499353f -> b91676106)

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/04/47204/1 in repository toolchain/jenkins-scripts. discards 8d499353f round-robin-*.sh: Add rr_stage jenkins job parameter new b91676106 round-robin-*.sh: Add rr_stage jenkins job parameter 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 (8d499353f) \ N -- N -- N refs/changes/04/47204/1 (b91676106) 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/04/47004/1 updated (bb99cb211 -> 14aaef21a)

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/04/47004/1 in repository toolchain/jenkins-scripts. discards bb99cb211 tcwg_bmk-build.sh: Upgrade minor version for some bmk projects adds 14aaef21a tcwg_bmk-build.sh: Upgrade minor version for some bmk projects 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 (bb99cb211) \ N -- N -- N refs/changes/04/47004/1 (14aaef21a) 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/04/46904/3 updated (421ce970a -> 558253bc3)

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/04/46904/3 in repository toolchain/jenkins-scripts. discards 421ce970a tcwg_chromium-build.sh: The revisions used to update each com [...] adds 558253bc3 tcwg_chromium-build.sh: The revisions used to update each com [...] 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 (421ce970a) \ N -- N -- N refs/changes/04/46904/3 (558253bc3) 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/04/46904/2 updated (9cd02703d -> 34684621a)

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/04/46904/2 in repository toolchain/jenkins-scripts. discards 9cd02703d tcwg_chromium-build.sh: The revisions used to update each com [...] new 34684621a tcwg_chromium-build.sh: The revisions used to update each com [...] 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 (9cd02703d) \ N -- N -- N refs/changes/04/46904/2 (34684621a) 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/04/46904/1 updated (bcf24b711 -> 4c492f11d)

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/04/46904/1 in repository toolchain/jenkins-scripts. discards bcf24b711 tcwg_chromium-build.sh: update each components is done after [...] new 4c492f11d tcwg_chromium-build.sh: update each components is done after [...] 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 (bcf24b711) \ N -- N -- N refs/changes/04/46904/1 (4c492f11d) 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/04/46204/3 updated (b6e213412 -> ffc635404)

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/04/46204/3 in repository toolchain/jenkins-scripts. discards b6e213412 round-robin.sh: Move testresults2jenkins.sh to ABE adds ffc635404 round-robin.sh: Move testresults2jenkins.sh to 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 (b6e213412) \ N -- N -- N refs/changes/04/46204/3 (ffc635404) 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