Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/89/47289/1 updated (5682314c0 -> cd7d8c681)

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/89/47289/1 in repository toolchain/jenkins-scripts. discards 5682314c0 generate-cimonitor-dashboard.py: diag now detects git fetch errors adds cd7d8c681 generate-cimonitor-dashboard.py: diag now detects git fetch errors 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 (5682314c0) \ N -- N -- N refs/changes/89/47289/1 (cd7d8c681) 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/89/47189/2 updated (0c4c3e9ee -> 901278dbd)

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/89/47189/2 in repository toolchain/jenkins-scripts. discards 0c4c3e9ee round-robin-bisect.sh: Adjust trigger files in case of dynami [...] discards f66fabd79 tcwg_chromium-build.sh: component_to_update inherit from base [...] adds 901278dbd tcwg_chromium-build.sh: component_to_update inherit from base [...] 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 (0c4c3e9ee) \ N -- N -- N refs/changes/89/47189/2 (901278dbd) 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 | 650 ------------- round-robin-bisect.sh | 743 --------------- round-robin-notify.sh | 2419 ----------------------------------------------- 3 files changed, 3812 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/89/47189/1 updated (93515ef83 -> 6044b2fe4)

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/89/47189/1 in repository toolchain/jenkins-scripts. discards 93515ef83 round-robin-bisect.sh: Adjust trigger files in case of dynami [...] discards 908eb8bc5 tcwg_chromium-build.sh: component_to_update inherit from base [...] adds 6044b2fe4 tcwg_chromium-build.sh: component_to_update inherit from base [...] 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 (93515ef83) \ N -- N -- N refs/changes/89/47189/1 (6044b2fe4) 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 | 650 ------------- round-robin-bisect.sh | 743 --------------- round-robin-notify.sh | 2419 ----------------------------------------------- 3 files changed, 3812 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/89/46589/3 updated (73fc9f13c -> 928ac6202)

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/89/46589/3 in repository toolchain/jenkins-scripts. discards 73fc9f13c round-robin-notify.sh (gnu_print_result): Add configure/make [...] discards a39df41b8 tcwg_gnu-build.sh: Upgrading version to update LNT dashboard [...] adds 928ac6202 tcwg_gnu-build.sh: Upgrading version to update LNT dashboard [...] 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 (73fc9f13c) \ N -- N -- N refs/changes/89/46589/3 (928ac6202) 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 | 611 ------------ round-robin-bisect.sh | 686 -------------- round-robin-notify.sh | 2362 ----------------------------------------------- 3 files changed, 3659 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/89/46589/2 updated (065209a71 -> 81599b3db)

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/89/46589/2 in repository toolchain/jenkins-scripts. discards 065209a71 round-robin-notify.sh (gnu_print_result): Add configure/make [...] discards 41591de5c round-robin-notify.sh (release_gcc_testresults_files): Fix ha [...] discards d0a72f55b round-robin.sh (build_abe): Do not send results for "fast_che [...] adds 81599b3db round-robin.sh (build_abe): Do not send results for "fast_che [...] 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 (065209a71) \ N -- N -- N refs/changes/89/46589/2 (81599b3db) 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 | 605 ------------ round-robin-bisect.sh | 686 -------------- round-robin-notify.sh | 2362 ----------------------------------------------- 3 files changed, 3653 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/89/46589/1 updated (971e1abce -> 1bb9f17e6)

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/89/46589/1 in repository toolchain/jenkins-scripts. discards 971e1abce round-robin-notify.sh (gnu_print_result): Add configure/make [...] discards 6bce9f834 round-robin.sh (build_abe): Enable maitainer_mode in precommi [...] new 1bb9f17e6 round-robin.sh (build_abe): Enable maitainer_mode in precommi [...] 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 (971e1abce) \ N -- N -- N refs/changes/89/46589/1 (1bb9f17e6) 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: round-robin-baseline.sh | 605 ------------ round-robin-bisect.sh | 686 -------------- round-robin-notify.sh | 2362 ----------------------------------------------- 3 files changed, 3653 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/89/46489/1 updated (c314c891e -> 85152c4fd)

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/89/46489/1 in repository toolchain/jenkins-scripts. discards c314c891e precommit-ssh-apply.sh: Generate email files adds 85152c4fd precommit-ssh-apply.sh: Generate email 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 (c314c891e) \ N -- N -- N refs/changes/89/46489/1 (85152c4fd) 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/89/46289/2 updated (77c75c4b2 -> 03ee6b7bb)

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/89/46289/2 in repository toolchain/jenkins-scripts. discards 77c75c4b2 round-robin-notify.sh: Rename results.compare into results.co [...] discards ef06121f2 tcwg-update-lnt-results.sh: Fix (2) when asking for all ci_pr [...] adds 03ee6b7bb tcwg-update-lnt-results.sh: Fix (2) when asking for all ci_pr [...] 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 (77c75c4b2) \ N -- N -- N refs/changes/89/46289/2 (03ee6b7bb) 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 | 567 ------------ round-robin-bisect.sh | 681 -------------- round-robin-notify.sh | 2248 ----------------------------------------------- 3 files changed, 3496 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/89/46289/1 updated (8a8e643cd -> 641aebe64)

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/89/46289/1 in repository toolchain/jenkins-scripts. discards 8a8e643cd round-robin-notify.sh: Rename results.compare into results.co [...] discards 1ace06997 round-robin.sh (build_abe): Fix thinko adds 641aebe64 round-robin.sh (build_abe): Fix thinko 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 (8a8e643cd) \ N -- N -- N refs/changes/89/46289/1 (641aebe64) 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 | 567 ------------ round-robin-bisect.sh | 681 -------------- round-robin-notify.sh | 2248 ----------------------------------------------- 3 files changed, 3496 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/89/45889/1 updated (c6ec7fa28 -> 9a7b82c5c)

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/89/45889/1 in repository toolchain/jenkins-scripts. discards c6ec7fa28 lnt-utils: fix issue on unexpected core lines adds 9a7b82c5c lnt-utils: fix issue on unexpected core lines 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 (c6ec7fa28) \ N -- N -- N refs/changes/89/45889/1 (9a7b82c5c) 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