Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/36/34836/3 updated (547338b67 -> 0a1c849f4)

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/36/34836/3 in repository toolchain/jenkins-scripts. discards 547338b67 round-robin-bisect.sh: * Show builds in last good/first bad [...] discards 9870685df sanity-check.sh: Allow local users to check individual scripts adds 0a1c849f4 sanity-check.sh: Allow local users to check individual scripts 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 (547338b67) \ N -- N -- N refs/changes/36/34836/3 (0a1c849f4) 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 | 628 -------------------------------------------------- 1 file changed, 628 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

[toolchain/jenkins-scripts] reference refs/changes/36/34836/2 updated (2746e7066 -> 0a1c849f4)

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/36/34836/2 in repository toolchain/jenkins-scripts. discards 2746e7066 round-robin-bisect.sh: * Show builds in last good/first bad [...] discards 9870685df sanity-check.sh: Allow local users to check individual scripts adds 0a1c849f4 sanity-check.sh: Allow local users to check individual scripts 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 (2746e7066) \ N -- N -- N refs/changes/36/34836/2 (0a1c849f4) 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 | 621 -------------------------------------------------- 1 file changed, 621 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

[toolchain/jenkins-scripts] reference refs/changes/36/34836/1 updated (27d4487fe -> 0a1c849f4)

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/36/34836/1 in repository toolchain/jenkins-scripts. discards 27d4487fe round-robin-bisect.sh: Show builds in last good/first bad order discards 9870685df sanity-check.sh: Allow local users to check individual scripts adds 0a1c849f4 sanity-check.sh: Allow local users to check individual scripts 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 (27d4487fe) \ N -- N -- N refs/changes/36/34836/1 (0a1c849f4) 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 | 619 -------------------------------------------------- 1 file changed, 619 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

[toolchain/jenkins-scripts] reference refs/changes/36/30536/1 updated (2913f9f0a -> f468ced67)

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/36/30536/1 in repository toolchain/jenkins-scripts. discards 2913f9f0a tcwg-cleanup-stale-containers.sh: Report failure to kill stal [...] adds f468ced67 tcwg-cleanup-stale-containers.sh: Report failure to kill stal [...] 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 (2913f9f0a) \ N -- N -- N refs/changes/36/30536/1 (f468ced67) 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/36/29836/3 updated (a87534dd6 -> 3c526e36e)

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/36/29836/3 in repository toolchain/jenkins-scripts. discards a87534dd6 round-robin.h: Record correct sha1 of base-artifacts/ in manifest adds 3c526e36e round-robin.h: Record correct sha1 of base-artifacts/ in 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 (a87534dd6) \ N -- N -- N refs/changes/36/29836/3 (3c526e36e) 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/36/29836/2 updated (462c0bd59 -> c9a2a8686)

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/36/29836/2 in repository toolchain/jenkins-scripts. discards 462c0bd59 round-robin.h: Record correct sha1 of base-artifacts/ in manifest adds c9a2a8686 round-robin.h: Record correct sha1 of base-artifacts/ in 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 (462c0bd59) \ N -- N -- N refs/changes/36/29836/2 (c9a2a8686) 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/36/29836/1 updated (5bded3027 -> 3a53b028d)

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/36/29836/1 in repository toolchain/jenkins-scripts. discards 5bded3027 round-robin.h: Record correct sha1 of base-artifacts/ in manifest adds 3a53b028d round-robin.h: Record correct sha1 of base-artifacts/ in 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 (5bded3027) \ N -- N -- N refs/changes/36/29836/1 (3a53b028d) 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/36/29436/4 updated (e7f4e1bc3 -> 21172b094)

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/36/29436/4 in repository toolchain/jenkins-scripts. discards e7f4e1bc3 Add timeout and retry utility and use it for git clone and fetch adds 21172b094 Add timeout and retry utility and use it for git clone and fetch 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 (e7f4e1bc3) \ N -- N -- N refs/changes/36/29436/4 (21172b094) 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/36/29436/3 updated (14e57b22e -> 69aaf2ca6)

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/36/29436/3 in repository toolchain/jenkins-scripts. discards 14e57b22e Add timeout and retry utility and use it for git clone and fetch new 69aaf2ca6 Add timeout and retry utility and use it for git clone and fetch 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 (14e57b22e) \ N -- N -- N refs/changes/36/29436/3 (69aaf2ca6) 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/36/29436/2 updated (e4786d8e0 -> 05cdf0cc1)

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/36/29436/2 in repository toolchain/jenkins-scripts. discards e4786d8e0 Add timeout and retry utility and use it for git clone and fetch new 05cdf0cc1 Add timeout and retry utility and use it for git clone and fetch 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 (e4786d8e0) \ N -- N -- N refs/changes/36/29436/2 (05cdf0cc1) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024