Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/63/45163/1 updated (e97272d40 -> f74284c9f)

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/63/45163/1 in repository toolchain/jenkins-scripts. discards e97272d40 round-robin-notify.sh (generate_jira_dir): Fix links to mail- [...] discards 2146d498c tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune adds f74284c9f tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune 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 (e97272d40) \ N -- N -- N refs/changes/63/45163/1 (f74284c9f) 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: round-robin-baseline.sh | 410 ------------- round-robin-bisect.sh | 653 -------------------- round-robin-notify.sh | 1506 ----------------------------------------------- 3 files changed, 2569 deletions(-) delete mode 100755 round-robin-baseline.sh delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- 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/63/44163/1 updated (354d01e46 -> 010f23ed0)

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/63/44163/1 in repository toolchain/jenkins-scripts. discards 354d01e46 round-robin.sh: Prepare source checkouts even better adds 010f23ed0 round-robin.sh: Prepare source checkouts even better 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 (354d01e46) \ N -- N -- N refs/changes/63/44163/1 (010f23ed0) 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/63/43563/1 updated (c4d9060b3 -> 8a6c430e2)

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/63/43563/1 in repository toolchain/jenkins-scripts. discards c4d9060b3 round-robin.sh: Fix typo adds 8a6c430e2 round-robin.sh: Fix typo 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 (c4d9060b3) \ N -- N -- N refs/changes/63/43563/1 (8a6c430e2) 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/63/43363/7 updated (5a84254c2 -> 8273f6c3d)

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/63/43363/7 in repository toolchain/jenkins-scripts. discards 5a84254c2 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] adds 8273f6c3d tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] 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 (5a84254c2) \ N -- N -- N refs/changes/63/43363/7 (8273f6c3d) 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/63/43363/6 updated (5138df2d0 -> b206e2f4c)

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/63/43363/6 in repository toolchain/jenkins-scripts. discards 5138df2d0 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] new b206e2f4c tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] 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 (5138df2d0) \ N -- N -- N refs/changes/63/43363/6 (b206e2f4c) 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/63/43363/5 updated (b18ce4b75 -> 254485683)

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/63/43363/5 in repository toolchain/jenkins-scripts. discards b18ce4b75 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] new 254485683 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] 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 (b18ce4b75) \ N -- N -- N refs/changes/63/43363/5 (254485683) 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/63/43363/4 updated (6e98cae89 -> 6d90b8b7c)

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/63/43363/4 in repository toolchain/jenkins-scripts. discards 6e98cae89 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] new 6d90b8b7c tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] 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 (6e98cae89) \ N -- N -- N refs/changes/63/43363/4 (6d90b8b7c) 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/63/43363/3 updated (8765ae34d -> 15aae2647)

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/63/43363/3 in repository toolchain/jenkins-scripts. discards 8765ae34d tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] new 15aae2647 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] 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 (8765ae34d) \ N -- N -- N refs/changes/63/43363/3 (15aae2647) 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/63/43363/2 updated (a50fcf553 -> 30056ba83)

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/63/43363/2 in repository toolchain/jenkins-scripts. discards a50fcf553 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] adds 30056ba83 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] 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 (a50fcf553) \ N -- N -- N refs/changes/63/43363/2 (30056ba83) 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/63/43363/1 updated (5085c1007 -> a2a2bceb5)

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/63/43363/1 in repository toolchain/jenkins-scripts. discards 5085c1007 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] adds a2a2bceb5 tcwg_bmk-build.sh: Fix tcwg_bmk_benchs. Run only one benchmar [...] 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 (5085c1007) \ N -- N -- N refs/changes/63/43363/1 (a2a2bceb5) 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