Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/38/42538/2 updated (633d024c6 -> 7749c5a3c)

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/38/42538/2 in repository toolchain/jenkins-scripts. discards 633d024c6 tcwg_bmk-build.sh: no try to compare benchmark results if build fail adds 7749c5a3c tcwg_bmk-build.sh: no try to compare benchmark results if build fail 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 (633d024c6) \ N -- N -- N refs/changes/38/42538/2 (7749c5a3c) 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/38/42538/1 updated (ace307c26 -> ad399dc2b)

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/38/42538/1 in repository toolchain/jenkins-scripts. discards ace307c26 tcwg_bmk-build.sh: no try to compare benchmark results if build fail new ad399dc2b tcwg_bmk-build.sh: no try to compare benchmark results if build fail 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 (ace307c26) \ N -- N -- N refs/changes/38/42538/1 (ad399dc2b) 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/38/42438/1 updated (750b568ec -> 0ecca0df8)

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/38/42438/1 in repository toolchain/jenkins-scripts. discards 750b568ec round-robin.sh: default dashboard mode is relative results ar [...] adds 0ecca0df8 round-robin.sh: default dashboard mode is relative results ar [...] 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 (750b568ec) \ N -- N -- N refs/changes/38/42438/1 (0ecca0df8) 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/38/42038/3 updated (0b1ba4e21 -> 138210297)

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/38/42038/3 in repository toolchain/jenkins-scripts. discards 0b1ba4e21 Make "git reset --hard" quiet adds 138210297 Make "git reset --hard" quiet 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 (0b1ba4e21) \ N -- N -- N refs/changes/38/42038/3 (138210297) 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/38/42038/2 updated (ba561d296 -> af94370cc)

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/38/42038/2 in repository toolchain/jenkins-scripts. discards ba561d296 Make "git reset --hard" quiet adds af94370cc Make "git reset --hard" quiet 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 (ba561d296) \ N -- N -- N refs/changes/38/42038/2 (af94370cc) 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/38/42038/1 updated (92ccdaec2 -> 9b8d0f4d9)

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/38/42038/1 in repository toolchain/jenkins-scripts. discards 92ccdaec2 Make "git reset --hard" quiet new 9b8d0f4d9 Make "git reset --hard" quiet 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 (92ccdaec2) \ N -- N -- N refs/changes/38/42038/1 (9b8d0f4d9) 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/38/41938/2 updated (282986c43 -> 4ec2d9967)

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/38/41938/2 in repository toolchain/jenkins-scripts. discards 282986c43 round-robin-bisect.sh: Remove notification code discards 293ab3e8a round-robin.sh: create_mail_dir: Fix adds 4ec2d9967 round-robin.sh: create_mail_dir: Fix 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 (282986c43) \ N -- N -- N refs/changes/38/41938/2 (4ec2d9967) 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 | 622 -------------------------------------------------- 1 file changed, 622 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

[toolchain/jenkins-scripts] reference refs/changes/38/41938/1 updated (5d8c6ab1e -> 9b44cf5f2)

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/38/41938/1 in repository toolchain/jenkins-scripts. discards 5d8c6ab1e round-robin-bisect.sh: Remove notification code discards 3c3e1fd84 round-robin*.sh: Fix notification on a new regression adds 9b44cf5f2 round-robin*.sh: Fix notification on a new regression 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 (5d8c6ab1e) \ N -- N -- N refs/changes/38/41938/1 (9b44cf5f2) 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 | 622 -------------------------------------------------- 1 file changed, 622 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

[toolchain/jenkins-scripts] reference refs/changes/38/41838/1 updated (8d0783f72 -> 4dfafa790)

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/38/41838/1 in repository toolchain/jenkins-scripts. discards 8d0783f72 round-robin.sh: Fix bisect test builds adds 4dfafa790 round-robin.sh: Fix bisect test builds 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 (8d0783f72) \ N -- N -- N refs/changes/38/41838/1 (4dfafa790) 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/38/41738/3 updated (fd4680103 -> 77ac19d3d)

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/38/41738/3 in repository toolchain/jenkins-scripts. discards fd4680103 tcwg-report-stale-rr-jobs.sh: add no change in sources automa [...] adds 77ac19d3d tcwg-report-stale-rr-jobs.sh: add no change in sources automa [...] 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 (fd4680103) \ N -- N -- N refs/changes/38/41738/3 (77ac19d3d) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024