Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/93/46193/1 updated (49aa9e279 -> 2523755f4)

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/93/46193/1 in repository toolchain/jenkins-scripts. discards 49aa9e279 tcwg_gnu-config.sh: Add long_config adds 2523755f4 tcwg_gnu-config.sh: Add long_config 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 (49aa9e279) \ N -- N -- N refs/changes/93/46193/1 (2523755f4) 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/93/46093/1 updated (aef14977d -> b9194e230)

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/93/46093/1 in repository toolchain/jenkins-scripts. discards aef14977d round-robin-notify.sh (create_jira_card): Add more flexibility discards a24953f92 round-robin-notify.sh (print_jira_template_card): Update and [...] discards c5e448bd7 round-robin-notify.sh (print_jira_template_card): Remove outd [...] discards 82a54ab83 tcwg_gnu-build.sh: Workaround rewrite artifact adds b9194e230 tcwg_gnu-build.sh: Workaround rewrite artifact 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 (aef14977d) \ N -- N -- N refs/changes/93/46093/1 (b9194e230) 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 | 1956 ----------------------------------------------- 3 files changed, 3204 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/93/45893/5 updated (c50764581 -> 4fab5281d)

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/93/45893/5 in repository toolchain/jenkins-scripts. discards c50764581 testresults2jenkins.sh: New script, called from build_abe adds 4fab5281d testresults2jenkins.sh: New script, called from build_abe 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 (c50764581) \ N -- N -- N refs/changes/93/45893/5 (4fab5281d) 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/93/45893/4 updated (2872ba584 -> 6d4785c15)

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/93/45893/4 in repository toolchain/jenkins-scripts. discards 2872ba584 testresults2jenkins.sh: New script, called from build_abe adds 6d4785c15 testresults2jenkins.sh: New script, called from build_abe 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 (2872ba584) \ N -- N -- N refs/changes/93/45893/4 (6d4785c15) 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/93/45893/3 updated (d37fbf048 -> bac197146)

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/93/45893/3 in repository toolchain/jenkins-scripts. discards d37fbf048 testresults2jenkins.sh: New script, called from build_abe adds bac197146 testresults2jenkins.sh: New script, called from build_abe 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 (d37fbf048) \ N -- N -- N refs/changes/93/45893/3 (bac197146) 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/93/45893/2 updated (56057274c -> eb78850f1)

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/93/45893/2 in repository toolchain/jenkins-scripts. discards 56057274c testresults2jenkins.sh: New script, called from build_abe adds eb78850f1 testresults2jenkins.sh: New script, called from build_abe 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 (56057274c) \ N -- N -- N refs/changes/93/45893/2 (eb78850f1) 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/93/45893/1 updated (519039a80 -> a975caebf)

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/93/45893/1 in repository toolchain/jenkins-scripts. discards 519039a80 testresults2jenkins.sh: New script, called from build_abe adds a975caebf testresults2jenkins.sh: New script, called from build_abe 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 (519039a80) \ N -- N -- N refs/changes/93/45893/1 (a975caebf) 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/93/45793/2 updated (618846b85 -> 0b3c95064)

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/93/45793/2 in repository toolchain/jenkins-scripts. discards 618846b85 Revert "tcwg_gnu-config.sh (settings_for_ci_project_and_confi [...] adds 0b3c95064 Revert "tcwg_gnu-config.sh (settings_for_ci_project_and_confi [...] 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 (618846b85) \ N -- N -- N refs/changes/93/45793/2 (0b3c95064) 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/93/45793/1 updated (d3ce9872a -> aee8710fa)

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/93/45793/1 in repository toolchain/jenkins-scripts. discards d3ce9872a Revert "tcwg_gnu-config.sh (settings_for_ci_project_and_confi [...] adds aee8710fa Revert "tcwg_gnu-config.sh (settings_for_ci_project_and_confi [...] 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 (d3ce9872a) \ N -- N -- N refs/changes/93/45793/1 (aee8710fa) 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/93/45693/1 updated (d62253a6c -> bc04190e5)

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/93/45693/1 in repository toolchain/jenkins-scripts. discards d62253a6c round-robin-baseline.sh (rewrite_single_revision): Remove old [...] discards 954596f6a round-robin-notify.sh: Use global rr[metric_id] instead of re [...] discards 4c92ddc61 round-robin-baseline.sh (rewrite_single_revision): Workaround [...] discards 9802ad8df round-robin-baseline.sh (rewrite_single_revision): Add workaround discards 10559c860 jenkins-helpers.sh (git_annex_download): Do not ignore rsync failure adds bc04190e5 jenkins-helpers.sh (git_annex_download): Do not ignore rsync failure 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 (d62253a6c) \ N -- N -- N refs/changes/93/45693/1 (bc04190e5) 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 | 516 -------------- round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1736 ----------------------------------------------- 3 files changed, 2907 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