Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/75/44475/1 updated (710033841 -> 4a3902508)

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/44475/1 in repository toolchain/jenkins-scripts. discards 710033841 round-robin-notify.sh (print_commits): Add output from git describe discards 44eac953f round-robin.sh: Add comments describing the sections in xfails.xfail adds 4a3902508 round-robin.sh: Add comments describing the sections in xfails.xfail 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 (710033841) \ N -- N -- N refs/changes/75/44475/1 (4a3902508) 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-bisect.sh | 647 ------------------------- round-robin-notify.sh | 1248 ------------------------------------------------- 2 files changed, 1895 deletions(-) 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/44275/4 updated (583cf9d8b -> 823758ad0)

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/44275/4 in repository toolchain/jenkins-scripts. discards 583cf9d8b round-robin-notify.sh: Exits prematurely if baseline_dir/top_ [...] discards a3ab26eab round-robin-notify.sh: rewrite for readability discards bc88bce5f round-robin.sh (build_abe): Add --check_patch option adds 823758ad0 round-robin.sh (build_abe): Add --check_patch option 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 (583cf9d8b) \ N -- N -- N refs/changes/75/44275/4 (823758ad0) 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-bisect.sh | 647 -------------------------- round-robin-notify.sh | 1226 ------------------------------------------------- 2 files changed, 1873 deletions(-) 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/44275/3 updated (220842767 -> 7f3edfe19)

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/44275/3 in repository toolchain/jenkins-scripts. discards 220842767 round-robin-notify.sh: Exits prematurely if baseline_dir/top_ [...] discards 1812cb222 round-robin-notify.sh: rewrite for readability discards 1b564e14b Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...] adds 7f3edfe19 Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...] 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 (220842767) \ N -- N -- N refs/changes/75/44275/3 (7f3edfe19) 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-bisect.sh | 647 -------------------------- round-robin-notify.sh | 1226 ------------------------------------------------- 2 files changed, 1873 deletions(-) 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/44275/2 updated (364da8325 -> 7f3edfe19)

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/44275/2 in repository toolchain/jenkins-scripts. discards 364da8325 round-robin-notify.sh: Exits prematurely if baseline_dir/top_ [...] discards 1812cb222 round-robin-notify.sh: rewrite for readability discards 1b564e14b Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...] adds 7f3edfe19 Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...] 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 (364da8325) \ N -- N -- N refs/changes/75/44275/2 (7f3edfe19) 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-bisect.sh | 647 -------------------------- round-robin-notify.sh | 1223 ------------------------------------------------- 2 files changed, 1870 deletions(-) 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/44275/1 updated (b0b1d416a -> 7f3edfe19)

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/44275/1 in repository toolchain/jenkins-scripts. discards b0b1d416a round-robin-notify.sh: Exits with a warning if revision of ba [...] discards 1812cb222 round-robin-notify.sh: rewrite for readability discards 1b564e14b Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...] adds 7f3edfe19 Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...] 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 (b0b1d416a) \ N -- N -- N refs/changes/75/44275/1 (7f3edfe19) 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-bisect.sh | 647 -------------------------- round-robin-notify.sh | 1220 ------------------------------------------------- 2 files changed, 1867 deletions(-) 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/44075/2 updated (34aa3e753 -> cc7e7cf03)

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/44075/2 in repository toolchain/jenkins-scripts. discards 34aa3e753 round-robin.sh (update_baseline): Cleanup history of tcwg_gcc [...] adds cc7e7cf03 round-robin.sh (update_baseline): Cleanup history of tcwg_gcc [...] 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 (34aa3e753) \ N -- N -- N refs/changes/75/44075/2 (cc7e7cf03) 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/44075/1 updated (f2f2a6b1d -> 3b5fe0eed)

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/44075/1 in repository toolchain/jenkins-scripts. discards f2f2a6b1d round-robin.sh (update_baseline): Cleanup history of tcwg_gcc [...] new 3b5fe0eed round-robin.sh (update_baseline): Cleanup history of tcwg_gcc [...] 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 (f2f2a6b1d) \ N -- N -- N refs/changes/75/44075/1 (3b5fe0eed) 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/43275/3 updated (211440d77 -> f04a87851)

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/43275/3 in repository toolchain/jenkins-scripts. discards 211440d77 Use output-bmk-results.py. adds f04a87851 Use output-bmk-results.py. 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 (211440d77) \ N -- N -- N refs/changes/75/43275/3 (f04a87851) 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/43275/2 updated (0d3d13ef1 -> e6cc7062f)

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/43275/2 in repository toolchain/jenkins-scripts. discards 0d3d13ef1 Use output-bmk-results.py. new e6cc7062f Use output-bmk-results.py. 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 (0d3d13ef1) \ N -- N -- N refs/changes/75/43275/2 (e6cc7062f) 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/43275/1 updated (1852ac165 -> f46ad8c89)

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/43275/1 in repository toolchain/jenkins-scripts. discards 1852ac165 Use output-bmk-results.py. new f46ad8c89 Use output-bmk-results.py. 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 (1852ac165) \ N -- N -- N refs/changes/75/43275/1 (f46ad8c89) 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