Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/81/42681/2 updated (3a19fa02d -> 988fad5af)

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/81/42681/2 in repository toolchain/jenkins-scripts. discards 3a19fa02d round-robin.sh (clone_repo): Store git info in artifacts for [...] adds 988fad5af round-robin.sh (clone_repo): Store git info in artifacts for [...] 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 (3a19fa02d) \ N -- N -- N refs/changes/81/42681/2 (988fad5af) 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/81/42681/1 updated (a4cd79a15 -> b76b40e94)

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/81/42681/1 in repository toolchain/jenkins-scripts. discards a4cd79a15 round-robin.sh (clone_repo): Store git info in artifacts for [...] adds b76b40e94 round-robin.sh (clone_repo): Store git info in artifacts for [...] 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 (a4cd79a15) \ N -- N -- N refs/changes/81/42681/1 (b76b40e94) 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/81/41981/2 updated (fb2d5f380 -> 2b94ba9c9)

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/81/41981/2 in repository toolchain/jenkins-scripts. discards fb2d5f380 tcwg_bmk-build.sh: Workaround md5sum processing being broken adds 2b94ba9c9 tcwg_bmk-build.sh: Workaround md5sum processing being broken 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 (fb2d5f380) \ N -- N -- N refs/changes/81/41981/2 (2b94ba9c9) 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/81/41981/1 updated (b9b751200 -> 642fbfb7a)

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/81/41981/1 in repository toolchain/jenkins-scripts. discards b9b751200 tcwg_bmk-build.sh: Workaround md5sum processing being broken new 642fbfb7a tcwg_bmk-build.sh: Workaround md5sum processing being broken 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 (b9b751200) \ N -- N -- N refs/changes/81/41981/1 (642fbfb7a) 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/81/41881/2 updated (dd7219b8e -> dc192b6b4)

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/81/41881/2 in repository toolchain/jenkins-scripts. discards dd7219b8e round-robin.sh (create_trigger_files): Fix last_good/first_ba [...] adds dc192b6b4 round-robin.sh (create_trigger_files): Fix last_good/first_ba [...] 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 (dd7219b8e) \ N -- N -- N refs/changes/81/41881/2 (dc192b6b4) 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/81/41881/1 updated (55bbf890f -> 7bed53191)

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/81/41881/1 in repository toolchain/jenkins-scripts. discards 55bbf890f round-robin.sh (create_trigger_files): Fix last_good/first_ba [...] new 7bed53191 round-robin.sh (create_trigger_files): Fix last_good/first_ba [...] 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 (55bbf890f) \ N -- N -- N refs/changes/81/41881/1 (7bed53191) 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/81/39781/2 updated (ae3ef5bd5 -> f823ace19)

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/81/39781/2 in repository toolchain/jenkins-scripts. discards ae3ef5bd5 Use linaro-local/vect-metric/master for vect-metric patch. adds f823ace19 Use linaro-local/vect-metric/master for vect-metric patch. 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 (ae3ef5bd5) \ N -- N -- N refs/changes/81/39781/2 (f823ace19) 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/81/39781/1 updated (b3bd5e74f -> 9ec09eb3c)

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/81/39781/1 in repository toolchain/jenkins-scripts. discards b3bd5e74f Use linaro-local/vect-metric/master for vect-metric patch. new 9ec09eb3c Use linaro-local/vect-metric/master for vect-metric patch. 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 (b3bd5e74f) \ N -- N -- N refs/changes/81/39781/1 (9ec09eb3c) 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/81/39481/2 updated (91b9040b6 -> 642b45f2a)

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/81/39481/2 in repository toolchain/jenkins-scripts. discards 91b9040b6 round-robin-bisect.sh: Handle a row of skipped commits in a b [...] adds 642b45f2a round-robin-bisect.sh: Handle a row of skipped commits in a b [...] 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 (91b9040b6) \ N -- N -- N refs/changes/81/39481/2 (642b45f2a) 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/81/39481/1 updated (9ca8dc3e7 -> 3715f725f)

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/81/39481/1 in repository toolchain/jenkins-scripts. discards 9ca8dc3e7 round-robin-bisect.sh: Handle a row of skipped commits in a b [...] discards 5ae5d906c round-robin-bisect.sh: Rebase on gcc-compare-results:master b [...] discards b69c914ac round-robin.sh (build_abe): Improve check_gdb workaround adds 3715f725f round-robin.sh (build_abe): Improve check_gdb workaround 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 (9ca8dc3e7) \ N -- N -- N refs/changes/81/39481/1 (3715f725f) 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 | 882 -------------------------------------------------- 1 file changed, 882 deletions(-) delete mode 100755 round-robin-bisect.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