Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/80/43380/1 updated (2a905542a -> 1838aaf67)

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/80/43380/1 in repository toolchain/jenkins-scripts. discards 2a905542a tcwg_aosp-build.sh: Make "repo sync" a bit more robust adds 1838aaf67 tcwg_aosp-build.sh: Make "repo sync" a bit more robust 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 (2a905542a) \ N -- N -- N refs/changes/80/43380/1 (1838aaf67) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/42880/1 updated (13172efee -> 68e790729)

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/80/42880/1 in repository toolchain/jenkins-scripts. discards 13172efee tcwg-report-ci-status.sh: Fixup after jenkins upgrade adds 68e790729 tcwg-report-ci-status.sh: Fixup after jenkins upgrade 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 (13172efee) \ N -- N -- N refs/changes/80/42880/1 (68e790729) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/42680/2 updated (244114949 -> fa85dd131)

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/80/42680/2 in repository toolchain/jenkins-scripts. discards 244114949 round-robin.sh (reset_artifacts): Allow initialization of bas [...] adds fa85dd131 round-robin.sh (reset_artifacts): Allow initialization of bas [...] 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 (244114949) \ N -- N -- N refs/changes/80/42680/2 (fa85dd131) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/42680/1 updated (f58e45dd8 -> 9f9947450)

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/80/42680/1 in repository toolchain/jenkins-scripts. discards f58e45dd8 round-robin.sh (reset_artifacts): Allow initialization of bas [...] adds 9f9947450 round-robin.sh (reset_artifacts): Allow initialization of bas [...] 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 (f58e45dd8) \ N -- N -- N refs/changes/80/42680/1 (9f9947450) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/42180/1 updated (ae3f78ac6 -> 5931daa10)

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/80/42180/1 in repository toolchain/jenkins-scripts. discards ae3f78ac6 round-robin.sh: Typo in print_results_date adds 5931daa10 round-robin.sh: Typo in print_results_date 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 (ae3f78ac6) \ N -- N -- N refs/changes/80/42180/1 (5931daa10) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/41980/1 updated (8b49daac2 -> 1554b9f7d)

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/80/41980/1 in repository toolchain/jenkins-scripts. discards 8b49daac2 round-robin.sh: Improve mail subject adds 1554b9f7d round-robin.sh: Improve mail subject 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 (8b49daac2) \ N -- N -- N refs/changes/80/41980/1 (1554b9f7d) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/41780/1 updated (45165caf2 -> b7e33f449)

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/80/41780/1 in repository toolchain/jenkins-scripts. discards 45165caf2 tcwg-benchmark-results.sh: Fix path for results.csv adds b7e33f449 tcwg-benchmark-results.sh: Fix path for results.csv 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 (45165caf2) \ N -- N -- N refs/changes/80/41780/1 (b7e33f449) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/41680/3 updated (39dd5096c -> 3a098cbb4)

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/80/41680/3 in repository toolchain/jenkins-scripts. discards 39dd5096c tcwg-llvm-release.sh: Fix git-ref adds 3a098cbb4 tcwg-llvm-release.sh: Fix git-ref 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 (39dd5096c) \ N -- N -- N refs/changes/80/41680/3 (3a098cbb4) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/41680/2 updated (889dcf8fb -> 20eedb4cd)

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/80/41680/2 in repository toolchain/jenkins-scripts. discards 889dcf8fb tcwg-llvm-release.sh: Fix git-ref new 20eedb4cd tcwg-llvm-release.sh: Fix git-ref 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 (889dcf8fb) \ N -- N -- N refs/changes/80/41680/2 (20eedb4cd) 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, 6 months

[toolchain/jenkins-scripts] reference refs/changes/80/41680/1 updated (4ebdf14e2 -> d34514553)

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/80/41680/1 in repository toolchain/jenkins-scripts. discards 4ebdf14e2 tcwg-llvm-release.sh: Fix git-ref new d34514553 tcwg-llvm-release.sh: Fix git-ref 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 (4ebdf14e2) \ N -- N -- N refs/changes/80/41680/1 (d34514553) 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, 6 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024