Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/30/47030/4 updated (af9c9bb40 -> 02e7ab9df)

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/30/47030/4 in repository toolchain/jenkins-scripts. discards af9c9bb40 tcwg-update-lnt-results.sh: Remove previous reports adds 02e7ab9df tcwg-update-lnt-results.sh: Remove previous reports 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 (af9c9bb40) \ N -- N -- N refs/changes/30/47030/4 (02e7ab9df) 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/30/47030/3 updated (b811099b0 -> f5fc3851e)

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/30/47030/3 in repository toolchain/jenkins-scripts. discards b811099b0 tcwg-update-lnt-results.sh: Remove previous reports adds f5fc3851e tcwg-update-lnt-results.sh: Remove previous reports 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 (b811099b0) \ N -- N -- N refs/changes/30/47030/3 (f5fc3851e) 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/30/47030/2 updated (70d47ffd4 -> e975bac33)

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/30/47030/2 in repository toolchain/jenkins-scripts. discards 70d47ffd4 tcwg-update-lnt-results.sh: Remove previous reports adds e975bac33 tcwg-update-lnt-results.sh: Remove previous reports 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 (70d47ffd4) \ N -- N -- N refs/changes/30/47030/2 (e975bac33) 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/30/47030/1 updated (d05f8b39a -> 7f34d1ccf)

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/30/47030/1 in repository toolchain/jenkins-scripts. discards d05f8b39a tcwg-update-lnt-results.sh: Remove previous reports new 7f34d1ccf tcwg-update-lnt-results.sh: Remove previous reports 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 (d05f8b39a) \ N -- N -- N refs/changes/30/47030/1 (7f34d1ccf) 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/30/46430/1 updated (abf7ddb68 -> 94ca382cd)

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/30/46430/1 in repository toolchain/jenkins-scripts. discards abf7ddb68 round-robin-baseline.sh: Small fix discards a6ee76c46 tcwg-report-stale-rr-jobs.sh: optimize the fetches, because t [...] adds 94ca382cd tcwg-report-stale-rr-jobs.sh: optimize the fetches, because t [...] 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 (abf7ddb68) \ N -- N -- N refs/changes/30/46430/1 (94ca382cd) 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 | 552 ----------- round-robin-bisect.sh | 681 -------------- round-robin-notify.sh | 2313 ----------------------------------------------- 3 files changed, 3546 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/30/45730/6 updated (de4cfe2e7 -> c2ba2f7c0)

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/30/45730/6 in repository toolchain/jenkins-scripts. discards de4cfe2e7 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Move [...] adds c2ba2f7c0 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Move [...] 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 (de4cfe2e7) \ N -- N -- N refs/changes/30/45730/6 (c2ba2f7c0) 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/30/45730/5 updated (d4dba86f6 -> 6f412b803)

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/30/45730/5 in repository toolchain/jenkins-scripts. discards d4dba86f6 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Move [...] adds 6f412b803 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Move [...] 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 (d4dba86f6) \ N -- N -- N refs/changes/30/45730/5 (6f412b803) 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/30/45730/4 updated (986078581 -> 18ce24921)

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/30/45730/4 in repository toolchain/jenkins-scripts. discards 986078581 tcwg_gnu-config.sh (settings_for_ci_project_and_target): Move [...] adds 18ce24921 tcwg_gnu-config.sh (settings_for_ci_project_and_target): Move [...] 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 (986078581) \ N -- N -- N refs/changes/30/45730/4 (18ce24921) 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/30/45730/3 updated (0fb56dbc5 -> 9955b455f)

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/30/45730/3 in repository toolchain/jenkins-scripts. discards 0fb56dbc5 tcwg_gnu-config.sh (settings_for_ci_project_and_target): Move [...] adds 9955b455f tcwg_gnu-config.sh (settings_for_ci_project_and_target): Move [...] 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 (0fb56dbc5) \ N -- N -- N refs/changes/30/45730/3 (9955b455f) 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/30/45730/2 updated (3b4432504 -> 33607cce8)

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/30/45730/2 in repository toolchain/jenkins-scripts. discards 3b4432504 jenkins-helpers.sh (settings_for_ci_project_and_target): Move [...] adds 33607cce8 jenkins-helpers.sh (settings_for_ci_project_and_target): Move [...] 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 (3b4432504) \ N -- N -- N refs/changes/30/45730/2 (33607cce8) 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