Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/51/39251/1 updated (814679e7c -> 3e7f94f0f)

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/51/39251/1 in repository toolchain/jenkins-scripts. discards 814679e7c round-robin-bisect.sh: Handle flaky tests for more check_* ci [...] discards 4c3e58e44 round-robin-bisect.sh: Update jira settings discards 3833207c2 start-container-docker.sh: Use at most half of RAM on normal [...] new 3e7f94f0f start-container-docker.sh: Use at most half of RAM on normal [...] 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 (814679e7c) \ N -- N -- N refs/changes/51/39251/1 (3e7f94f0f) 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: round-robin-bisect.sh | 828 -------------------------------------------------- 1 file changed, 828 deletions(-) delete mode 100755 round-robin-bisect.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/51/33651/3 updated (19abe8d93 -> 578e702cd)

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/51/33651/3 in repository toolchain/jenkins-scripts. discards 19abe8d93 tcwg_bmk-build.sh: Run only regressed benchmarks during bisection adds 578e702cd tcwg_bmk-build.sh: Run only regressed benchmarks during bisection 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 (19abe8d93) \ N -- N -- N refs/changes/51/33651/3 (578e702cd) 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/51/33651/2 updated (051bbbf03 -> be2a3cbc7)

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/51/33651/2 in repository toolchain/jenkins-scripts. discards 051bbbf03 tcwg_bmk-build.sh: Run only regressed benchmarks during bisection new be2a3cbc7 tcwg_bmk-build.sh: Run only regressed benchmarks during bisection 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 (051bbbf03) \ N -- N -- N refs/changes/51/33651/2 (be2a3cbc7) 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/51/33651/1 updated (a19237c2c -> d84a587d6)

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/51/33651/1 in repository toolchain/jenkins-scripts. discards a19237c2c tcwg_bmk-build.sh: Run only regressed benchmarks during bisection new d84a587d6 tcwg_bmk-build.sh: Run only regressed benchmarks during bisection 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 (a19237c2c) \ N -- N -- N refs/changes/51/33651/1 (d84a587d6) 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/51/33551/3 updated (83f95531c -> 45bf479ca)

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/51/33551/3 in repository toolchain/jenkins-scripts. discards 83f95531c round-robin.sh: Fix "init" mode failing to clone yet-missing [...] adds 45bf479ca round-robin.sh: Fix "init" mode failing to clone yet-missing [...] 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 (83f95531c) \ N -- N -- N refs/changes/51/33551/3 (45bf479ca) 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/51/33551/2 updated (4e41ef9f4 -> e69e5d0db)

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/51/33551/2 in repository toolchain/jenkins-scripts. discards 4e41ef9f4 round-robin.sh: Fix "init" mode failing to clone yet-missing [...] adds e69e5d0db round-robin.sh: Fix "init" mode failing to clone yet-missing [...] 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 (4e41ef9f4) \ N -- N -- N refs/changes/51/33551/2 (e69e5d0db) 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/51/33551/1 updated (b0da181fb -> 6ee7a8e5c)

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/51/33551/1 in repository toolchain/jenkins-scripts. discards b0da181fb round-robin.sh: Fix "init" mode failing to clone yet-missing [...] adds 6ee7a8e5c round-robin.sh: Fix "init" mode failing to clone yet-missing [...] 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 (b0da181fb) \ N -- N -- N refs/changes/51/33551/1 (6ee7a8e5c) 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/51/32851/2 updated (d371c65ca -> 2682bec0c)

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/51/32851/2 in repository toolchain/jenkins-scripts. discards d371c65ca tcwg-benchmark.sh: Simplify parameter passing through ssh adds 2682bec0c tcwg-benchmark.sh: Simplify parameter passing through ssh 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 (d371c65ca) \ N -- N -- N refs/changes/51/32851/2 (2682bec0c) 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/51/32851/1 updated (6f276b338 -> 6cf2257e7)

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/51/32851/1 in repository toolchain/jenkins-scripts. discards 6f276b338 tcwg-benchmark.sh: Simplify parameter passing through ssh adds 6cf2257e7 tcwg-benchmark.sh: Simplify parameter passing through ssh 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 (6f276b338) \ N -- N -- N refs/changes/51/32851/1 (6cf2257e7) 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/51/32051/2 updated (6a81bd343 -> 13624f64c)

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/51/32051/2 in repository toolchain/jenkins-scripts. discards 6a81bd343 tcwg-update-llvmbot-containers.sh: Fix undefined array error adds 13624f64c tcwg-update-llvmbot-containers.sh: Fix undefined array error 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 (6a81bd343) \ N -- N -- N refs/changes/51/32051/2 (13624f64c) 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