Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/36/29436/1 updated (ecea96266 -> ce5e06b85)

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/36/29436/1 in repository toolchain/jenkins-scripts. discards ecea96266 Add timeout and retry utility and use it for git clone and fetch new ce5e06b85 Add timeout and retry utility and use it for git clone and fetch 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 (ecea96266) \ N -- N -- N refs/changes/36/29436/1 (ce5e06b85) 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/35/47135/1 updated (a45a6ca1b -> 68fe93260)

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/35/47135/1 in repository toolchain/jenkins-scripts. discards a45a6ca1b tcwg_chromium-build.sh: ci-autotest on specify on the build adds 68fe93260 tcwg_chromium-build.sh: ci-autotest on specify on the build 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 (a45a6ca1b) \ N -- N -- N refs/changes/35/47135/1 (68fe93260) 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/35/47035/1 updated (f8c5f34f3 -> 5480f7f25)

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/35/47035/1 in repository toolchain/jenkins-scripts. discards f8c5f34f3 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Add [...] adds 5480f7f25 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Add [...] 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 (f8c5f34f3) \ N -- N -- N refs/changes/35/47035/1 (5480f7f25) 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/35/46835/3 updated (2ecf29f6a -> d9cab7bc2)

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/35/46835/3 in repository toolchain/jenkins-scripts. discards 2ecf29f6a lnt-utils.sh: Fix execution_variability adds d9cab7bc2 lnt-utils.sh: Fix execution_variability 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 (2ecf29f6a) \ N -- N -- N refs/changes/35/46835/3 (d9cab7bc2) 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/35/46835/2 updated (16762cdb6 -> 1a92bf4b9)

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/35/46835/2 in repository toolchain/jenkins-scripts. discards 16762cdb6 lnt-utils.sh: Fix execution_variability adds 1a92bf4b9 lnt-utils.sh: Fix execution_variability 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 (16762cdb6) \ N -- N -- N refs/changes/35/46835/2 (1a92bf4b9) 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/35/46835/1 updated (ae0a1736f -> 62d35a826)

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/35/46835/1 in repository toolchain/jenkins-scripts. discards ae0a1736f lnt-utils.sh: Fix execution_variability adds 62d35a826 lnt-utils.sh: Fix execution_variability 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 (ae0a1736f) \ N -- N -- N refs/changes/35/46835/1 (62d35a826) 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/35/46535/1 updated (faf0dfe89 -> 4d22710db)

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/35/46535/1 in repository toolchain/jenkins-scripts. discards faf0dfe89 tcwg-cleanup-stale-results.sh: Deleted as now useless new 4d22710db tcwg-cleanup-stale-results.sh: Deleted as now useless 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 (faf0dfe89) \ N -- N -- N refs/changes/35/46535/1 (4d22710db) 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/35/46435/1 updated (33aa8473c -> 7413a0bda)

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/35/46435/1 in repository toolchain/jenkins-scripts. discards 33aa8473c round-robin-notify.sh: Move handling of TCWG_JIRA_TOKEN to ya [...] discards 01a6781de round-robin-bisect.sh: Handle "only skipped commits left to t [...] discards 76e9cdf84 tcwg-lnt/create_server.sh: Use Linaro LNT repo adds 7413a0bda tcwg-lnt/create_server.sh: Use Linaro LNT repo 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 (33aa8473c) \ N -- N -- N refs/changes/35/46435/1 (7413a0bda) 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 | 686 -------------- round-robin-notify.sh | 2302 ----------------------------------------------- 3 files changed, 3540 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/35/46235/3 updated (7149668cd -> e7515666e)

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/35/46235/3 in repository toolchain/jenkins-scripts. discards 7149668cd round-robin-notify.sh: Generate a publish html file for jenkins job discards 6be09e13f round-robin-notify.sh: Typo discards 94384c3cc lnt-utils.sh: Add git revision infos for the build adds e7515666e lnt-utils.sh: Add git revision infos for the build 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 (7149668cd) \ N -- N -- N refs/changes/35/46235/3 (e7515666e) 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 | 567 ------------- round-robin-bisect.sh | 681 ---------------- round-robin-notify.sh | 2062 ----------------------------------------------- 3 files changed, 3310 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/35/46235/2 updated (049bee45a -> e7515666e)

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/35/46235/2 in repository toolchain/jenkins-scripts. discards 049bee45a round-robin-notify.sh: Generate a publish html file for jenkins job discards 6be09e13f round-robin-notify.sh: Typo discards 94384c3cc lnt-utils.sh: Add git revision infos for the build adds e7515666e lnt-utils.sh: Add git revision infos for the build 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 (049bee45a) \ N -- N -- N refs/changes/35/46235/2 (e7515666e) 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 | 567 ------------- round-robin-bisect.sh | 681 ---------------- round-robin-notify.sh | 2062 ----------------------------------------------- 3 files changed, 3310 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024