Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/67/40167/1 updated (1e69645b1 -> 28eb85694)

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/67/40167/1 in repository toolchain/jenkins-scripts. discards 1e69645b1 tcwg-llvmbots: Move armv7 worker tk1-08 to silent buildmaster new 28eb85694 tcwg-llvmbots: Move armv7 worker tk1-08 to silent buildmaster 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 (1e69645b1) \ N -- N -- N refs/changes/67/40167/1 (28eb85694) 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/67/35567/2 updated (79fd9fd1b -> 9a0cbdc65)

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/67/35567/2 in repository toolchain/jenkins-scripts. discards 79fd9fd1b start-container-docker.sh: Assert that the task parameter has [...] adds 9a0cbdc65 start-container-docker.sh: Assert that the task parameter has [...] 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 (79fd9fd1b) \ N -- N -- N refs/changes/67/35567/2 (9a0cbdc65) 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/67/35567/1 updated (e3d399517 -> 41b525e3b)

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/67/35567/1 in repository toolchain/jenkins-scripts. discards e3d399517 start-container-docker.sh: Assert that the task parameter has [...] new 41b525e3b start-container-docker.sh: Assert that the task parameter has [...] 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 (e3d399517) \ N -- N -- N refs/changes/67/35567/1 (41b525e3b) 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/67/35067/3 updated (5478eca64 -> bbe8f53bd)

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/67/35067/3 in repository toolchain/jenkins-scripts. discards 5478eca64 sanity-check.sh: Scan files in the current working dir adds bbe8f53bd sanity-check.sh: Scan files in the current working dir 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 (5478eca64) \ N -- N -- N refs/changes/67/35067/3 (bbe8f53bd) 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/67/35067/2 updated (c22657318 -> eed6d5339)

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/67/35067/2 in repository toolchain/jenkins-scripts. discards c22657318 sanity-check.sh: Scan files in the current working dir new eed6d5339 sanity-check.sh: Scan files in the current working dir 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 (c22657318) \ N -- N -- N refs/changes/67/35067/2 (eed6d5339) 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/67/35067/1 updated (b0806eaa1 -> 2266d8e5e)

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/67/35067/1 in repository toolchain/jenkins-scripts. discards b0806eaa1 sanity-check.sh: Scan files in the current working dir new 2266d8e5e sanity-check.sh: Scan files in the current working dir 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 (b0806eaa1) \ N -- N -- N refs/changes/67/35067/1 (2266d8e5e) 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/67/34767/3 updated (267b0de16 -> 8c953bbc9)

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/67/34767/3 in repository toolchain/jenkins-scripts. discards 267b0de16 round-robin-bisect.sh: Add Jira issue numbers for tcwg_bmk-ci [...] discards 3d395a131 sanity-check.sh: Add script to shellcheck jenkins-scripts adds 8c953bbc9 sanity-check.sh: Add script to shellcheck jenkins-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 (267b0de16) \ N -- N -- N refs/changes/67/34767/3 (8c953bbc9) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/67/34767/2 updated (b51ade7cd -> 47d5f6c91)

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/67/34767/2 in repository toolchain/jenkins-scripts. discards b51ade7cd round-robin-bisect.sh: Add Jira issue numbers for tcwg_bmk-ci [...] discards a85ebcfbb sanity-check.sh: Allow local users to check individual scripts new 47d5f6c91 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 (b51ade7cd) \ N -- N -- N refs/changes/67/34767/2 (47d5f6c91) 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: 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/67/34767/1 updated (fce82688b -> 47d5f6c91)

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/67/34767/1 in repository toolchain/jenkins-scripts. discards fce82688b round-robin-bisect.sh: Add Jira issue numbers for tcwg_bmk-ci [...] discards a85ebcfbb sanity-check.sh: Allow local users to check individual scripts new 47d5f6c91 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 (fce82688b) \ N -- N -- N refs/changes/67/34767/1 (47d5f6c91) 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: round-robin-bisect.sh | 618 -------------------------------------------------- 1 file changed, 618 deletions(-) delete mode 100755 round-robin-bisect.sh -- 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/67/34667/1 updated (512d79ce1 -> 385406abc)

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/67/34667/1 in repository toolchain/jenkins-scripts. discards 512d79ce1 docker-run.sh: Make sure $prefix is initialized adds 385406abc docker-run.sh: Make sure $prefix is initialized 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 (512d79ce1) \ N -- N -- N refs/changes/67/34667/1 (385406abc) 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