Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-norov-defconfig updated (be1064c4ac -> faeae0b21f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-norov-defconfig in repository toolchain/ci/base-artifacts. from be1064c4ac 12: onsuccess: #39: boot: Success after binutils/gcc/qemu: 1 [...] new faeae0b21f 13: onsuccess: #40: boot: Success after binutils/gcc/linux/q [...] 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: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30492 -> 30208 bytes 04-build_abe-stage1/console.log.xz | Bin 68840 -> 68812 bytes 05-build_abe-qemu/console.log.xz | Bin 31740 -> 32340 bytes 06-build_linux/console.log.xz | Bin 3432 -> 3428 bytes 07-boot_linux/console.log.xz | Bin 6220 -> 6248 bytes 08-check_regression/console.log.xz | Bin 3772 -> 4212 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (e701051f18 -> 0a139ac1ba)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards e701051f18 156: onsuccess: #1561: 2: Success after gcc: 2 commits discards 474098c382 155: onsuccess: #1560: 2: Success after gcc: 3 commits discards c3ec7415ed 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards 45fc22228e 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards 4e43f182c1 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards ff307452ec 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards ec5bebf78e 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards 9be971537d 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards 846879ef28 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards 67ff3a4e26 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 5d3883de25 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards fb3f9a3497 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 8c83db740b 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards d84ad0e284 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards d5763be765 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards cd7d5da118 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards ec89210f8f 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 06ea7d005f 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 20b67f2c4d 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 9afda6dd4b 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards e55d086953 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards de9a0fcc04 135: force: #1540: 2: Success after gcc: 23 commits discards 7c01b6bd54 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 8915218eab 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards f3d9465ad8 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards e10abe0291 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 27d3d1538a 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards d2bf1a3f20 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 76b60f63a7 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 29ad0336c5 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 349892f518 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards add8989a73 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 82968a6457 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards f9085add64 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 5bfc551080 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards de85091e2f 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 09155ab3bf 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards ea83da6e3a 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards ec554d9dec 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 39bca18e2a 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards e8bfcd678d 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 3b11cc1c7a 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 707c0b9492 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 2a617bc9ad 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 007d745178 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards e95b07c326 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards dff251bbf0 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 4cc8701716 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 070d5f6dc9 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards b7c5d684f9 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 4600cda9cc 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 3ea54a6c0a 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 3379ef3aa3 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 251992e37d 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards f5cf77dd5c 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 94b02c752c 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 32a22c45ba 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 1312374a1e 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards ecd71a3ced 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 45ae1854e9 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards acfed926ad 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 48fa178cd8 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 2d28c97f09 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 6bd294d838 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 4856f7222a 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 94a8ab704f 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 818a7765a8 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 7e5bae2b84 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 572b7042d6 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 3e25e16a6b 87: onsuccess: 2: Success after gcc: 4 commits discards 6246df0d52 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 68bc211ab7 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 56cef2edc8 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards e55c050f38 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 9649b87639 82: onsuccess: 1: Successful build after gcc: 3 commits discards 9aeb027939 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 8e976d9c96 80: force: 2: Successful build after gcc: 14 commits discards 48a74f9d28 79: onsuccess: 2: Successful build after binutils: 5 commits discards 5deb8226f7 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards d91021ee97 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 57cab9c8cb 76: onsuccess: 2: Successful build after gcc: 12 commits discards 546b82d687 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 5f92bbce73 74: onsuccess: 2: Successful build after baseline build: no [...] discards c10fd27de3 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 055a7babb7 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f8a4a09c74 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 67c57f7656 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards b279aed7c2 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 25c448cca0 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 101d885087 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 71700362cd 66: onsuccess: 2: Successful build after gcc: 9 commits discards c9d9cc9426 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 827b3f26a4 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2d1e6201e7 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8f0f6142ba 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 0f5e3530e8 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards c0cc30c313 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 4c4d68e866 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 0dc4bf72db 58: force: 2: Successful build after gcc: 6 commits discards 8b0e04e5bd 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards b1a761457e 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 3f15454426 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 679d291cfe 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new a77cfe19d7 58: force: 2: Successful build after gcc: 6 commits new f5c07b5e8d 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 9981f63a2a 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new e730583974 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new aee9463c85 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 6d750cde7f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e90d3f850c 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0c903cd1ef 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8ee5a61686 66: onsuccess: 2: Successful build after gcc: 9 commits new fac23a4ae9 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9a0e5b033f 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new f409c3b438 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 00e7000613 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9133658634 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new b1f3040f09 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 24fe3ba09f 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 3f2147f856 74: onsuccess: 2: Successful build after baseline build: no [...] new 0ff3d0db73 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 005446f577 76: onsuccess: 2: Successful build after gcc: 12 commits new 02ba8340ca 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new c06b115f99 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 8ce0757943 79: onsuccess: 2: Successful build after binutils: 5 commits new 5ff5aafa4e 80: force: 2: Successful build after gcc: 14 commits new 5e4646f9f7 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new b0aaa946b4 82: onsuccess: 1: Successful build after gcc: 3 commits new 9ae1072882 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new ee808a0d98 84: onsuccess: 2: Success after binutils/gcc: 15 commits new fddd7ac82f 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 54f4eda1f8 86: onsuccess: 2: Success after binutils/gcc: 10 commits new bb22296f6d 87: onsuccess: 2: Success after gcc: 4 commits new 2fe2fdf9df 88: onsuccess: 2: Success after binutils/gcc: 25 commits new dd3e4627ae 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 49883b166d 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 8bc317b045 91: onsuccess: 2: Success after binutils/gcc: 7 commits new c84e7df8e4 92: onsuccess: 2: Success after binutils/gcc: 9 commits new ed3428c61a 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 05157103ce 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 5e27d66552 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 3b49412232 96: onsuccess: #1452: 2: Success after gcc: 2 commits new dca8e394e1 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 00caf6e150 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new f996ece922 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 3a16ed9c61 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 43341fddac 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 4dc444104d 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new e8e329f4a3 103: onsuccess: #1504: 2: Success after gcc: 2 commits new cfb4e93865 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new e5f30701f6 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 24179d08fa 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 05dc4ca895 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 278a251be8 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 767113a753 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 3c7479bdad 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 2eef63bd9d 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new b80495ddcb 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 6024302eb0 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 07f70d481c 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new ea0cd94dad 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 63dcc1f7d0 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new d02692ebfb 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 3989be41bd 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 1058c9a569 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 51c1ca7ca3 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 17a41dde22 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new c85d7e38da 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new c2cdb1f483 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 9b759f6750 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new a9be3ba568 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 867fea8697 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 5bd51cbe0b 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 5391240abf 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 6fa5882d47 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 582de35e10 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new a6e2a03394 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 429bca8670 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 746b8c460d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new a27d304fc7 134: onsuccess: #1538: 2: Success after binutils: 2 commits new c6b37269ec 135: force: #1540: 2: Success after gcc: 23 commits new a6074c2384 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new ab540777ed 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 6ec362eb6b 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 91e7bdea0c 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 93f7ff0281 140: onsuccess: #1545: 1: Success after gcc: 7 commits new decf274e4c 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new e5de707be6 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 907b23bf3e 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 46b290b1b7 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 2580815625 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 9117e27556 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new 4ce333bf58 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 50f1ed90e8 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new f70c10e4b6 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new caa6a95bd2 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 89f46c2cc6 151: onsuccess: #1556: 2: Success after binutils: 12 commits new 912c36536b 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new b8164c020e 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 233c7d02b6 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new 4a8fb4caea 155: onsuccess: #1560: 2: Success after gcc: 3 commits new 386c5eb531 156: onsuccess: #1561: 2: Success after gcc: 2 commits new 0a139ac1ba 157: onsuccess: #1562: 2: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (e701051f18) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1676 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50828 -> 50088 bytes 05-build_abe-bootstrap/console.log.xz | Bin 464944 -> 462904 bytes 06-check_regression/console.log.xz | Bin 2636 -> 2552 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- manifest.sh | 14 ++++---- 9 files changed, 41 insertions(+), 41 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allmodconfig updated (ab9280e509 -> 855d7daa80)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from ab9280e509 15: onsuccess: #427: boot: Success after linux: 299 commits new 855d7daa80 16: onsuccess: #428: boot: Success after binutils/llvm/linux [...] 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: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1924 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30260 -> 30316 bytes 04-build_kernel_llvm/console.log.xz | Bin 63924 -> 65440 bytes 05-build_abe-qemu/console.log.xz | Bin 31688 -> 31920 bytes 06-build_linux/console.log.xz | Bin 3016 -> 3072 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 2960 -> 4380 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- 17 files changed, 25 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (a882f4e730 -> e983bf3e9c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards a882f4e730 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 58774adb1f 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards fc5fc48993 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 48d55df16a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards e034c5f96b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards f6d7e2e8a2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 41139d194c 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards eb2b668a42 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 54efb27810 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 889681194d 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 6633c37870 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards fce064f1db 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards c439c4a94c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards b9a391e3a7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 93ee7abe0f 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 0c27b588d9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 111319437a 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 7ebf9d5804 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards f4cbabb336 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 4708f044b9 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 75b55f826f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 4db58376ea 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 2549c671f5 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards a36c47fb82 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 02633937aa 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards ba372532b3 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 4bbb3f79a1 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a51d539072 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards ca65df3b26 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 4c78fc981d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 8fce5a14c7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7f98c1bfa7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 6de80566d0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards b7653d7340 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards f339e3633c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 5414124dc7 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 1678eb05fd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 02bd0b232e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards ecef0c6c2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards da6660e8a1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 8ecda5ecfa 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 19dab87b43 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards abdaea57f8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 037e6acccb 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards a2d0a8b2f5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards ee67e17f28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 238d385e60 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards d6f4f738d1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 0b919f121c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 886c27a001 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6dbb07463d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 14da978944 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 8e6e936e42 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f698ec0705 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 6c9117c315 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards f106b3cd1d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards fae1611214 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 88683acb7d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards a56fe2dfd8 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards ddde8d07d5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 13dadffb3d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b6f1b90a08 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 8fa2fe3666 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 54a74a99d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 644d99e5cf 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 25d3bffd77 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e08367dd1a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 698cd6dde8 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards d4daa9a413 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards b3d6bb1a3d 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 6e936d87cd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards d62c49152e 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 23e897cf8b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c3a01f6120 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 77b85d12d0 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fa8c8ae89f 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7d66e1c4d9 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2fb8c62346 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b96f696f82 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a1a47f8568 74: onsuccess: 1: Successful build after linux: 44 commits discards 9627f29912 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards de43a37264 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd5af60c44 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 46d80d9643 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 30d11270a7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 51156f628e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0ffa6796b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a242ea9424 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 45dcfc6a49 65: onsuccess: 1: Successful build after gcc: 4 commits discards 7f682b3b4c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d57abef12b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9c2019cf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards bbcb2ad845 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8984294400 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 39dba10390 59: onsuccess: 1: Successful build after glibc: 2 commits discards 57d05c5b00 58: onsuccess: 1: Successful build after binutils: 2 commits discards a355157ce4 57: onsuccess: 1: Successful build after gcc: 7 commits discards 5c6f11b0c2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9d5b309c6d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb8e007954 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 8ba4b2067a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 18179e6695 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a45dedba1c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 8fcf491a1c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37c3ea4edb 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad3a9801b1 57: onsuccess: 1: Successful build after gcc: 7 commits new 0874c56cb1 58: onsuccess: 1: Successful build after binutils: 2 commits new 5120701f95 59: onsuccess: 1: Successful build after glibc: 2 commits new ccd590fb0b 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 18a606131e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 419b3979cb 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 46f21e916f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d789aa4f6b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 553521013b 65: onsuccess: 1: Successful build after gcc: 4 commits new 877d0960b6 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a465020cbc 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 992f51b0ba 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 547233f33a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new b171334fb3 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 24ea50fb85 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 21091188d3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d18e092599 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 152d9d9c66 74: onsuccess: 1: Successful build after linux: 44 commits new f8115df2ff 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a2b05392fc 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7d906ec025 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ac4902beca 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 869e43cf97 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6bde732342 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 7ed49d5088 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new ef667b98c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new acfcfccd6b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 7240ad26ad 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 22c8849d64 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 698b16abd6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d7f40d2ffe 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new a89e17ebba 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ae85b4b02f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 20006fb903 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9a50fc47c4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 417841b2f0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 96bf0c9a77 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 86cebe779f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 5c6b895a28 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new e5eb880b3a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new db9a4126df 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new f18d52e2db 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 855e449b99 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new e294f9b8db 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 572b4166a4 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 5b0356bcfe 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 78d8007739 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 7940fea132 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 731d4d2da1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a345543f24 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new b078445d22 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new ae312d931c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 5048094191 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 62d2a3628a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 1b5152c93e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new a0ab6a3ad0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new cd9cfc7051 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new ad21ac19a6 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 0257429e1e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 4a97e580f7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new ce3d5ca4ec 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new c0a3db4c85 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 18aae24cec 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 7097a4cae0 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 0df8f7472c 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 0b05186668 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new bc0d1b5253 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new f73aec0706 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new e3693f1d49 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 0235de1faf 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 32c5636dc5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 9310bfa850 128: onsuccess: #1723: 1: Success after linux: 12 commits new d761ce5e29 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a5ba3cd9d1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 790ab8fe09 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a99f3a8bb3 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 3ba26c6a09 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 3b6b94d805 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 8c7c1e6a95 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 9cbeb95bc2 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new fa886ceab0 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 485a62a95d 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new d982bc4ffc 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 07530500c9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new ed3c943398 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 49c1b608d8 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 2dfbc043e5 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 26b7b9040b 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b8fcb121ff 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 4dd8f075bc 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 5dce5766a3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new bd764c03b5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 9dad1db68e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new d8f0723963 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 7ee5182049 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 20a59418bf 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new d9df8af538 153: onsuccess: #1754: 1: Success after gcc: 2 commits new e983bf3e9c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (a882f4e730) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1676 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29860 -> 30000 bytes 04-build_abe-stage1/console.log.xz | Bin 90276 -> 90828 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8920 bytes 07-build_abe-glibc/console.log.xz | Bin 233840 -> 234904 bytes 08-build_abe-stage2/console.log.xz | Bin 224272 -> 224020 bytes 09-build_abe-gdb/console.log.xz | Bin 36944 -> 37184 bytes 10-build_abe-qemu/console.log.xz | Bin 31776 -> 31400 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2816 -> 2736 bytes 13-check_regression/console.log.xz | Bin 5392 -> 5916 bytes 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 57 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2668044 -> 2650704 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2231760 -> 2201416 bytes sumfiles/gcc.sum | 2606 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 890340 -> 893568 bytes sumfiles/gfortran.sum | 70 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201416 -> 201520 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432600 -> 427764 bytes sumfiles/libstdc++.sum | 16 +- 37 files changed, 1541 insertions(+), 1499 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (a1e72573bc -> 1b4e6ed840)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards a1e72573bc 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards a7085f579a 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 7dec13eeac 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards 1a882c2da9 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards cd9fdec514 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards 2a7b355e5a 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards f12c9516ee 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 1763c420ef 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards 1be71f1064 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 4c8a5b47e8 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 68ec4f2419 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 8a68b772fb 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 8620bb10ce 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards d26404a36e 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 5a6c398f0a 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards d97cadd6c1 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 193bec6f3d 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 6617807ae1 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards e8126dfd71 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 98141d0f92 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards b30ebf0be2 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards d41ba945e9 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 6861fcb913 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 03b77b16af 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 0ff466561b 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 5e6269ea5d 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards ca801d9ef6 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 5289bcc881 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards cef6935280 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 41a431ca38 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 4e56e02401 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 53df66618e 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards a36e3d62d9 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 06ef455a0c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 2e31d97564 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 7c2039926a 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 253bffb79f 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 6b3779c7d4 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards a260fa03bc 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards d32d2b606b 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards c291e87033 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards c092c20d68 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 8eeab5251f 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards c2c48d723c 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 668026cfd2 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 442bb3933f 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 3e2ba7ceef 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards b4d0eafde8 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 033c20a89d 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 8b3a05a289 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards a63e9a22e6 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards bb8ebdd697 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards d8093cab93 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 6fa8d9c8b3 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 467765cb6d 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards da138b1c6a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 7800bd0ea6 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 1da3cb0e7b 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards a8576e9fcb 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 77c8345273 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards a31a63307d 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 5d0ce913fe 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 660b26f0f7 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards e4798dfa7a 88: onsuccess: 1: Success after gcc: 20 commits discards 0f65a0c5f7 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards d6852839dd 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards f060576f5c 85: onsuccess: 2: Success after binutils: 4 commits discards 2be6bc8b05 84: onsuccess: 2: Success after gcc: 9 commits discards b1021a374c 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 7dd5207365 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards d857d5a970 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 9a46016725 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards bfb1c2d88e 79: onsuccess: 1: Successful build after gcc: 3 commits discards 1ae55b92d2 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 71daf6a68e 77: force: 2: Successful build after gcc: 32 commits discards 70e6ca2c7d 76: onsuccess: 2: Successful build after binutils: 10 commits discards 085fa7770c 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 361e3513fe 74: onsuccess: 2: Successful build after gcc: 13 commits discards 03978191f0 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 25171fe0c4 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards e074cde162 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6a0c04125d 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 9f1963a59b 69: onsuccess: 2: Successful build after baseline build: no [...] discards a01b9878ee 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 55cfd776ff 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards dde92f4093 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 29bc2db2b8 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 29da6e2c7b 64: onsuccess: 2: Successful build after gcc: 7 commits discards 47fc2ae29f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards eedeab0191 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards db0b41b9fb 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 5a7065f7c2 60: onsuccess: 1: Successful build after gcc: 15 commits discards 24d5162624 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 5fd0efab6c 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 458e9d01df 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 37441dcbf7 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 9fcb5c50c5 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5a6fe7aa00 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 568955a8f8 53: onsuccess: 2: Successful build after gcc: 5 commits discards 258f364da4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards bf7f6a4078 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 90048db548 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 9aa8ce6206 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 3e1c93716d 53: onsuccess: 2: Successful build after gcc: 5 commits new 1b45d9e2e0 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a59e7af402 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 109d8eef0c 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 8d290e9885 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 37c5361ef8 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new ee94ebed57 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new aae0927dff 60: onsuccess: 1: Successful build after gcc: 15 commits new 352cf3aec5 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 29ac06359e 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a51dd92ebc 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 354a98e5ea 64: onsuccess: 2: Successful build after gcc: 7 commits new 5e8b397010 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a11a75f541 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 79e1bf522a 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 63b4032f07 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 41cfdaab7b 69: onsuccess: 2: Successful build after baseline build: no [...] new f92e40c843 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 577711f918 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1655d1ef2d 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new eff9ae4479 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 450922f398 74: onsuccess: 2: Successful build after gcc: 13 commits new 83eaad3613 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new c9bfb520a6 76: onsuccess: 2: Successful build after binutils: 10 commits new e0db0e1980 77: force: 2: Successful build after gcc: 32 commits new 0de204e0f0 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 2dcbbc963f 79: onsuccess: 1: Successful build after gcc: 3 commits new f5b2ce5250 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 1c7009a04f 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 406cae4634 82: onsuccess: 2: Success after binutils/gcc: 26 commits new af2cb9ec31 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 37156a1b1e 84: onsuccess: 2: Success after gcc: 9 commits new 2643786cad 85: onsuccess: 2: Success after binutils: 4 commits new d30b8d8f94 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 00399ce84a 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new f0a9707708 88: onsuccess: 1: Success after gcc: 20 commits new 0ef1872f9f 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 31299c2d99 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 8d32e0dda5 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 2927cfcc76 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 4ea6a148de 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 596e4c30d7 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new f46bcb694e 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new ed9a32d9f6 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 28ab3d1b26 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 43b2c9088b 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 346784d1fa 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new a4efb20664 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 9775b9fc0a 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new b116045e6f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new c3b7ce1e1a 103: onsuccess: #1524: 2: Success after gcc: 2 commits new d710a78b15 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 748b5cd3aa 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 953f73ddfb 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 9f48440542 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new a230d6d546 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 7b1c661bd0 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 253f657e5c 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 42799c67b5 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 12b0a7240d 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 2539794996 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new d18c64c070 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 949ca36951 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 02177a9410 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new e6c33c1099 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 0bacb1b59c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 92173dd6a2 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 1b7acf8616 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 36e731e3ad 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 0f5163c2cf 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 43f1a3e824 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 3cc9a46b55 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new b040ead829 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 345e082341 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new c06502a0b1 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new a8ed03bafa 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 13de00ba41 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 512d7e87d5 130: onsuccess: #1554: 2: Success after gcc: 9 commits new f1a902be4e 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new bdab2ccfe8 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new aa923b6bfb 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 04ab60f274 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new f96f88b4c6 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new cdd86a44f3 136: onsuccess: #1561: 2: Success after binutils: 3 commits new d36aede1dd 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 6c04a12a82 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new d121c4f65f 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 8a8cb4f0a1 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new b2d30ca1a2 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 367e33d46c 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new d69b0a234d 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 396a60dea2 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new f18eadb628 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new c19b85d328 146: onsuccess: #1573: 2: Success after binutils: 7 commits new 48eb86ff78 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new a8cd9efd45 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new fe4265bce4 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new 3a0bda6a65 150: onsuccess: #1577: 2: Success after gcc: 3 commits new d4ca328ec8 151: onsuccess: #1578: 2: Success after gcc: 2 commits new 1b4e6ed840 152: onsuccess: #1579: 2: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (a1e72573bc) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 37588 -> 37704 bytes 05-build_abe-bootstrap/console.log.xz | Bin 270556 -> 268040 bytes 06-check_regression/console.log.xz | Bin 2528 -> 2556 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- manifest.sh | 14 ++++---- 9 files changed, 41 insertions(+), 41 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig updated (ca997e324f -> 9e484fc4ea)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from ca997e324f 12: onsuccess: #370: all: Success after binutils/gcc/linux/q [...] new 9e484fc4ea 13: onsuccess: #371: all: Success after binutils/gcc/linux/q [...] 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: 01-reset_artifacts/console.log.xz | Bin 1684 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29728 -> 29844 bytes 04-build_abe-stage1/console.log.xz | Bin 90820 -> 90504 bytes 05-build_abe-qemu/console.log.xz | Bin 31148 -> 31692 bytes 06-build_linux/console.log.xz | Bin 4140 -> 4140 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4180 -> 4416 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch release/2.36/master updated (d1d8379bff -> cdc496eb55)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.36/master in repository glibc. from d1d8379bff hppa: Fix initialization of dp register [BZ 29635] new cdc496eb55 hppa: undef __ASSUME_SET_ROBUST_LIST 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: sysdeps/unix/sysv/linux/hppa/kernel-features.h | 3 +++ 1 file changed, 3 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch release/2.35/master updated (562e5b2821 -> a6d2e2c192)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.35/master in repository glibc. from 562e5b2821 hppa: Fix initialization of dp register [BZ 29635] new a6d2e2c192 hppa: undef __ASSUME_SET_ROBUST_LIST 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: sysdeps/unix/sysv/linux/hppa/kernel-features.h | 3 +++ 1 file changed, 3 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (62500c5e7d -> 1c5478176b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 62500c5e7d 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards c1b4f5b55d 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards bae22b3612 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards d5928e3d01 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 73136f8f8b 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 705656d83e 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards ac651e341f 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 788e73fe1a 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards be0f9ac6b2 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards d65b93d040 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards eb6a7187d3 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards f7529f78c9 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 8acb112f1a 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 5dbfd5d4b9 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 4a3f193734 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards a3172f8d91 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards d88fb74fca 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards afc4a0a5ed 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 9778cc8250 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards bd1bee6f64 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 5df0c93afb 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 06a35458d0 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards c5f474187a 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards b38124b3a9 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 5c43ced46d 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards e0e6131ecd 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 78e9a9c5b4 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards f7fb9fb100 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards d4019cb437 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 96c6f8a9ae 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 17242707d2 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards d6ddb65d76 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 18dfdd1849 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 6a00317488 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 25804e2fae 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 615f1c2b7d 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 5328c24681 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards a183dcbf2f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 7d6730bc71 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards ca70ea8152 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 4f7f5c7519 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 72756deafd 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 53cc9736f9 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 7ebad9e5a0 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards d433dc328d 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 1752be0872 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 9787fcd32b 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards fd8749cfc6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 7147ac9387 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards aa8ae8713b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 2611b14f07 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 15f19f7ca4 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 4a9eca8f03 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 5b220d9acd 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards bd03144934 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards b29528a9a0 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 899321ab73 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 2f8579b021 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 8a1337576e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 038d56c861 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards b10d4a46a7 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 1b2504a505 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards ffc8312ff7 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 924d7814a0 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 350d95e53d 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 3e3485946a 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards a442f3c307 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c489ccf389 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 248fa2fd38 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards bc0fc2c05a 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 725171dc7c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards b30366d39e 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 5f088b2f76 85: onsuccess: 7: Success after gcc: 9 commits discards 7eadf130f5 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4bbd04dba1 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards d1c9d16cdf 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards ece4440a63 81: onsuccess: 7: Successful build after gcc: 2 commits discards d791f41a97 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards f72411053f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2dc766b3f9 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6a78b37dd4 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards ad49c5513e 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b22d5075c1 75: onsuccess: 7: Successful build after linux: 44 commits discards b0c7dda274 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards dbbc997636 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 79785617eb 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 20b0bb2ba0 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 4365fb6025 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 7dea929520 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d35ad127b5 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 56ea0c9256 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5fc9dea3a2 66: onsuccess: 7: Successful build after gcc: 3 commits discards 0d3a956bcc 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c0f9c717ae 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c8135444c7 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards f7d70f123f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards c55016b2b2 61: onsuccess: 4: Successful build after gcc: 15 commits discards 7e3efeac3e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 890601dff0 59: force: 7: Successful build after gcc: 2 commits discards 1fa6c48b15 58: onsuccess: 7: Successful build after glibc: 2 commits discards eab2724fa4 57: onsuccess: 7: Successful build after gcc: 7 commits new e9485b96ee 57: onsuccess: 7: Successful build after gcc: 7 commits new a397c3a772 58: onsuccess: 7: Successful build after glibc: 2 commits new 2feb795a27 59: force: 7: Successful build after gcc: 2 commits new 0e296d72ab 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 1e516f16f0 61: onsuccess: 4: Successful build after gcc: 15 commits new bdbfc40266 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new caab8993ba 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 070ac58fc4 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new abc068a1a9 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 598e4b0b10 66: onsuccess: 7: Successful build after gcc: 3 commits new 58cc92e5f9 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 281c6bef72 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b8bc494f33 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5c773cc01c 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 2e0c69b3a1 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new d68d37c6fe 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 7081b376dc 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 11403ebbf0 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 2c15ab93b6 75: onsuccess: 7: Successful build after linux: 44 commits new 6df5fa279e 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 44e1c6d7ef 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new ff7417ce2e 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b09dcd09b5 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a6c988ea60 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new c99acf4632 81: onsuccess: 7: Successful build after gcc: 2 commits new d92759da48 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 30a273451b 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 50600744c2 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 7e419852b2 85: onsuccess: 7: Success after gcc: 9 commits new d40bf82279 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new b20338525e 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new f19a63de93 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 01a1f666e7 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new ac5503fdcb 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 2026d06234 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9ecfa094d9 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new b1dde5da62 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new d80679f81b 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 479e46263e 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 95081acbc3 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 0817dd6f37 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new eb94dad74b 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 7816944b1f 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new cbc4fb079b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 77130b14bd 101: onsuccess: #1609: 7: Success after binutils: 78 commits new db2c65000c 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 09fe5cb492 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new e03998e197 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new bd31d5eeb4 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 51f05a58c8 106: onsuccess: #1617: 7: Success after gcc: 2 commits new e80af7aaaa 107: onsuccess: #1618: 7: Success after gcc: 2 commits new f023daecd3 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 81861e1525 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 0de7c00f51 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new f97584989d 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 275a7cb066 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new e4fb4a7bd4 113: onsuccess: #1624: 7: Success after gcc: 6 commits new b31d91fa8c 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new fe8eca7fb5 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 375d64e158 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 2cbed6b11c 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new d1bcae5123 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 0924c6f8c6 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new cfa5a227eb 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 27c82bcd79 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 32a39a0aa5 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 85bdf022ca 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 7f3f3f2815 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new c3f8438c78 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new d42dc5c6d5 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 4e620675e7 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 7dd71fdede 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 384e9ca27e 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 26c82c1eaf 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new c7e20d046e 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 2e4bcdc353 132: onsuccess: #1645: 7: Success after linux: 23 commits new f80bbc3dd1 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 380172e71f 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 38788a071e 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 5b3974432e 136: onsuccess: #1650: 7: Success after binutils: 2 commits new bcb27b3582 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 7c6381f6c8 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new ebc8fc50b7 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 0b344fa0ff 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 02788b5778 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 735bb69e62 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 664fd52f2d 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 4cbff1543c 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 0cc398ee5f 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 3ae3e23fd5 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 0e450ce15d 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new f831ac80e8 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 028d96b70d 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new aff035dfd3 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 0147fca33a 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 976f13bdf5 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 0cb850ded3 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 562bf4005f 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 89c5f3c582 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new ad0d54a38b 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 8229a5adb5 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 1c5478176b 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (62500c5e7d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 29912 -> 29976 bytes 05-build_abe-stage1/console.log.xz | Bin 90732 -> 91308 bytes 07-build_abe-linux/console.log.xz | Bin 8616 -> 8900 bytes 08-build_abe-glibc/console.log.xz | Bin 234396 -> 233652 bytes 09-build_abe-stage2/console.log.xz | Bin 223320 -> 224760 bytes 10-build_abe-gdb/console.log.xz | Bin 37152 -> 37156 bytes 11-build_abe-qemu/console.log.xz | Bin 31992 -> 31480 bytes 12-check_regression/console.log.xz | Bin 3344 -> 3624 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++++++-------- 18 files changed, 52 insertions(+), 52 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-defconfig updated (bdcd49325f -> 7a3c30f644)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-defconfig in repository toolchain/ci/base-artifacts. from bdcd49325f 12: onsuccess: #39: boot: Success after binutils/gcc/qemu: 1 [...] new 7a3c30f644 13: onsuccess: #40: boot: Success after binutils/gcc/linux/q [...] 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: 01-reset_artifacts/console.log.xz | Bin 1888 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29900 -> 30048 bytes 04-build_abe-stage1/console.log.xz | Bin 91324 -> 90748 bytes 05-build_abe-qemu/console.log.xz | Bin 31056 -> 31320 bytes 06-build_linux/console.log.xz | Bin 5484 -> 5492 bytes 07-boot_linux/console.log.xz | Bin 5812 -> 5840 bytes 08-check_regression/console.log.xz | Bin 3808 -> 4352 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022