Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/09/35709/1 updated (f76096084 -> ca7d74d61)

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/09/35709/1 in repository toolchain/jenkins-scripts. discards f76096084 tcwg-start-container.sh: Handle containers stuck in restart loop adds ca7d74d61 tcwg-start-container.sh: Handle containers stuck in restart loop 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 (f76096084) \ N -- N -- N refs/changes/09/35709/1 (ca7d74d61) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/35309/2 updated (1d70568f3 -> 0cc054d4f)

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/09/35309/2 in repository toolchain/jenkins-scripts. discards 1d70568f3 round-robin.sh (build_abe): Pass "--disable update" to ABE adds 0cc054d4f round-robin.sh (build_abe): Pass "--disable update" to 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 (1d70568f3) \ N -- N -- N refs/changes/09/35309/2 (0cc054d4f) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/35309/1 updated (671c45951 -> cb4ec6878)

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/09/35309/1 in repository toolchain/jenkins-scripts. discards 671c45951 round-robin.sh (build_abe): Pass "--disable update" to ABE new cb4ec6878 round-robin.sh (build_abe): Pass "--disable update" to 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 (671c45951) \ N -- N -- N refs/changes/09/35309/1 (cb4ec6878) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/33509/1 updated (4318caa69 -> eef97c798)

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/09/33509/1 in repository toolchain/jenkins-scripts. discards 4318caa69 round-robin.sh: Fix print_updated_components() adds eef97c798 round-robin.sh: Fix print_updated_components() 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 (4318caa69) \ N -- N -- N refs/changes/09/33509/1 (eef97c798) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/32809/3 updated (4cbfdb512 -> 71a68f300)

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/09/32809/3 in repository toolchain/jenkins-scripts. discards 4cbfdb512 tcwg-benchmark-results.sh: Upload more results to jenkins artifacts adds 71a68f300 tcwg-benchmark-results.sh: Upload more results to jenkins 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 (4cbfdb512) \ N -- N -- N refs/changes/09/32809/3 (71a68f300) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/32809/2 updated (565c94c85 -> fde592225)

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/09/32809/2 in repository toolchain/jenkins-scripts. discards 565c94c85 tcwg-benchmark-results.sh: Upload more results to jenkins artifacts adds fde592225 tcwg-benchmark-results.sh: Upload more results to jenkins 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 (565c94c85) \ N -- N -- N refs/changes/09/32809/2 (fde592225) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/32809/1 updated (1bce4c07a -> 74a6498a2)

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/09/32809/1 in repository toolchain/jenkins-scripts. discards 1bce4c07a tcwg-benchmark-results.sh: Upload more results to jenkins artifacts adds 74a6498a2 tcwg-benchmark-results.sh: Upload more results to jenkins 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 (1bce4c07a) \ N -- N -- N refs/changes/09/32809/1 (74a6498a2) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/31309/1 updated (d54cde947 -> 8e0a01738)

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/09/31309/1 in repository toolchain/jenkins-scripts. discards d54cde947 tcwg_bmk-build.sh: Add a delay to tcwg-benchmark waiting loop adds 8e0a01738 tcwg_bmk-build.sh: Add a delay to tcwg-benchmark waiting loop 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 (d54cde947) \ N -- N -- N refs/changes/09/31309/1 (8e0a01738) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/30909/2 updated (2fd1e2bcf -> fd1c5787b)

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/09/30909/2 in repository toolchain/jenkins-scripts. discards 2fd1e2bcf docker-run.sh, jenkins-helpers.sh: Fix use of flock adds fd1c5787b docker-run.sh, jenkins-helpers.sh: Fix use of flock 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 (2fd1e2bcf) \ N -- N -- N refs/changes/09/30909/2 (fd1c5787b) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/30909/1 updated (fafbc979b -> a78462f3b)

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/09/30909/1 in repository toolchain/jenkins-scripts. discards fafbc979b docker-run.sh, jenkins-helpers.sh: Fix use of flock new a78462f3b docker-run.sh, jenkins-helpers.sh: Fix use of flock 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 (fafbc979b) \ N -- N -- N refs/changes/09/30909/1 (a78462f3b) 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.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024