Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/58/47158/1 updated (f4e76aa62 -> 55beab9e1)

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/58/47158/1 in repository toolchain/jenkins-scripts. discards f4e76aa62 tcwg_bmk-build.sh: upgrade fujitsu projects adds 55beab9e1 tcwg_bmk-build.sh: upgrade fujitsu 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 (f4e76aa62) \ N -- N -- N refs/changes/58/47158/1 (55beab9e1) 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/58/47058/1 updated (733f719de -> 99f40fe9c)

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/58/47058/1 in repository toolchain/jenkins-scripts. discards 733f719de tcwg_gnu-build.sh: Improve handling of corrupted results. adds 99f40fe9c tcwg_gnu-build.sh: Improve handling of corrupted results. 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 (733f719de) \ N -- N -- N refs/changes/58/47058/1 (99f40fe9c) 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/58/46758/2 updated (0535e1c33 -> 1276b9ce2)

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/58/46758/2 in repository toolchain/jenkins-scripts. discards 0535e1c33 start-container-docker.sh: Workaround WSL's issue with "hostname -A" adds 1276b9ce2 start-container-docker.sh: Workaround WSL's issue with "hostname -A" 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 (0535e1c33) \ N -- N -- N refs/changes/58/46758/2 (1276b9ce2) 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/58/46758/1 updated (30d1275fe -> 7e4f1ae08)

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/58/46758/1 in repository toolchain/jenkins-scripts. discards 30d1275fe start-container-docker.sh: Workaround WSL's issue with "hostname -A" new 7e4f1ae08 start-container-docker.sh: Workaround WSL's issue with "hostname -A" 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 (30d1275fe) \ N -- N -- N refs/changes/58/46758/1 (7e4f1ae08) 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/58/46658/3 updated (949149644 -> ca09d67f4)

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/58/46658/3 in repository toolchain/jenkins-scripts. discards 949149644 tcwg_gnu-build.sh: Add support for aarch64-w64-mingw32 adds ca09d67f4 tcwg_gnu-build.sh: Add support for aarch64-w64-mingw32 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 (949149644) \ N -- N -- N refs/changes/58/46658/3 (ca09d67f4) 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/58/46658/2 updated (0d82f4dee -> 3fb3224aa)

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/58/46658/2 in repository toolchain/jenkins-scripts. discards 0d82f4dee tcwg_gnu-build.sh: Add support for aarch64-w64-mingw32 adds 3fb3224aa tcwg_gnu-build.sh: Add support for aarch64-w64-mingw32 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 (0d82f4dee) \ N -- N -- N refs/changes/58/46658/2 (3fb3224aa) 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/58/46658/1 updated (2896c9d54 -> 78071a0f2)

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/58/46658/1 in repository toolchain/jenkins-scripts. discards 2896c9d54 tcwg_gnu-build.sh: Add support for aarch64-w64-mingw32 new 78071a0f2 tcwg_gnu-build.sh: Add support for aarch64-w64-mingw32 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 (2896c9d54) \ N -- N -- N refs/changes/58/46658/1 (78071a0f2) 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/58/46458/1 updated (5b460638d -> a0efa3efe)

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/58/46458/1 in repository toolchain/jenkins-scripts. discards 5b460638d jenkins-helpers.sh (git_clean): Remove corrupted index adds a0efa3efe jenkins-helpers.sh (git_clean): Remove corrupted index 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 (5b460638d) \ N -- N -- N refs/changes/58/46458/1 (a0efa3efe) 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/58/45658/2 updated (3d9a6a027 -> 9485a171d)

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/58/45658/2 in repository toolchain/jenkins-scripts. discards 3d9a6a027 round-robin-notify.sh (print_mail_recipients): Make more flexible discards 291741672 round-robin-notify.sh (print_mail_recipients): Simplify discards addf3b386 round-robin-notify.sh: Re-enable emails to clang-built-linux project discards 41f2ed493 round-robin-notify.sh (update_interesting_commits): Cleanup u [...] discards 80d12e5ff round-robin-notify.sh (update_interesting_commits): Rename su [...] discards 7eacfd71e round-robin-notify.sh (update_interesting_commits): Add detai [...] discards 11c2ca8e2 tcwg_bmk-build.sh: rename samples-variabilty.py script adds 9485a171d tcwg_bmk-build.sh: rename samples-variabilty.py script 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 (3d9a6a027) \ N -- N -- N refs/changes/58/45658/2 (9485a171d) 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 | 455 ------------- round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1719 ----------------------------------------------- 3 files changed, 2829 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/58/45658/1 updated (4da7ba729 -> ecc96ac0b)

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/58/45658/1 in repository toolchain/jenkins-scripts. discards 4da7ba729 round-robin-notify.sh (print_mail_recipients): Make more flexible discards 61a1d785f round-robin-notify.sh (print_mail_recipients): Simplify discards 390caa644 round-robin-notify.sh: Re-enable emails to clang-built-linux project discards 38d813d9e round-robin-notify.sh (update_interesting_commits): Cleanup u [...] discards a91dd19f9 round-robin-notify.sh (update_interesting_commits): Rename su [...] discards 359c8e061 round-robin-notify.sh (update_interesting_commits): Add detai [...] discards f20216f12 round-robin-notify.sh: Cleanup generation of email files discards d67583abd round-robin-notify.sh (print_commits): Improve precommit output discards 0985806cc round-robin-notify.sh (print_commits): Restructure adds ecc96ac0b round-robin-notify.sh (print_commits): Restructure 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 (4da7ba729) \ N -- N -- N refs/changes/58/45658/1 (ecc96ac0b) 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 | 455 ------------- round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1715 ----------------------------------------------- 3 files changed, 2825 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024