Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/33/44233/1 updated (2965b8713 -> f6b6fcb05)

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/33/44233/1 in repository toolchain/jenkins-scripts. discards 2965b8713 round-robin-notify.sh: Minimal fix for jira card format discards 17ddf03b6 round-robin-notify.sh: remove artifacts mail and dashboard dir new f6b6fcb05 round-robin-notify.sh: remove artifacts mail and dashboard 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 (2965b8713) \ N -- N -- N refs/changes/33/44233/1 (f6b6fcb05) 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 | 633 -------------------------- round-robin-notify.sh | 1195 ------------------------------------------------- 2 files changed, 1828 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.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/33/43733/2 updated (cb22a5faf -> 9eb963336)

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/33/43733/2 in repository toolchain/jenkins-scripts. discards cb22a5faf tcwg_bmk-build.sh: handle samples-variability even if emtpy c [...] adds 9eb963336 tcwg_bmk-build.sh: handle samples-variability even if emtpy c [...] 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 (cb22a5faf) \ N -- N -- N refs/changes/33/43733/2 (9eb963336) 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/33/43733/1 updated (fa2136d27 -> bb52dfc37)

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/33/43733/1 in repository toolchain/jenkins-scripts. discards fa2136d27 tcwg_bmk-build.sh: handle samples-variability even if emtpy c [...] new bb52dfc37 tcwg_bmk-build.sh: handle samples-variability even if emtpy c [...] 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 (fa2136d27) \ N -- N -- N refs/changes/33/43733/1 (bb52dfc37) 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/33/43533/1 updated (0351a379c -> 02d1abda9)

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/33/43533/1 in repository toolchain/jenkins-scripts. discards 0351a379c wrappers/install-wrappers.sh: Use git sha1 as hash for ccache [...] adds 02d1abda9 wrappers/install-wrappers.sh: Use git sha1 as hash for ccache [...] 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 (0351a379c) \ N -- N -- N refs/changes/33/43533/1 (02d1abda9) 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/33/43333/2 updated (d5b110b44 -> d81988ec9)

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/33/43333/2 in repository toolchain/jenkins-scripts. discards d5b110b44 tcwg_aosp-build.sh: rename base-artifacts branch adds d81988ec9 tcwg_aosp-build.sh: rename base-artifacts branch 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 (d5b110b44) \ N -- N -- N refs/changes/33/43333/2 (d81988ec9) 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/33/43333/1 updated (c03d1ef11 -> 1d0fdef45)

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/33/43333/1 in repository toolchain/jenkins-scripts. discards c03d1ef11 tcwg_aosp-build.sh: rename base-artifacts branch adds 1d0fdef45 tcwg_aosp-build.sh: rename base-artifacts branch 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 (c03d1ef11) \ N -- N -- N refs/changes/33/43333/1 (1d0fdef45) 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/33/42333/5 updated (7c6a5412c -> d3d2cecd5)

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/33/42333/5 in repository toolchain/jenkins-scripts. discards 7c6a5412c dashboard-push-one-branch: Recreate csv results in dashboard- [...] adds d3d2cecd5 dashboard-push-one-branch: Recreate csv results in dashboard- [...] 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 (7c6a5412c) \ N -- N -- N refs/changes/33/42333/5 (d3d2cecd5) 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/33/42333/4 updated (3037f2557 -> 4b726e5b4)

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/33/42333/4 in repository toolchain/jenkins-scripts. discards 3037f2557 dashboard-push-one-branch: Recreate csv results in dashboard- [...] new 4b726e5b4 dashboard-push-one-branch: Recreate csv results in dashboard- [...] 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 (3037f2557) \ N -- N -- N refs/changes/33/42333/4 (4b726e5b4) 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/33/42333/3 updated (c85f53ac6 -> 434929622)

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/33/42333/3 in repository toolchain/jenkins-scripts. discards c85f53ac6 dashboard-push-one-branch: Recreate csv results in dashboard- [...] new 434929622 dashboard-push-one-branch: Recreate csv results in dashboard- [...] 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 (c85f53ac6) \ N -- N -- N refs/changes/33/42333/3 (434929622) 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/33/42333/2 updated (0939542b9 -> 9eafeb7a0)

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/33/42333/2 in repository toolchain/jenkins-scripts. discards 0939542b9 dashboard-push-one-branch.sh: Recreate first csv results if n [...] adds 9eafeb7a0 dashboard-push-one-branch.sh: Recreate first csv results if n [...] 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 (0939542b9) \ N -- N -- N refs/changes/33/42333/2 (9eafeb7a0) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024