Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/21/41121/1 updated (1411d348a -> f581bab88)

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/21/41121/1 in repository toolchain/jenkins-scripts. discards 1411d348a tcwg-update-host-container: setup connection to localhost adds f581bab88 tcwg-update-host-container: setup connection to localhost 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 (1411d348a) \ N -- N -- N refs/changes/21/41121/1 (f581bab88) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/39721/1 updated (f96366a48 -> 3c229ac8f)

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/21/39721/1 in repository toolchain/jenkins-scripts. discards f96366a48 tcwg_bmk-build.sh: Make email formatting more consistent adds 3c229ac8f tcwg_bmk-build.sh: Make email formatting more consistent 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 (f96366a48) \ N -- N -- N refs/changes/21/39721/1 (3c229ac8f) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/39221/1 updated (a804ea62c -> 0afec70c5)

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/21/39221/1 in repository toolchain/jenkins-scripts. discards a804ea62c round-robin.sh: Add a workaround for avoiding running TSan te [...] adds 0afec70c5 round-robin.sh: Add a workaround for avoiding running TSan te [...] 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 (a804ea62c) \ N -- N -- N refs/changes/21/39221/1 (0afec70c5) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/34921/2 updated (59177150a -> 93c34ddc3)

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/21/34921/2 in repository toolchain/jenkins-scripts. discards 59177150a Dummy commit to test CI. new 93c34ddc3 Dummy commit to test CI. 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 (59177150a) \ N -- N -- N refs/changes/21/34921/2 (93c34ddc3) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/34921/1 updated (feb5eacdc -> 6f1526bef)

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/21/34921/1 in repository toolchain/jenkins-scripts. discards feb5eacdc Dummy commit to test CI. new 6f1526bef Dummy commit to test CI. 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 (feb5eacdc) \ N -- N -- N refs/changes/21/34921/1 (6f1526bef) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/34721/1 updated (b30e0e44d -> df2def6e5)

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/21/34721/1 in repository toolchain/jenkins-scripts. discards b30e0e44d docker-run.sh: Add "--dryrun N" command-line option new df2def6e5 docker-run.sh: Add "--dryrun N" command-line option 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 (b30e0e44d) \ N -- N -- N refs/changes/21/34721/1 (df2def6e5) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/32721/2 updated (8fa33bd75 -> b0d122130)

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/21/32721/2 in repository toolchain/jenkins-scripts. discards 8fa33bd75 jenkins-helpers.sh: Don't require $WORKSPACE set for "build" [...] adds b0d122130 jenkins-helpers.sh: Don't require $WORKSPACE set for "build" [...] 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 (8fa33bd75) \ N -- N -- N refs/changes/21/32721/2 (b0d122130) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/32721/1 updated (333da27af -> da28b9545)

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/21/32721/1 in repository toolchain/jenkins-scripts. discards 333da27af jenkins-helpers.sh: Don't require $WORKSPACE set for "build" [...] adds da28b9545 jenkins-helpers.sh: Don't require $WORKSPACE set for "build" [...] 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 (333da27af) \ N -- N -- N refs/changes/21/32721/1 (da28b9545) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/32621/2 updated (e532a62ee -> 329f1a1f8)

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/21/32621/2 in repository toolchain/jenkins-scripts. discards e532a62ee tcwg_bmk-build.sh: Fix pattern. adds 329f1a1f8 tcwg_bmk-build.sh: Fix pattern. 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 (e532a62ee) \ N -- N -- N refs/changes/21/32621/2 (329f1a1f8) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/21/32621/1 updated (8ddda3d8b -> 45d3e2b21)

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/21/32621/1 in repository toolchain/jenkins-scripts. discards 8ddda3d8b tcwg_bmk-build.sh: Fix pattern. new 45d3e2b21 tcwg_bmk-build.sh: Fix pattern. 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 (8ddda3d8b) \ N -- N -- N refs/changes/21/32621/1 (45d3e2b21) 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, 1 week

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024