Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/87/35387/3 updated (ccb12e1c5 -> 813603848)

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/87/35387/3 in repository toolchain/jenkins-scripts. discards ccb12e1c5 tcwg_bmk-build.sh: Adjust build scores adds 813603848 tcwg_bmk-build.sh: Adjust build scores 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 (ccb12e1c5) \ N -- N -- N refs/changes/87/35387/3 (813603848) 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/87/35387/2 updated (3bc016aab -> 65562a946)

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/87/35387/2 in repository toolchain/jenkins-scripts. discards 3bc016aab tcwg_bmk-build.sh: Adjust build scores adds 65562a946 tcwg_bmk-build.sh: Adjust build scores 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 (3bc016aab) \ N -- N -- N refs/changes/87/35387/2 (65562a946) 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/87/35387/1 updated (13f817a5e -> 234030e2d)

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/87/35387/1 in repository toolchain/jenkins-scripts. discards 13f817a5e tcwg_bmk-build.sh: Adjust build scores adds 234030e2d tcwg_bmk-build.sh: Adjust build scores 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 (13f817a5e) \ N -- N -- N refs/changes/87/35387/1 (234030e2d) 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/87/34987/1 updated (76d9d1354 -> 007600e16)

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/87/34987/1 in repository toolchain/jenkins-scripts. discards 76d9d1354 round-robin.sh/tcwg_kernel-build.sh adds 007600e16 round-robin.sh/tcwg_kernel-build.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 (76d9d1354) \ N -- N -- N refs/changes/87/34987/1 (007600e16) 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/87/34387/2 updated (61d8236d6 -> 0f9eb7e91)

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/87/34387/2 in repository toolchain/jenkins-scripts. discards 61d8236d6 tcwg_bmk-build.sh: define ref_artifacts and new_artifacts in [...] adds 0f9eb7e91 tcwg_bmk-build.sh: define ref_artifacts and new_artifacts in [...] 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 (61d8236d6) \ N -- N -- N refs/changes/87/34387/2 (0f9eb7e91) 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/87/34387/1 updated (dc2270a8e -> ec4ae4ee8)

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/87/34387/1 in repository toolchain/jenkins-scripts. discards dc2270a8e tcwg_bmk-build.sh: Fix thinko in second to last commit new ec4ae4ee8 tcwg_bmk-build.sh: Fix thinko in second to last commit 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 (dc2270a8e) \ N -- N -- N refs/changes/87/34387/1 (ec4ae4ee8) 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/87/32987/4 updated (8905025aa -> 2fd6527e1)

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/87/32987/4 in repository toolchain/jenkins-scripts. discards 8905025aa round-robin.sh: Add no_build_regression_p helper adds 2fd6527e1 round-robin.sh: Add no_build_regression_p helper 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 (8905025aa) \ N -- N -- N refs/changes/87/32987/4 (2fd6527e1) 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/87/32987/3 updated (7ede2b3a4 -> f13dbfc39)

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/87/32987/3 in repository toolchain/jenkins-scripts. discards 7ede2b3a4 round-robin.sh: Add no_build_regression_p helper adds f13dbfc39 round-robin.sh: Add no_build_regression_p helper 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 (7ede2b3a4) \ N -- N -- N refs/changes/87/32987/3 (f13dbfc39) 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/87/32987/2 updated (3220e5e01 -> 679f3ec8a)

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/87/32987/2 in repository toolchain/jenkins-scripts. discards 3220e5e01 round-robin.sh: Add no_build_regression_p helper adds 679f3ec8a round-robin.sh: Add no_build_regression_p helper 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 (3220e5e01) \ N -- N -- N refs/changes/87/32987/2 (679f3ec8a) 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/87/32987/1 updated (cbe398ad6 -> 9cdf9014e)

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/87/32987/1 in repository toolchain/jenkins-scripts. discards cbe398ad6 round-robin.sh: Add no_build_regression_p helper adds 9cdf9014e round-robin.sh: Add no_build_regression_p helper 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 (cbe398ad6) \ N -- N -- N refs/changes/87/32987/1 (9cdf9014e) 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