Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/53/45853/1 updated (ffda9fc5e -> 398b71ed5)

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/53/45853/1 in repository toolchain/jenkins-scripts. discards ffda9fc5e generate-cimonitor-dashboard.py: Fix automatic diagnostic adds 398b71ed5 generate-cimonitor-dashboard.py: Fix automatic diagnostic 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 (ffda9fc5e) \ N -- N -- N refs/changes/53/45853/1 (398b71ed5) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45753/2 updated (3aaddac35 -> a4c133cac)

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/53/45753/2 in repository toolchain/jenkins-scripts. discards 3aaddac35 tcwg-update-llvmbot-containers.sh: Add silent flang libcxx bot adds a4c133cac tcwg-update-llvmbot-containers.sh: Add silent flang libcxx bot 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 (3aaddac35) \ N -- N -- N refs/changes/53/45753/2 (a4c133cac) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45753/1 updated (59fec2ee1 -> a902de1b6)

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/53/45753/1 in repository toolchain/jenkins-scripts. discards 59fec2ee1 tcwg-update-llvmbot-containers.sh: Add silent flang libcxx bot new a902de1b6 tcwg-update-llvmbot-containers.sh: Add silent flang libcxx bot 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 (59fec2ee1) \ N -- N -- N refs/changes/53/45753/1 (a902de1b6) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45653/2 updated (6c061ffa5 -> 87e17e401)

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/53/45653/2 in repository toolchain/jenkins-scripts. discards 6c061ffa5 tcwg-bmk-build.sh (no_regression_p): Update assert adds 87e17e401 tcwg-bmk-build.sh (no_regression_p): Update assert 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 (6c061ffa5) \ N -- N -- N refs/changes/53/45653/2 (87e17e401) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45653/1 updated (30c1dae3b -> 1d794b1d2)

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/53/45653/1 in repository toolchain/jenkins-scripts. discards 30c1dae3b tcwg-bmk-build.sh (no_regression_p): Update assert new 1d794b1d2 tcwg-bmk-build.sh (no_regression_p): Update assert 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 (30c1dae3b) \ N -- N -- N refs/changes/53/45653/1 (1d794b1d2) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45353/2 updated (00b2e8b38 -> f0567bb00)

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/53/45353/2 in repository toolchain/jenkins-scripts. discards 00b2e8b38 pw-report.sh: Update links to artifacts adds f0567bb00 pw-report.sh: Update links to artifacts 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 (00b2e8b38) \ N -- N -- N refs/changes/53/45353/2 (f0567bb00) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45353/1 updated (fd892228b -> 5e9dbece2)

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/53/45353/1 in repository toolchain/jenkins-scripts. discards fd892228b pw-report.sh: Update links to artifacts new 5e9dbece2 pw-report.sh: Update links to artifacts 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 (fd892228b) \ N -- N -- N refs/changes/53/45353/1 (5e9dbece2) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45253/2 updated (146e3b504 -> 3de51ca69)

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/53/45253/2 in repository toolchain/jenkins-scripts. discards 146e3b504 round-robin-notify.sh (gnu_print_result): Do not print out em [...] discards ea0efb4f1 round-robin.sh (create_trigger_files): Fix typo adds 3de51ca69 round-robin.sh (create_trigger_files): 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 (146e3b504) \ N -- N -- N refs/changes/53/45253/2 (3de51ca69) 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 | 1518 ----------------------------------------------- 3 files changed, 2581 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45253/1 updated (f1eeff3eb -> 7efdc03f4)

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/53/45253/1 in repository toolchain/jenkins-scripts. discards f1eeff3eb round-robin-notify.sh (gnu_print_result): Do not print out em [...] discards 934531cfc round-robin.sh: Start bisection from top of branch, rather th [...] adds 7efdc03f4 round-robin.sh: Start bisection from top of branch, rather th [...] 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 (f1eeff3eb) \ N -- N -- N refs/changes/53/45253/1 (7efdc03f4) 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 | 1514 ----------------------------------------------- 3 files changed, 2577 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/45053/1 updated (3a2957287 -> db91ca43f)

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/53/45053/1 in repository toolchain/jenkins-scripts. discards 3a2957287 pw-*.sh: Remove handling of "queued" bundle adds db91ca43f pw-*.sh: Remove handling of "queued" bundle 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 (3a2957287) \ N -- N -- N refs/changes/53/45053/1 (db91ca43f) 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.

11 months, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024