Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/78/47178/3 updated (665dbedb5 -> d94438367)

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/78/47178/3 in repository toolchain/jenkins-scripts. discards 665dbedb5 round-robin.sh: use extra_build_parameters for trigger files new d94438367 round-robin.sh: use extra_build_parameters for trigger files 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 (665dbedb5) \ N -- N -- N refs/changes/78/47178/3 (d94438367) 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/78/47178/2 updated (c56e1b8a2 -> 69c84762b)

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/78/47178/2 in repository toolchain/jenkins-scripts. discards c56e1b8a2 round-robin.sh: use extra_build_parameters for trigger files new 69c84762b round-robin.sh: use extra_build_parameters for trigger files 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 (c56e1b8a2) \ N -- N -- N refs/changes/78/47178/2 (69c84762b) 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/78/47178/1 updated (4984b850d -> 4e666d42d)

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/78/47178/1 in repository toolchain/jenkins-scripts. discards 4984b850d round-robin.sh: use extra_build_parameters for trigger files new 4e666d42d round-robin.sh: use extra_build_parameters for trigger files 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 (4984b850d) \ N -- N -- N refs/changes/78/47178/1 (4e666d42d) 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/78/46978/1 updated (61212edbf -> 7bc0d45a3)

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/78/46978/1 in repository toolchain/jenkins-scripts. discards 61212edbf generate-cimonitor-dashboard.py: Diagnostic if a lock file is [...] adds 7bc0d45a3 generate-cimonitor-dashboard.py: Diagnostic if a lock file is [...] 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 (61212edbf) \ N -- N -- N refs/changes/78/46978/1 (7bc0d45a3) 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/78/46178/4 updated (169786c46 -> 39ca06967)

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/78/46178/4 in repository toolchain/jenkins-scripts. discards 169786c46 tcwg-update-lnt-results.sh: new script to update lnt results adds 39ca06967 tcwg-update-lnt-results.sh: new script to update lnt results 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 (169786c46) \ N -- N -- N refs/changes/78/46178/4 (39ca06967) 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/78/46178/3 updated (c5e0fa093 -> 98aa0f40b)

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/78/46178/3 in repository toolchain/jenkins-scripts. discards c5e0fa093 tcwg-update-lnt-results.sh: new script to update lnt results new 98aa0f40b tcwg-update-lnt-results.sh: new script to update lnt results 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 (c5e0fa093) \ N -- N -- N refs/changes/78/46178/3 (98aa0f40b) 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/78/46178/2 updated (eedc97753 -> de5ddb422)

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/78/46178/2 in repository toolchain/jenkins-scripts. discards eedc97753 tcwg-update-lnt-results.sh: new script to update lnt results new de5ddb422 tcwg-update-lnt-results.sh: new script to update lnt results 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 (eedc97753) \ N -- N -- N refs/changes/78/46178/2 (de5ddb422) 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/78/46178/1 updated (c9a153a23 -> da13065e4)

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/78/46178/1 in repository toolchain/jenkins-scripts. discards c9a153a23 tcwg-update-lnt-results.sh: new script to update lnt results new da13065e4 tcwg-update-lnt-results.sh: new script to update lnt results 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 (c9a153a23) \ N -- N -- N refs/changes/78/46178/1 (da13065e4) 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/78/45678/2 updated (954596f6a -> bc04190e5)

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/78/45678/2 in repository toolchain/jenkins-scripts. discards 954596f6a round-robin-notify.sh: Use global rr[metric_id] instead of re [...] discards 4c92ddc61 round-robin-baseline.sh (rewrite_single_revision): Workaround [...] discards 9802ad8df round-robin-baseline.sh (rewrite_single_revision): Add workaround discards 10559c860 jenkins-helpers.sh (git_annex_download): Do not ignore rsync failure adds bc04190e5 jenkins-helpers.sh (git_annex_download): Do not ignore rsync failure 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 (954596f6a) \ N -- N -- N refs/changes/78/45678/2 (bc04190e5) 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-baseline.sh | 499 -------------- round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1736 ----------------------------------------------- 3 files changed, 2890 deletions(-) delete mode 100755 round-robin-baseline.sh 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/78/45678/1 updated (c0172a336 -> 0c9f4f98d)

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/78/45678/1 in repository toolchain/jenkins-scripts. discards c0172a336 round-robin-notify.sh: Use global rr[metric_id] instead of re [...] discards 7a5971879 round-robin-notify.sh: Fix bmk_generate_extra_details discards 08db330b1 tcwg_bmk-build.sh: Test history rewrite on SPEC CPU2006 configs adds 0c9f4f98d tcwg_bmk-build.sh: Test history rewrite on SPEC CPU2006 configs 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 (c0172a336) \ N -- N -- N refs/changes/78/45678/1 (0c9f4f98d) 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-baseline.sh | 477 ------------- round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1736 ----------------------------------------------- 3 files changed, 2868 deletions(-) delete mode 100755 round-robin-baseline.sh 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024