Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/88/38188/3 updated (28611f0a7 -> 04c32d0c4)

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/88/38188/3 in repository toolchain/jenkins-scripts. discards 28611f0a7 tcwg-report-stale-rr-branches.sh: New script adds 04c32d0c4 tcwg-report-stale-rr-branches.sh: New 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 (28611f0a7) \ N -- N -- N refs/changes/88/38188/3 (04c32d0c4) 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/88/38188/2 updated (00414569b -> f240112c5)

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/88/38188/2 in repository toolchain/jenkins-scripts. discards 00414569b tcwg-report-stale-rr-branches.sh: New script adds f240112c5 tcwg-report-stale-rr-branches.sh: New 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 (00414569b) \ N -- N -- N refs/changes/88/38188/2 (f240112c5) 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/88/38188/1 updated (d3d0de5c0 -> 4c3aea2cc)

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/88/38188/1 in repository toolchain/jenkins-scripts. discards d3d0de5c0 tcwg-report-stale-rr-branches.sh: New script adds 4c3aea2cc tcwg-report-stale-rr-branches.sh: New 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 (d3d0de5c0) \ N -- N -- N refs/changes/88/38188/1 (4c3aea2cc) 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/88/35388/3 updated (cb9e011ff -> 60d5ba369)

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/88/35388/3 in repository toolchain/jenkins-scripts. discards cb9e011ff round-robin.sh: Simplify "check" logic of build_abe() adds 60d5ba369 round-robin.sh: Simplify "check" logic of build_abe() 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 (cb9e011ff) \ N -- N -- N refs/changes/88/35388/3 (60d5ba369) 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/88/35388/2 updated (836b1e9c2 -> 949af05a3)

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/88/35388/2 in repository toolchain/jenkins-scripts. discards 836b1e9c2 round-robin.sh: Simplify "check" logic of build_abe() adds 949af05a3 round-robin.sh: Simplify "check" logic of build_abe() 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 (836b1e9c2) \ N -- N -- N refs/changes/88/35388/2 (949af05a3) 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/88/35388/1 updated (72f9a42ce -> 1f4de019a)

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/88/35388/1 in repository toolchain/jenkins-scripts. discards 72f9a42ce round-robin.sh: Simplify "check" logic of build_abe() adds 1f4de019a round-robin.sh: Simplify "check" logic of build_abe() 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 (72f9a42ce) \ N -- N -- N refs/changes/88/35388/1 (1f4de019a) 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/88/32988/4 updated (29412604c -> 9df7e8afb)

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/88/32988/4 in repository toolchain/jenkins-scripts. discards 29412604c tcwg_bmk-build.sh: Move results.csv to step's artifacts adds 9df7e8afb tcwg_bmk-build.sh: Move results.csv to step's artifacts 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 (29412604c) \ N -- N -- N refs/changes/88/32988/4 (9df7e8afb) 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/88/32988/3 updated (20ea5cad2 -> ab95508ed)

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/88/32988/3 in repository toolchain/jenkins-scripts. discards 20ea5cad2 tcwg_bmk-build.sh: Move results.csv to step's artifacts adds ab95508ed tcwg_bmk-build.sh: Move results.csv to step's artifacts 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 (20ea5cad2) \ N -- N -- N refs/changes/88/32988/3 (ab95508ed) 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/88/32988/2 updated (7dbb1fbab -> ce87b2a47)

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/88/32988/2 in repository toolchain/jenkins-scripts. discards 7dbb1fbab tcwg_bmk-build.sh: Move results.csv to step's artifacts adds ce87b2a47 tcwg_bmk-build.sh: Move results.csv to step's artifacts 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 (7dbb1fbab) \ N -- N -- N refs/changes/88/32988/2 (ce87b2a47) 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/88/32988/1 updated (76a2192cc -> 447ad8cc8)

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/88/32988/1 in repository toolchain/jenkins-scripts. discards 76a2192cc tcwg_bmk-build.sh: Move results.csv to step's artifacts adds 447ad8cc8 tcwg_bmk-build.sh: Move results.csv to step's artifacts 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 (76a2192cc) \ N -- N -- N refs/changes/88/32988/1 (447ad8cc8) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024