Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/61/45261/3 updated (2ec1a6363 -> 392fc2d06)

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/45261/3 in repository toolchain/jenkins-scripts. discards 2ec1a6363 tcwg_bmk-build.sh: Use all history to compute sample variability adds 392fc2d06 tcwg_bmk-build.sh: Use all history to compute sample variability 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 (2ec1a6363) \ N -- N -- N refs/changes/61/45261/3 (392fc2d06) 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/45261/2 updated (caa29d42b -> 14993c7f3)

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/45261/2 in repository toolchain/jenkins-scripts. discards caa29d42b tcwg_bmk-build.sh: Use all history to compute sample variability new 14993c7f3 tcwg_bmk-build.sh: Use all history to compute sample variability 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 (caa29d42b) \ N -- N -- N refs/changes/61/45261/2 (14993c7f3) 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/45261/1 updated (e24ef1e89 -> 5707cb02f)

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/45261/1 in repository toolchain/jenkins-scripts. discards e24ef1e89 tcwg_bmk-build.sh: Use all history to compute sample variability new 5707cb02f tcwg_bmk-build.sh: Use all history to compute sample variability 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 (e24ef1e89) \ N -- N -- N refs/changes/61/45261/1 (5707cb02f) 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/44161/1 updated (118b837ba -> 07602a0aa)

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/44161/1 in repository toolchain/jenkins-scripts. discards 118b837ba round-robin.sh (build_abe): Touch GCC's auto-generated files adds 07602a0aa round-robin.sh (build_abe): Touch GCC's auto-generated files 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 (118b837ba) \ N -- N -- N refs/changes/61/44161/1 (07602a0aa) 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/43561/1 updated (30973f55f -> 24e8aaf40)

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/43561/1 in repository toolchain/jenkins-scripts. discards 30973f55f round-robin.sh: Unify implementations of breakup_changed_components adds 24e8aaf40 round-robin.sh: Unify implementations of breakup_changed_components 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 (30973f55f) \ N -- N -- N refs/changes/61/43561/1 (24e8aaf40) 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/43461/1 updated (d9df8d2e5 -> 05f646931)

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/43461/1 in repository toolchain/jenkins-scripts. discards d9df8d2e5 tcwg-llvmbot: Move armv8-lld-2stage so silent adds 05f646931 tcwg-llvmbot: Move armv8-lld-2stage so silent 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 (d9df8d2e5) \ N -- N -- N refs/changes/61/43461/1 (05f646931) 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/43361/1 updated (068160062 -> 571a02d76)

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/43361/1 in repository toolchain/jenkins-scripts. discards 068160062 tcwg_bmk-build.sh: Look at ci_project to patch cflags adds 571a02d76 tcwg_bmk-build.sh: Look at ci_project to patch cflags 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 (068160062) \ N -- N -- N refs/changes/61/43361/1 (571a02d76) 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/42261/2 updated (d8eced4b0 -> 9b327d9f1)

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/42261/2 in repository toolchain/jenkins-scripts. discards d8eced4b0 tcwg_bmk-build.sh,dashboard-generate-squad.sh: Add suffix vs- [...] adds 9b327d9f1 tcwg_bmk-build.sh,dashboard-generate-squad.sh: Add suffix vs- [...] 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 (d8eced4b0) \ N -- N -- N refs/changes/61/42261/2 (9b327d9f1) 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/42261/1 updated (aaa841c1f -> 6483436e8)

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/42261/1 in repository toolchain/jenkins-scripts. discards aaa841c1f tcwg_bmk-build.sh,dashboard-generate-squad.sh: Add suffix vs- [...] new 6483436e8 tcwg_bmk-build.sh,dashboard-generate-squad.sh: Add suffix vs- [...] 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 (aaa841c1f) \ N -- N -- N refs/changes/61/42261/1 (6483436e8) 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/42061/1 updated (2f708af69 -> 619cd47b6)

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/42061/1 in repository toolchain/jenkins-scripts. discards 2f708af69 dashboard-generate-squad.sh: remove extra space adds 619cd47b6 dashboard-generate-squad.sh: remove extra space 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 (2f708af69) \ N -- N -- N refs/changes/61/42061/1 (619cd47b6) 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