Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/35/41735/1 updated (5a5dbead2 -> 896200f91)

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/35/41735/1 in repository toolchain/jenkins-scripts. discards 5a5dbead2 tcwg-report-stale-rr-jobs.sh: double timeslot for relaease jobs adds 896200f91 tcwg-report-stale-rr-jobs.sh: double timeslot for relaease jobs 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 (5a5dbead2) \ N -- N -- N refs/changes/35/41735/1 (896200f91) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/41635/2 updated (e54ac9c17 -> 82ca3c28c)

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/35/41635/2 in repository toolchain/jenkins-scripts. discards e54ac9c17 tcwg-update-llvmbot-containers.sh: Remove unused parts of the [...] adds 82ca3c28c tcwg-update-llvmbot-containers.sh: Remove unused parts of the [...] 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 (e54ac9c17) \ N -- N -- N refs/changes/35/41635/2 (82ca3c28c) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/41635/1 updated (d2cbe845b -> d0e0ae78c)

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/35/41635/1 in repository toolchain/jenkins-scripts. discards d2cbe845b tcwg-update-llvmbot-containers.sh: Remove unused parts of the [...] new d0e0ae78c tcwg-update-llvmbot-containers.sh: Remove unused parts of the [...] 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 (d2cbe845b) \ N -- N -- N refs/changes/35/41635/1 (d0e0ae78c) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/40735/2 updated (3b0978f33 -> fc44b30bd)

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/35/40735/2 in repository toolchain/jenkins-scripts. discards 3b0978f33 stale-jobs : Add a first automatic analysis adds fc44b30bd stale-jobs : Add a first automatic analysis 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 (3b0978f33) \ N -- N -- N refs/changes/35/40735/2 (fc44b30bd) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/40735/1 updated (1be9c429d -> e54a6a16e)

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/35/40735/1 in repository toolchain/jenkins-scripts. discards 1be9c429d stale-jobs : Add a first automatic analysis new e54a6a16e stale-jobs : Add a first automatic analysis 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 (1be9c429d) \ N -- N -- N refs/changes/35/40735/1 (e54a6a16e) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/39535/2 updated (6ba959831 -> c19473fed)

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/35/39535/2 in repository toolchain/jenkins-scripts. discards 6ba959831 round-robin.sh: Switch GDB CI loops back to using abe:tested adds c19473fed round-robin.sh: Switch GDB CI loops back to using abe:tested 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 (6ba959831) \ N -- N -- N refs/changes/35/39535/2 (c19473fed) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/39535/1 updated (74a72b0d6 -> be417b9b8)

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/35/39535/1 in repository toolchain/jenkins-scripts. discards 74a72b0d6 round-robin.sh: Switch GDB CI loops back to using abe:tested new be417b9b8 round-robin.sh: Switch GDB CI loops back to using abe:tested 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 (74a72b0d6) \ N -- N -- N refs/changes/35/39535/1 (be417b9b8) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/39235/1 updated (ebf7321c7 -> 749003541)

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/35/39235/1 in repository toolchain/jenkins-scripts. discards ebf7321c7 tcwg_gnu-build.sh: Build binutils for native GCC testing adds 749003541 tcwg_gnu-build.sh: Build binutils for native GCC testing 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 (ebf7321c7) \ N -- N -- N refs/changes/35/39235/1 (749003541) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/39035/1 updated (28c69cfc4 -> 9f319185d)

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/35/39035/1 in repository toolchain/jenkins-scripts. discards 28c69cfc4 tcwg-update-llvmbot-containers: Correct patterns for choosing [...] adds 9f319185d tcwg-update-llvmbot-containers: Correct patterns for choosing [...] 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 (28c69cfc4) \ N -- N -- N refs/changes/35/39035/1 (9f319185d) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/35/35435/2 updated (c0e26f302 -> 0692a0fbb)

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/35/35435/2 in repository toolchain/jenkins-scripts. discards c0e26f302 round-robin-bisect.sh: Fix shellcheck warnings discards f83ab343d round-robin*.sh: Pass component URL alongside component branches adds 0692a0fbb round-robin*.sh: Pass component URL alongside component branches 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 (c0e26f302) \ N -- N -- N refs/changes/35/35435/2 (0692a0fbb) 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 | 651 -------------------------------------------------- 1 file changed, 651 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, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024