Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/97/43597/1 updated (8436d680c -> 88ef5f15b)

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/97/43597/1 in repository toolchain/jenkins-scripts. discards 8436d680c generate-cimonitor-dashboard.py: improve diag new 88ef5f15b generate-cimonitor-dashboard.py: improve diag 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 (8436d680c) \ N -- N -- N refs/changes/97/43597/1 (88ef5f15b) 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/97/43397/4 updated (bc353a0e5 -> 6ed213634)

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/97/43397/4 in repository toolchain/jenkins-scripts. discards bc353a0e5 tcwg_bmk-build.sh: check if previous and new bmk results are [...] adds 6ed213634 tcwg_bmk-build.sh: check if previous and new bmk results are [...] 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 (bc353a0e5) \ N -- N -- N refs/changes/97/43397/4 (6ed213634) 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/97/43397/3 updated (accf4362e -> 64d32c903)

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/97/43397/3 in repository toolchain/jenkins-scripts. discards accf4362e tcwg_bmk-build.sh: check if previous and new bmk results are [...] new 64d32c903 tcwg_bmk-build.sh: check if previous and new bmk results are [...] 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 (accf4362e) \ N -- N -- N refs/changes/97/43397/3 (64d32c903) 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/97/43397/2 updated (657f62319 -> 537d001c7)

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/97/43397/2 in repository toolchain/jenkins-scripts. discards 657f62319 tcwg_bmk-build.sh: check if previous and new bmk results are [...] adds 537d001c7 tcwg_bmk-build.sh: check if previous and new bmk results are [...] 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 (657f62319) \ N -- N -- N refs/changes/97/43397/2 (537d001c7) 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/97/43397/1 updated (b191143d0 -> ec3c7cc60)

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/97/43397/1 in repository toolchain/jenkins-scripts. discards b191143d0 tcwg_bmk-build.sh: check if previous and new bmk results are [...] new ec3c7cc60 tcwg_bmk-build.sh: check if previous and new bmk results are [...] 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 (b191143d0) \ N -- N -- N refs/changes/97/43397/1 (ec3c7cc60) 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/97/43297/1 updated (85de0b85b -> eb9851262)

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/97/43297/1 in repository toolchain/jenkins-scripts. discards 85de0b85b tcwg-generate-source-cache.sh: Add bmk-scripts and AOSP manifest adds eb9851262 tcwg-generate-source-cache.sh: Add bmk-scripts and AOSP manifest 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 (85de0b85b) \ N -- N -- N refs/changes/97/43297/1 (eb9851262) 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/97/42797/2 updated (aeb35932d -> e15313860)

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/97/42797/2 in repository toolchain/jenkins-scripts. discards aeb35932d Use lldb-server mode for running lldb tests adds e15313860 Use lldb-server mode for running lldb tests 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 (aeb35932d) \ N -- N -- N refs/changes/97/42797/2 (e15313860) 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/97/42797/1 updated (926f2a4fb -> f0a925e2f)

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/97/42797/1 in repository toolchain/jenkins-scripts. discards 926f2a4fb Use lldb-server mode for running lldb tests adds f0a925e2f Use lldb-server mode for running lldb tests 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 (926f2a4fb) \ N -- N -- N refs/changes/97/42797/1 (f0a925e2f) 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/97/42697/2 updated (459835758 -> 03e20b1ba)

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/97/42697/2 in repository toolchain/jenkins-scripts. discards 459835758 wrappers/*: Remove bin/my<tool> workaround adds 03e20b1ba wrappers/*: Remove bin/my<tool> workaround 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 (459835758) \ N -- N -- N refs/changes/97/42697/2 (03e20b1ba) 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/97/42697/1 updated (50bbf5798 -> a2d1af875)

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/97/42697/1 in repository toolchain/jenkins-scripts. discards 50bbf5798 wrappers/*: Remove bin/my<tool> workaround new a2d1af875 wrappers/*: Remove bin/my<tool> workaround 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 (50bbf5798) \ N -- N -- N refs/changes/97/42697/1 (a2d1af875) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024