Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/61/33961/4 updated (981d178df -> b65638e96)

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/61/33961/4 in repository toolchain/jenkins-scripts. discards 981d178df tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy scores adds b65638e96 tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy 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 (981d178df) \ N -- N -- N refs/changes/61/33961/4 (b65638e96) 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/61/33961/3 updated (da6c5be82 -> cf751c1b6)

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/61/33961/3 in repository toolchain/jenkins-scripts. discards da6c5be82 tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy scores new cf751c1b6 tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy 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 (da6c5be82) \ N -- N -- N refs/changes/61/33961/3 (cf751c1b6) 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/61/33961/2 updated (0e1d20927 -> ad1fb278f)

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/61/33961/2 in repository toolchain/jenkins-scripts. discards 0e1d20927 tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy scores new ad1fb278f tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy 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 (0e1d20927) \ N -- N -- N refs/changes/61/33961/2 (ad1fb278f) 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/61/33961/1 updated (51ad82964 -> 679a81dcd)

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/61/33961/1 in repository toolchain/jenkins-scripts. discards 51ad82964 tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy scores new 679a81dcd tcwg_bmk-build.sh, tcwg_gnu-build.sh: Fix bisection-worthy 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 (51ad82964) \ N -- N -- N refs/changes/61/33961/1 (679a81dcd) 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/61/30861/1 updated (c456885a4 -> 7d6bf5ca2)

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/61/30861/1 in repository toolchain/jenkins-scripts. discards c456885a4 Add tcwg_bmk-build.sh as a copy of tcwg_kernel-build.sh adds 7d6bf5ca2 Add tcwg_bmk-build.sh as a copy of 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 (c456885a4) \ N -- N -- N refs/changes/61/30861/1 (7d6bf5ca2) 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/61/30461/1 updated (edc32fe94 -> f328ee33d)

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/61/30461/1 in repository toolchain/jenkins-scripts. discards edc32fe94 tcwg_bmk-build.sh: Restrict LLVM benchmarking to c_and_cxx adds f328ee33d tcwg_bmk-build.sh: Restrict LLVM benchmarking to c_and_cxx 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 (edc32fe94) \ N -- N -- N refs/changes/61/30461/1 (f328ee33d) 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/61/30261/3 updated (eb98ad65e -> a26823bc3)

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/61/30261/3 in repository toolchain/jenkins-scripts. discards eb98ad65e [rr-many 4/N] Update round-robin.sh: push_baseline() adds a26823bc3 [rr-many 4/N] Update round-robin.sh: push_baseline() 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 (eb98ad65e) \ N -- N -- N refs/changes/61/30261/3 (a26823bc3) 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/61/30261/2 updated (bb65dfcf7 -> 018c24fcc)

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/61/30261/2 in repository toolchain/jenkins-scripts. discards bb65dfcf7 [rr-many 4/N] Update round-robin.sh: push_baseline() adds 018c24fcc [rr-many 4/N] Update round-robin.sh: push_baseline() 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 (bb65dfcf7) \ N -- N -- N refs/changes/61/30261/2 (018c24fcc) 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/61/30261/1 updated (b4f6859ae -> 36e458f19)

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/61/30261/1 in repository toolchain/jenkins-scripts. discards b4f6859ae [rr-many 4/N] Update round-robin.sh: update_baseline() adds 36e458f19 [rr-many 4/N] Update round-robin.sh: update_baseline() 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 (b4f6859ae) \ N -- N -- N refs/changes/61/30261/1 (36e458f19) 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/60/47260/8 updated (b64959104 -> 3abf770c2)

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/60/47260/8 in repository toolchain/jenkins-scripts. discards b64959104 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] adds 3abf770c2 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (b64959104) \ N -- N -- N refs/changes/60/47260/8 (3abf770c2) 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