Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/45/42345/2 updated (23473b02e -> 27bbdb096)

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/45/42345/2 in repository toolchain/jenkins-scripts. discards 23473b02e Use compare-results.py instead of csvs2table.py. new 27bbdb096 Use compare-results.py instead of 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 (23473b02e) \ N -- N -- N refs/changes/45/42345/2 (27bbdb096) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/42345/1 updated (d11726b7c -> f6c81c8aa)

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/45/42345/1 in repository toolchain/jenkins-scripts. discards d11726b7c Use compare-results.py instead of csvs2table.py. new f6c81c8aa Use compare-results.py instead of 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 (d11726b7c) \ N -- N -- N refs/changes/45/42345/1 (f6c81c8aa) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/42245/2 updated (808f49ee7 -> 5877ec183)

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/45/42245/2 in repository toolchain/jenkins-scripts. discards 808f49ee7 tcwg_bmk-build.sh: Run VECT benchmark jobs in parallel. adds 5877ec183 tcwg_bmk-build.sh: Run VECT benchmark jobs in parallel. 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 (808f49ee7) \ N -- N -- N refs/changes/45/42245/2 (5877ec183) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/42245/1 updated (3d8c9bfb0 -> cc455e18d)

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/45/42245/1 in repository toolchain/jenkins-scripts. discards 3d8c9bfb0 tcwg_bmk-build.sh: Run VECT benchmark jobs in parallel. new cc455e18d tcwg_bmk-build.sh: Run VECT benchmark jobs in parallel. 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 (3d8c9bfb0) \ N -- N -- N refs/changes/45/42245/1 (cc455e18d) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/41945/1 updated (9af3dd4ca -> 7710359da)

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/45/41945/1 in repository toolchain/jenkins-scripts. discards 9af3dd4ca dashboard.sh: handle TCWG_SQUAD_TOKEN new 7710359da dashboard.sh: handle TCWG_SQUAD_TOKEN 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 (9af3dd4ca) \ N -- N -- N refs/changes/45/41945/1 (7710359da) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/41845/2 updated (d2dcf014b -> 803bedda5)

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/45/41845/2 in repository toolchain/jenkins-scripts. discards d2dcf014b tcwg_bmk-build.sh: Create mail everytime adds 803bedda5 tcwg_bmk-build.sh: Create mail everytime 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 (d2dcf014b) \ N -- N -- N refs/changes/45/41845/2 (803bedda5) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/41845/1 updated (c2b2c386e -> 261d1115c)

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/45/41845/1 in repository toolchain/jenkins-scripts. discards c2b2c386e tcwg_bmk-build.sh: Create mail everytime new 261d1115c tcwg_bmk-build.sh: Create mail everytime 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 (c2b2c386e) \ N -- N -- N refs/changes/45/41845/1 (261d1115c) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/40245/2 updated (32d9cc543 -> f3cd57844)

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/45/40245/2 in repository toolchain/jenkins-scripts. discards 32d9cc543 tcwg_bmk-build.sh: Remove VECT from bmk_cflags. adds f3cd57844 tcwg_bmk-build.sh: Remove VECT from bmk_cflags. 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 (32d9cc543) \ N -- N -- N refs/changes/45/40245/2 (f3cd57844) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/40245/1 updated (945a230ac -> 7f978fd61)

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/45/40245/1 in repository toolchain/jenkins-scripts. discards 945a230ac tcwg_bmk-build.sh: Remove VECT from bmk_cflags. new 7f978fd61 tcwg_bmk-build.sh: Remove VECT from bmk_cflags. 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 (945a230ac) \ N -- N -- N refs/changes/45/40245/1 (7f978fd61) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/39345/1 updated (0604d8b81 -> d970736c0)

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/45/39345/1 in repository toolchain/jenkins-scripts. discards 0604d8b81 round-robin-bisect.sh: Better handle spurious regressions discards 8fcaafa22 tcwg_bmk-build.sh: Fix benchmarking on tcwg-apm-* adds d970736c0 tcwg_bmk-build.sh: Fix benchmarking on tcwg-apm-* 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 (0604d8b81) \ N -- N -- N refs/changes/45/39345/1 (d970736c0) 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 | 848 -------------------------------------------------- 1 file changed, 848 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024