Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/63/43263/3 updated (e6775987f -> 9c4e6fe71)

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/63/43263/3 in repository toolchain/jenkins-scripts. discards e6775987f round-robin.sh: Organize build_abe() arguments adds 9c4e6fe71 round-robin.sh: Organize build_abe() arguments 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 (e6775987f) \ N -- N -- N refs/changes/63/43263/3 (9c4e6fe71) 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/63/43263/2 updated (ac43dc7f0 -> 0048b00af)

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/63/43263/2 in repository toolchain/jenkins-scripts. discards ac43dc7f0 round-robin.sh: Organize build_abe() arguments new 0048b00af round-robin.sh: Organize build_abe() arguments 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 (ac43dc7f0) \ N -- N -- N refs/changes/63/43263/2 (0048b00af) 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/63/43263/1 updated (a051fa3c8 -> 9c3bbba29)

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/63/43263/1 in repository toolchain/jenkins-scripts. discards a051fa3c8 round-robin.sh: Organize build_abe() arguments adds 9c3bbba29 round-robin.sh: Organize build_abe() arguments 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 (a051fa3c8) \ N -- N -- N refs/changes/63/43263/1 (9c3bbba29) 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/63/42663/2 updated (588ae85d9 -> 9c48f0dd9)

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/63/42663/2 in repository toolchain/jenkins-scripts. discards 588ae85d9 downstream_patches: adapt patch for spec2017 adds 9c48f0dd9 downstream_patches: adapt patch for spec2017 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 (588ae85d9) \ N -- N -- N refs/changes/63/42663/2 (9c48f0dd9) 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/63/42663/1 updated (2e80b2c23 -> 5df2c980b)

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/63/42663/1 in repository toolchain/jenkins-scripts. discards 2e80b2c23 downstream_patches: adapt patch for spec2017 new 5df2c980b downstream_patches: adapt patch for spec2017 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 (2e80b2c23) \ N -- N -- N refs/changes/63/42663/1 (5df2c980b) 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/63/41663/1 updated (2ce4f13d3 -> 3ca427864)

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/63/41663/1 in repository toolchain/jenkins-scripts. discards 2ce4f13d3 LLDB AArch64 buildbot temporarily disabled new 3ca427864 LLDB AArch64 buildbot temporarily disabled 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 (2ce4f13d3) \ N -- N -- N refs/changes/63/41663/1 (3ca427864) 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/63/39763/2 updated (4af0ea66d -> 8becceb6e)

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/63/39763/2 in repository toolchain/jenkins-scripts. discards 4af0ea66d tcwg_kernel-build.sh (no_regression_p): Simplify, use no_buil [...] adds 8becceb6e tcwg_kernel-build.sh (no_regression_p): Simplify, use no_buil [...] 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 (4af0ea66d) \ N -- N -- N refs/changes/63/39763/2 (8becceb6e) 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/63/39763/1 updated (6c24a9285 -> 1bfa006fb)

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/63/39763/1 in repository toolchain/jenkins-scripts. discards 6c24a9285 tcwg_kernel-build.sh (no_regression_p): Simplify, use no_buil [...] new 1bfa006fb tcwg_kernel-build.sh (no_regression_p): Simplify, use no_buil [...] 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 (6c24a9285) \ N -- N -- N refs/changes/63/39763/1 (1bfa006fb) 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/63/39363/2 updated (b05a0b4c0 -> d5a335796)

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/63/39363/2 in repository toolchain/jenkins-scripts. discards b05a0b4c0 tcwg_bmk-build.sh: Fix LTO benchmarking adds d5a335796 tcwg_bmk-build.sh: Fix LTO benchmarking 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 (b05a0b4c0) \ N -- N -- N refs/changes/63/39363/2 (d5a335796) 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/63/39363/1 updated (f720cd469 -> 8596f0327)

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/63/39363/1 in repository toolchain/jenkins-scripts. discards f720cd469 tcwg_bmk-build.sh: Fix LTO benchmarking adds 8596f0327 tcwg_bmk-build.sh: Fix LTO benchmarking 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 (f720cd469) \ N -- N -- N refs/changes/63/39363/1 (8596f0327) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024