Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/30/30730/2 updated (7b44d0602 -> 2d800210c)

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/30/30730/2 in repository toolchain/jenkins-scripts. discards 7b44d0602 tcwg-update-snapshots_ref.sh: Use tcwg-tk1_32-build label ins [...] adds 2d800210c tcwg-update-snapshots_ref.sh: Use tcwg-tk1_32-build label ins [...] 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 (7b44d0602) \ N -- N -- N refs/changes/30/30730/2 (2d800210c) 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/30/30730/1 updated (fafc16d4b -> 602a2c77f)

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/30/30730/1 in repository toolchain/jenkins-scripts. discards fafc16d4b tcwg-update-snapshots_ref.sh: Use tcwg-tk1_32-build label ins [...] new 602a2c77f tcwg-update-snapshots_ref.sh: Use tcwg-tk1_32-build label ins [...] 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 (fafc16d4b) \ N -- N -- N refs/changes/30/30730/1 (602a2c77f) 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/30/30530/2 updated (f48528653 -> 0f98ad44f)

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/30/30530/2 in repository toolchain/jenkins-scripts. discards f48528653 tcwg_bmk-build.sh: Move results_id to benchmark() adds 0f98ad44f tcwg_bmk-build.sh: Move results_id to benchmark() 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 (f48528653) \ N -- N -- N refs/changes/30/30530/2 (0f98ad44f) 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/30/30530/1 updated (078fad4cc -> b813fd515)

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/30/30530/1 in repository toolchain/jenkins-scripts. discards 078fad4cc tcwg_bmk-build.sh: Move results_id to benchmark() adds b813fd515 tcwg_bmk-build.sh: Move results_id to benchmark() 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 (078fad4cc) \ N -- N -- N refs/changes/30/30530/1 (b813fd515) 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/30/29430/2 updated (1187c164a -> e85b56788)

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/30/29430/2 in repository toolchain/jenkins-scripts. discards 1187c164a tcwg_kernel-build.sh: Make build_abe_1 depend only on ${rr[]} adds e85b56788 tcwg_kernel-build.sh: Make build_abe_1 depend only on ${rr[]} 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 (1187c164a) \ N -- N -- N refs/changes/30/29430/2 (e85b56788) 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/30/29430/1 updated (7dba4ef5e -> dfd96b18d)

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/30/29430/1 in repository toolchain/jenkins-scripts. discards 7dba4ef5e tcwg_kernel-build.sh: Make build_abe_1 depend only on ${rr[]} adds dfd96b18d tcwg_kernel-build.sh: Make build_abe_1 depend only on ${rr[]} 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 (7dba4ef5e) \ N -- N -- N refs/changes/30/29430/1 (dfd96b18d) 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/30/29330/2 updated (571d4039d -> f3c63fe41)

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/30/29330/2 in repository toolchain/jenkins-scripts. discards 571d4039d tcwg_kernel-bisect.sh: Send emails only on successful bisects. discards b207fc2ac Migrate email logic from tcwg_kernel.yaml to tcwg_kernel-bisect.sh. discards bdbf886eb tcwg-update-host-containers.sh, tcwg-start-container.sh: Refa [...] adds f3c63fe41 tcwg-update-host-containers.sh, tcwg-start-container.sh: Refa [...] 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 (571d4039d) \ N -- N -- N refs/changes/30/29330/2 (f3c63fe41) 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: tcwg_kernel-bisect.sh | 220 -------------------------------------------------- 1 file changed, 220 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- 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/30/29330/1 updated (a5c2d2aa0 -> ce794b80b)

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/30/29330/1 in repository toolchain/jenkins-scripts. discards a5c2d2aa0 tcwg_kernel-bisect.sh: Send emails only on successful bisects. discards 148291018 tcwg-update-llvmbot-containers.sh: New job script adds ce794b80b tcwg-update-llvmbot-containers.sh: New job script 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 (a5c2d2aa0) \ N -- N -- N refs/changes/30/29330/1 (ce794b80b) 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: tcwg_kernel-bisect.sh | 220 -------------------------------------------------- 1 file changed, 220 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- 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/30/29230/5 updated (b207fc2ac -> f3c63fe41)

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/30/29230/5 in repository toolchain/jenkins-scripts. discards b207fc2ac Migrate email logic from tcwg_kernel.yaml to tcwg_kernel-bisect.sh. discards bdbf886eb tcwg-update-host-containers.sh, tcwg-start-container.sh: Refa [...] adds f3c63fe41 tcwg-update-host-containers.sh, tcwg-start-container.sh: Refa [...] 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 (b207fc2ac) \ N -- N -- N refs/changes/30/29230/5 (f3c63fe41) 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: tcwg_kernel-bisect.sh | 224 -------------------------------------------------- 1 file changed, 224 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- 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/30/29230/4 updated (584aad18d -> 15bef0aa8)

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/30/29230/4 in repository toolchain/jenkins-scripts. discards 584aad18d Migrate email logic from tcwg_kernel.yaml to tcwg_kernel-bisect.sh. discards 5cbd5427c tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...] adds 15bef0aa8 tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...] 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 (584aad18d) \ N -- N -- N refs/changes/30/29230/4 (15bef0aa8) 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: tcwg_kernel-bisect.sh | 224 -------------------------------------------------- 1 file changed, 224 deletions(-) delete mode 100755 tcwg_kernel-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