Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/75/46575/2 updated (a39df41b8 -> 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/75/46575/2 in repository toolchain/jenkins-scripts. 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 (a39df41b8) \ N -- N -- N refs/changes/75/46575/2 (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: -- 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/75/46575/1 updated (bda94af9e -> cd6e82814)

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/75/46575/1 in repository toolchain/jenkins-scripts. discards bda94af9e tcwg_gnu-build.sh: Upgrading version for LNT dashboard information new cd6e82814 tcwg_gnu-build.sh: Upgrading version for LNT dashboard information 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 (bda94af9e) \ N -- N -- N refs/changes/75/46575/1 (cd6e82814) 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/75/46375/4 updated (86e90f701 -> 430d33e7c)

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/75/46375/4 in repository toolchain/jenkins-scripts. discards 86e90f701 round-robin-notify.sh (generate_readme): Print list of files [...] discards 612fd815a tcwg-lnt: Add patch to change color in daily report adds 430d33e7c tcwg-lnt: Add patch to change color in daily report 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 (86e90f701) \ N -- N -- N refs/changes/75/46375/4 (430d33e7c) 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 | 2306 ----------------------------------------------- 3 files changed, 3554 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/75/46375/3 updated (d8f70636e -> 430d33e7c)

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/75/46375/3 in repository toolchain/jenkins-scripts. discards d8f70636e round-robin-notify.sh (generate_readme): Print list of files [...] discards 1274e86ee round-robin-notify.sh (release_gcc_testresults_files): Rely o [...] discards 612fd815a tcwg-lnt: Add patch to change color in daily report adds 430d33e7c tcwg-lnt: Add patch to change color in daily report 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 (d8f70636e) \ N -- N -- N refs/changes/75/46375/3 (430d33e7c) 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 | 2315 ----------------------------------------------- 3 files changed, 3563 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/75/46375/2 updated (e80474f58 -> 62494a99a)

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/75/46375/2 in repository toolchain/jenkins-scripts. discards e80474f58 round-robin-notify.sh (generate_readme): Print list of files [...] discards 4527162ef round-robin-notify.sh (release_gcc_testresults_files): Rely o [...] discards dd0f2d7c4 round-robin-notify.sh: Point directly to BUILD_URL/artifact/a [...] discards fb752d67b round-robin-notify.sh (release_testresults_files): Call calcu [...] discards 46d25e6d8 round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...] adds 62494a99a round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...] 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 (e80474f58) \ N -- N -- N refs/changes/75/46375/2 (62494a99a) 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 | 2310 ----------------------------------------------- 3 files changed, 3558 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/75/46375/1 updated (65148e6a9 -> 62494a99a)

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/75/46375/1 in repository toolchain/jenkins-scripts. discards 65148e6a9 round-robin-notify.sh (generate_readme): Print list of files [...] discards 6ab144a5c round-robin-notify.sh (release_gcc_testresults_files): Rely o [...] discards dd0f2d7c4 round-robin-notify.sh: Point directly to BUILD_URL/artifact/a [...] discards fb752d67b round-robin-notify.sh (release_testresults_files): Call calcu [...] discards 46d25e6d8 round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...] adds 62494a99a round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...] 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 (65148e6a9) \ N -- N -- N refs/changes/75/46375/1 (62494a99a) 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 | 2308 ----------------------------------------------- 3 files changed, 3556 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/75/46175/2 updated (d031291ef -> a3e252243)

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/75/46175/2 in repository toolchain/jenkins-scripts. discards d031291ef tcwg-report-stale-rr-jobs.sh: more robust in case host key change new a3e252243 tcwg-report-stale-rr-jobs.sh: more robust in case host key change 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 (d031291ef) \ N -- N -- N refs/changes/75/46175/2 (a3e252243) 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/75/46175/1 updated (02fbc6147 -> 48e761585)

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/75/46175/1 in repository toolchain/jenkins-scripts. discards 02fbc6147 tcwg-report-stale-rr-jobs.sh: more robust in case host key change new 48e761585 tcwg-report-stale-rr-jobs.sh: more robust in case host key change 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 (02fbc6147) \ N -- N -- N refs/changes/75/46175/1 (48e761585) 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/75/45475/5 updated (782c88d39 -> 25a69f1ae)

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/75/45475/5 in repository toolchain/jenkins-scripts. discards 782c88d39 tcwg-report-stale-rr-jobs.sh: Adapt tcwg-report-stale-rr-jobs [...] adds 25a69f1ae tcwg-report-stale-rr-jobs.sh: Adapt tcwg-report-stale-rr-jobs [...] 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 (782c88d39) \ N -- N -- N refs/changes/75/45475/5 (25a69f1ae) 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/75/45475/4 updated (1f824a295 -> 04f1f15c9)

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/75/45475/4 in repository toolchain/jenkins-scripts. discards 1f824a295 tcwg-report-stale-rr-jobs.sh: Adapt tcwg-report-stale-rr-jobs [...] new 04f1f15c9 tcwg-report-stale-rr-jobs.sh: Adapt tcwg-report-stale-rr-jobs [...] 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 (1f824a295) \ N -- N -- N refs/changes/75/45475/4 (04f1f15c9) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024