Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/13/44613/2 updated (a91f2cf04 -> f87dcca44)

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/13/44613/2 in repository toolchain/jenkins-scripts. discards a91f2cf04 round-robin-notify.sh: Restrict publishing of benchmark source discards 879ff353d round-robin-notify.sh: Rework posting of jira comments discards 5cbcc54cf round-robin-notify.sh: Create jira card for every interesting commit discards 0fc893f2f round-robin.sh: Fix "ERROR: case (4) in check_regression" errors adds f87dcca44 round-robin.sh: Fix "ERROR: case (4) in check_regression" errors 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 (a91f2cf04) \ N -- N -- N refs/changes/13/44613/2 (f87dcca44) 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 | 166 ----- round-robin-bisect.sh | 653 -------------------- round-robin-notify.sh | 1532 ----------------------------------------------- 3 files changed, 2351 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/13/44613/1 updated (41b4c422c -> f87dcca44)

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/13/44613/1 in repository toolchain/jenkins-scripts. discards 41b4c422c round-robin-notify.sh: Restrict publishing of benchmark source discards 9173f66d7 round-robin-notify.sh: Rework posting of jira comments discards 5cbcc54cf round-robin-notify.sh: Create jira card for every interesting commit discards 0fc893f2f round-robin.sh: Fix "ERROR: case (4) in check_regression" errors adds f87dcca44 round-robin.sh: Fix "ERROR: case (4) in check_regression" errors 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 (41b4c422c) \ N -- N -- N refs/changes/13/44613/1 (f87dcca44) 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 | 166 ----- round-robin-bisect.sh | 653 -------------------- round-robin-notify.sh | 1532 ----------------------------------------------- 3 files changed, 2351 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/13/44513/3 updated (78e472690 -> e0de27077)

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/13/44513/3 in repository toolchain/jenkins-scripts. discards 78e472690 pw-apply.sh: Handle merged patch series adds e0de27077 pw-apply.sh: Handle merged patch series 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 (78e472690) \ N -- N -- N refs/changes/13/44513/3 (e0de27077) 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/13/44513/2 updated (e0e6d083b -> cb47bbd8a)

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/13/44513/2 in repository toolchain/jenkins-scripts. discards e0e6d083b pw-apply.sh: Handle merged patch series new cb47bbd8a pw-apply.sh: Handle merged patch series 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 (e0e6d083b) \ N -- N -- N refs/changes/13/44513/2 (cb47bbd8a) 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/13/44513/1 updated (f8395bbd9 -> e84840a4d)

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/13/44513/1 in repository toolchain/jenkins-scripts. discards f8395bbd9 pw-apply.sh: Handle merged patch series new e84840a4d pw-apply.sh: Handle merged patch series 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 (f8395bbd9) \ N -- N -- N refs/changes/13/44513/1 (e84840a4d) 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/13/44413/2 updated (d99966788 -> 296387d7e)

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/13/44413/2 in repository toolchain/jenkins-scripts. discards d99966788 Store differences between compare-results.py and csvs2table.py. adds 296387d7e Store differences between compare-results.py and csvs2table.py. 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 (d99966788) \ N -- N -- N refs/changes/13/44413/2 (296387d7e) 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/13/44413/1 updated (5c40535d4 -> 5caf80af0)

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/13/44413/1 in repository toolchain/jenkins-scripts. discards 5c40535d4 Store differences between compare-results.py and csvs2table.py. new 5caf80af0 Store differences between compare-results.py and csvs2table.py. 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 (5c40535d4) \ N -- N -- N refs/changes/13/44413/1 (5caf80af0) 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/13/43813/2 updated (2c12171b7 -> 557ea2f82)

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/13/43813/2 in repository toolchain/jenkins-scripts. discards 2c12171b7 round-robin-notify.sh: rename few functions discards 90e3f5f05 round-robin-notify.sh: Can now use round-robin-notify.sh on a [...] adds 557ea2f82 round-robin-notify.sh: Can now use round-robin-notify.sh on a [...] 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 (2c12171b7) \ N -- N -- N refs/changes/13/43813/2 (557ea2f82) 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 | 627 -------------------------- round-robin-notify.sh | 1173 ------------------------------------------------- 2 files changed, 1800 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/13/43813/1 updated (dba5b8161 -> f7f73a8fd)

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/13/43813/1 in repository toolchain/jenkins-scripts. discards dba5b8161 round-robin-notify.sh: rename few functions discards 0408532df round-robin-notify.sh: Can now use round-robin-notify.sh on a [...] adds f7f73a8fd round-robin-notify.sh: Can now use round-robin-notify.sh on a [...] 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 (dba5b8161) \ N -- N -- N refs/changes/13/43813/1 (f7f73a8fd) 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 | 627 -------------------------- round-robin-notify.sh | 1173 ------------------------------------------------- 2 files changed, 1800 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/13/42613/1 updated (aebd01b81 -> 5bc80b721)

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/13/42613/1 in repository toolchain/jenkins-scripts. discards aebd01b81 tcwg_bmk-build.sh: switch experimental flang test to fortran only adds 5bc80b721 tcwg_bmk-build.sh: switch experimental flang test to fortran only 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 (aebd01b81) \ N -- N -- N refs/changes/13/42613/1 (5bc80b721) 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024