Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (9293d273b8c -> a48c0ecd87b)

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_profiled_lto in repository toolchain/ci/base-artifacts. discards 9293d273b8c 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards 8943adbf159 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards e0513cc428f 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards 54c9ba68101 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards f86390fc8cf 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards f34d0bca053 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards 2e39a93fc51 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards c20fa3443dd 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards 9d6ea50829a 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards e52a65af9c2 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 4243469b546 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards 40b10343a6f 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards 56d38bde65a 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards b16b87860b6 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 16a86043ee5 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 4ec8d1bb660 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards b59ff5fd7ae 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards 555b5466c44 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards fab04ca58d4 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards 002776719a5 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards 744cc4a9d4b 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards 97219be1c17 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards 658e248efe8 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards 4b6b61b2c9e 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards 2d5594ef8f2 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards d87df6286b6 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards 4b5c82cca5d 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards 1c6e4447918 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 63452000a2e 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 593d5e85aba 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards 447fe36f6a4 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards cfa838f9904 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards 46a5391af6a 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards 7bc1d5062fe 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 6cef2c84d12 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards aebf37ce1f3 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards e0b6aaa3fb7 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards 2a77d803f15 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards 5f33ed38a60 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards b7de6f2a72d 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards dd5348cc352 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 2cbc8cb520b 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards 856dfebd646 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards 76b747d008a 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards e95b149689c 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards e151e6f0647 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards a02e16ce82a 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards fc69978faa1 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards b128deb9289 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 4378b24a943 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards 62c2cba7d7b 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards bdd2b6fd784 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 6274d200275 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards b4bfa718615 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards b48b951db64 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards f781e239b13 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards fea49ad640c 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards 11c820d8b19 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards a8a780010fb 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 261b4d48816 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 8c8ae63567b 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards 5cf1e9dbba4 141: onsuccess: #559: 1: Success after gcc: 4 commits discards 1060194ea40 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] discards 086fd41a9d9 139: force: #557: 2: Success after gcc: 6 commits discards 1ad3f413f60 138: onsuccess: #554: 2: Success after binutils: 10 commits discards b6b07e6dbc0 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards b0265991405 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards 88e6696f9ff 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards 4bd96aa25eb 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards a9de4733878 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards a9bd357ec8b 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards b452e2fc0ce 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 1f11e720d00 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards f0bc1de2b2b 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 3294171990f 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 8086bbb16e6 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 5ff97b9e6f0 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards b7d2774596f 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards fe239c76087 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards 9ba683a7929 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards cde98b4bb7e 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards e132d5ec384 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 36daec2e04f 120: onsuccess: #535: 1: Success after binutils: 10 commits discards c1d8e831d4d 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] discards f6cebd3df0e 118: force: #533: 2: Success after binutils: 4 commits discards f07b8ecfd70 117: onsuccess: #531: 2: Success after gcc: 65 commits discards 5d717ad4ecd 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 27b309b8119 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards d5dcf02b5c8 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards 1ae5d2471f3 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 3870956ca30 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 87b9472b6f3 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards f18f43d57d7 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards 31612a7e5d9 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards fffa8fe9177 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards 25df1c7c699 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards 8f8078786a3 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards 85aea3c154c 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits discards 3ccee1ea532 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits discards 3582d6c5f6b 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits discards 63f9d540785 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits new 64b7177289c 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits new 4a49a430501 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new cb2d1320508 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits new a98c9d4abed 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new 18828bd1eb7 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new dbb3ac9906c 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new 59f37721b50 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new d34e9e619af 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new b1e6448d534 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new c353e8be6c1 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new 5f2a1b4c700 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 811345d32df 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 225560b46e1 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new d67e43990fc 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new cd3add71750 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new fe242527004 117: onsuccess: #531: 2: Success after gcc: 65 commits new fcb6c5abac6 118: force: #533: 2: Success after binutils: 4 commits new af00e2162d5 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] new 96607df7205 120: onsuccess: #535: 1: Success after binutils: 10 commits new 83791eb7ed9 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 27fc8ffcff0 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new d8e299c1268 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 72c6ca1c8f4 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 003cd19c6b8 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 5fc6a5a5650 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 6df39d69282 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new a4638fb306b 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new f9423d57a52 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 3eca0fd6739 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 6c378d82afa 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 24f59bfdc06 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new dd643e697dd 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new a987d4c2495 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 9376f856ce6 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new f2181161768 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new a7a6526a698 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 2e0f5197cc4 138: onsuccess: #554: 2: Success after binutils: 10 commits new 0e51806bb04 139: force: #557: 2: Success after gcc: 6 commits new d3eea401d83 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] new 8f5fee604d7 141: onsuccess: #559: 1: Success after gcc: 4 commits new 6b5f2466c8b 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 94bacb8d4e0 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new f52451bb27c 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new d898d2ded83 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new ab3346340c8 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new e99b6f1e6e7 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new 080cc31c3cb 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new a5639076f71 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new 7b3a4866940 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new 88116eb757f 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new d0ec5d41ba2 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 4a3151a201b 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 35a99f5f80b 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new 064d78a3c00 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new c4319630988 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new 4e54682f895 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new 29c93788a99 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new 5747e887af9 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new af0a68e2c4f 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 3b8e07a69b5 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new 68564f701f9 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new 70e32b17d9d 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new c551f33f32e 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new f1c8455b06d 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 49234c26e95 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new dc50d97575a 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new fa82e47a6a8 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 8bdee6e204b 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new ddbf34dbb1b 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new cbe446ed617 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new f1d20a32078 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new ead7b477527 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 8505ce326b4 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new 07f6243b6e2 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new dff2187ae38 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 9e88f40ad17 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new 77969967e90 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new dc9fb79102d 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 50f67c2d865 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new b23850004f3 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new b67616984a3 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 8159996f170 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 1a5e84198e4 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new a6a4c852d34 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 73f4c0ce133 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new 0bce73cf276 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new 4609dedc6f3 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new abb056cdd27 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 115caf0ea9c 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new 9952068d8e3 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 144202d0918 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new 4252d1f6c48 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new 88be7d5a4ef 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 4d9a22866ef 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 79fbe8ff469 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new b45d08fe2f0 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new 8b46aaf0502 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new de9728e6af2 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new 9d222ad85cf 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 4a5cb393c0c 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new d8a6066c823 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new a48c0ecd87b 203: onsuccess: #18: 2: Success after binutils/gcc: 9 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 (9293d273b8c) \ 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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 38768 -> 38920 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 303680 -> 304580 bytes 06-check_regression/console.log.xz | Bin 3012 -> 2840 bytes 07-update_baseline/console.log | 32 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++------ 13 files changed, 31 insertions(+), 31 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig updated (57aceb99613 -> 78ca1efcdea)

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-master-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from 57aceb99613 46: onsuccess: #4: boot: Success after binutils/llvm/qemu: [...] new 78ca1efcdea 47: onsuccess: #5: 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 1772 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31204 -> 30780 bytes 04-build_kernel_llvm/console.log.xz | Bin 67984 -> 65756 bytes 05-build_abe-qemu/console.log.xz | Bin 32684 -> 32612 bytes 06-build_linux/console.log.xz | Bin 3356 -> 3496 bytes 07-boot_linux/console.log.xz | Bin 6144 -> 6136 bytes 08-check_regression/console.log.xz | Bin 3880 -> 4224 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 9 +++++++++ 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 20 files changed, 36 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (155086031f9 -> 9eba0786858)

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_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 155086031f9 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards a27f7931661 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6a62d93b99f 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards bef38b070b5 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2228ee3ccc8 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards fe30e2af731 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0729c9dd2ee 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2349063dc4b 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 6fe857d06c7 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0137c182009 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 2c30dbd0b84 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards dbca5f37dc0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 333bdacf924 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 3513fc14b88 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 61bc28819d8 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 5c1c866909b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards fa1f8ca049f 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards c8d122e89e2 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards ab43cfad7fd 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 194f844c9a1 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 583ab404478 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 346b3ae23a3 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9f8fb8358bb 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 94392ec19d3 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards b94d21fee54 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 2a8671627af 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards c78a686e12a 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 16b25664e89 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 906e3677d0c 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 8dd77ad2552 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 1b3b1977ade 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards f58eef350c2 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 25cfceb35ab 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 6785e861b55 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 8753d754345 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 255f9f74a2e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 4fa2e8254b3 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 505fbe7d2a5 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 3a0dd644d28 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards ee8c89cb74c 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 76383c84cfd 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 7b4691e55e3 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards d83a8fe5ec7 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards f41c3333cee 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards aab591cf5df 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 5204ca8ba52 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards ac9984af711 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards b50776e0326 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 3b9d785841b 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards dabcf90de07 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 38e8f874b98 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 796a473f317 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 679fc8a58b7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 3cad2557940 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 17a0ffbb4dd 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 7e87e443470 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 8c94a3ebee6 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 9c1b8baf85f 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 8749e34df75 162: onsuccess: #624: 1: Success after linux: 10 commits discards 3915ad462dc 161: onsuccess: #623: 1: Success after glibc: 9 commits discards bded6cb177c 160: onsuccess: #621: 1: Success after gcc: 11 commits discards e6cc2352c8b 159: onsuccess: #620: 1: Success after binutils: 12 commits discards b6b17da4e1a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards e63a02e8b1b 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards f1e0a624349 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards d1598da0fa1 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 26e78c9ec1f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards f02dddfac25 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards a579b75528e 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 6ef161d9b70 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards d4abe1d7bf0 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 572d0ae14dd 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 35fb69c46cc 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards a79bd57570b 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 5aa210b658d 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards fe3f94dfbb1 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards ec60844263e 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 3947070511f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 20e2d191a75 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 85cb926bbcf 141: onsuccess: #601: 1: Success after linux: 794 commits discards 77c06816b58 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 292d9781203 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 0e8f608f667 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards f657cd7c273 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 5a6bc9a5a04 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 7fe484fe112 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 9c4936483c6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 8261c72a094 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 5014af5cf86 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 9e38e964ca3 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards ecfcd27af40 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 0d53937b9f9 129: onsuccess: #588: 1: Success after linux: 4 commits discards 97b4ea0d1c3 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 6deb1030c9f 127: onsuccess: #584: 1: Success after linux: 21 commits discards 8e25dc50225 126: onsuccess: #582: 1: Success after gcc: 9 commits discards dc9851cc02a 125: onsuccess: #581: 1: Success after binutils: 4 commits discards e020894a0f2 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards e755cba3c37 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 7d99e77b5f1 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards e721e19a8e0 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 8a553e51a44 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 9f5b87389c9 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 394db57dfe7 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 532751927de 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 525400d30f4 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new f10bfcbb9e5 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 2bb7683c9bc 125: onsuccess: #581: 1: Success after binutils: 4 commits new 6293dcc56c4 126: onsuccess: #582: 1: Success after gcc: 9 commits new d906b0158a5 127: onsuccess: #584: 1: Success after linux: 21 commits new 8256a8402a1 128: onsuccess: #586: 1: Success after binutils: 22 commits new 037fdf281cd 129: onsuccess: #588: 1: Success after linux: 4 commits new 000b2ec6068 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new cf019f47d42 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 92df92e83fd 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new ce60fa72d85 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new e6c4a214b86 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 58fad518146 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new a3bd9f5751c 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 07d7cb9acec 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new e4ea349fb82 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new f1d643a4b4b 139: onsuccess: #599: 1: Success after binutils: 10 commits new 1061c4925e8 140: onsuccess: #600: 1: Success after gcc: 23 commits new 7535f6aa078 141: onsuccess: #601: 1: Success after linux: 794 commits new 166f90e48b3 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 4f627023b26 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 4622df71f6e 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new d182059e96e 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 5563d915481 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new e9908c81abe 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 1024f55b5dd 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 730e56f2976 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d9af29bf50e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new b163930ed51 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 0a5d3b27652 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new c82375f6793 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 5e5d733cbe4 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new b0ed6f94f73 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new eea73e8d8dd 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 35b8b9c0ff7 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 7b477f79a75 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new dbb330bbe1a 159: onsuccess: #620: 1: Success after binutils: 12 commits new 26d08e1bf37 160: onsuccess: #621: 1: Success after gcc: 11 commits new 2d98d9aed2b 161: onsuccess: #623: 1: Success after glibc: 9 commits new c8551931a10 162: onsuccess: #624: 1: Success after linux: 10 commits new c7c64594959 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new c3f69eb8674 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new be1048c69af 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 12b697b6212 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new af6880e8c39 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new b858003a326 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 243335bb55e 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 57f47854f89 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 3eba04f43e6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 8c40255fa7e 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 13de028dc00 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new aeab41f8f9f 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new ba871bc142d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 2737e447fff 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new b3b9420b87f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new c78af9a1bfd 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 6fe4dc6f08f 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 5baf0994bbf 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new ea1b7845968 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 82717ee9b12 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 15bd62006b0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 9234af26b57 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 5aaae497f2c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 72122b3c279 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 20c0caaae18 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 20c083eb902 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new d03a3e6c630 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new e0082fe6392 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 8c0689b205f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 98921baa001 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new cdb7eac0d86 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 9b48762ca5b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 13817fd698a 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 753e017e84e 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 9d6675601cb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 6a3fb2cd5db 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 94e396de706 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 0533882953d 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 5280b69656a 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 0e5d2e1b3d9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 105ff778a0a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3ba4ec9e18d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new f6a6b7f0e85 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6c80135832b 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 67e0e7df045 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 96bb61506ce 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 4c199cde8c3 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 56dec98c1fc 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 42aefab7bee 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 264de065b07 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c6ee421b86c 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 84ee57739bf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 436edc4e589 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 8fcaf951bc3 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 56814ea7227 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ec2bc3913bd 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new c5c5af2a2e0 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 0865a2574ea 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 9eba0786858 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] 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 (155086031f9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1748 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52312 -> 52840 bytes 04-build_abe-gcc/console.log.xz | Bin 236040 -> 237428 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 236308 -> 235572 bytes 08-build_abe-gdb/console.log.xz | Bin 51032 -> 51164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3748 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2560 -> 3812 bytes 11-check_regression/console.log.xz | Bin 7508 -> 5884 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 8 - 11-check_regression/mail-body.txt | 34 ++-- 11-check_regression/results.compare | 27 +-- 11-check_regression/results.compare2 | 237 +--------------------- 11-check_regression/results.regressions | 28 --- 12-update_baseline/console.log | 66 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- results | 28 --- sumfiles/g++.log.xz | Bin 2906556 -> 2907112 bytes sumfiles/g++.sum | 106 +++++----- sumfiles/gcc.log.xz | Bin 2482004 -> 2495892 bytes sumfiles/gcc.sum | 342 ++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 950240 -> 952564 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233940 -> 233952 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468620 -> 476848 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 371 insertions(+), 660 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O2_LTO updated (1f8b262af51 -> eadd90e4490)

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_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from 1f8b262af51 6: force: #10: 1: [TCWG CI] 526.blender_r speeds up by -4% [...] new eadd90e4490 7: force: #11: 1: [TCWG CI] 500.perlbench_r failed to build [...] 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 1764 -> 1792 bytes 02-build_bmk_llvm/console.log.xz | Bin 99488 -> 99628 bytes 03-benchmark/benchmark-build.log | 110 +- 03-benchmark/benchmark.log | 108 +- 03-benchmark/console.log.xz | Bin 3916 -> 3892 bytes .../compare-results-vs-first-internal.csv | 42 +- .../compare-results-vs-prev-internal.csv | 56 +- 04-check_regression/console.log.xz | Bin 6000 -> 6676 bytes .../csv-results-vs-first-1/perf.csv | 118 +- .../csv-results-vs-first-1/results.csv | 1898 +- .../csv-results-vs-first-1/size.csv | 81595 +++++++++---------- 04-check_regression/csv-results-vs-first-1/sve.csv | 13 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 124 +- .../csv-results-vs-prev-0/results.csv | 1219 +- 04-check_regression/csv-results-vs-prev-0/size.csv | 42955 +++++----- 04-check_regression/csv-results-vs-prev-0/sve.csv | 10 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 118 +- .../csv-results-vs-prev-1/results.csv | 1898 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 81595 +++++++++---------- 04-check_regression/csv-results-vs-prev-1/sve.csv | 13 +- 04-check_regression/exe.improvement | 1 - 04-check_regression/exe.regression | 1 + 04-check_regression/extra-bisect-params | 2 +- 04-check_regression/jira-body.txt | 4 +- 04-check_regression/mail-body.txt | 4 +- 04-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/exe.regression.diff | 1 + 04-check_regression/results-vs-first-brief.csv | 48 +- 04-check_regression/results-vs-first-full.csv | 120 +- 04-check_regression/results-vs-first-internal.csv | 56 +- 04-check_regression/results-vs-first.csv | 56 +- 04-check_regression/results-vs-first.log | 893 +- 04-check_regression/results-vs-prev-brief.csv | 48 +- 04-check_regression/results-vs-prev-compare.csv | 4 +- 04-check_regression/results-vs-prev-full.csv | 130 +- 04-check_regression/results-vs-prev-internal.csv | 56 +- 04-check_regression/results-vs-prev.csv | 56 +- 04-check_regression/results-vs-prev.log | 1227 +- 04-check_regression/results.regressions | 5 + 04-check_regression/trigger-bisect | 3 + .../error_code-1 => trigger-notify} | 0 dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-functional.json | 4 +- .../500.perlbench_r/results-metadata.json | 10 +- .../500.perlbench_r/results-metrics.json | 2 - .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 10 +- .../508.namd_r/results-metadata.json | 10 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../527.cam4_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../548.exchange2_r/results-metadata.json | 10 +- .../549.fotonik3d_r/results-metadata.json | 10 +- .../554.roms_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 102 +- dashboard/squad-vs-first/summary-annotation.txt | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 830 + jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 15 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 5 + results_id | 2 +- 88 files changed, 104778 insertions(+), 111066 deletions(-) delete mode 100644 04-check_regression/exe.improvement create mode 100644 04-check_regression/exe.regression create mode 100644 04-check_regression/results.regressions create mode 100644 04-check_regression/trigger-bisect copy 04-check_regression/{output-bmk-results/error_code-1 => trigger-notify} (100%) create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/interesting-commits] branch master updated (9946e057 -> 38217688)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 9946e057 Add entry a611b3f3059e4c3b9e7b914091c3edaef099fd5d from https [...] new 38217688 Add entry 6b03ce374e0dc64868b4b6665056dfc3fda0e98f from https [...] 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: .../build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_bmk-code_speed-cpu2017rate/status.txt | 9 +++++++++ 4 files changed, 10 insertions(+), 1 deletion(-) copy llvm/sha1/6b03ce374e0dc64868b4b6665056dfc3fda0e98f/tcwg_bmk-code_speed-cpu201 [...] copy llvm/sha1/6b03ce374e0dc64868b4b6665056dfc3fda0e98f/tcwg_bmk-code_speed-cpu201 [...] copy llvm/sha1/6b03ce374e0dc64868b4b6665056dfc3fda0e98f/tcwg_bmk-code_speed-cpu201 [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (5fe18b2a4f9 -> 20aa69ef099)

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_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 5fe18b2a4f9 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 98a1d6ef85d 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 8efffc9eb63 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 435351babe2 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards b3da5eabaf8 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 126490a82e4 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 29ff17fb386 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ac44fd9faa1 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 31d491be9f2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ff7f6a4d2da 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 0b849aa77cc 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 3f35bcc8f81 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 06be110cb5b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6196af1ac07 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 1c55bd69508 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1cb815d99a7 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards fb649f316f4 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards cc68fdc43c2 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards ae4a8a90242 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards e23daf6bf8e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards f7aa9bf1dc5 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards aa970308e19 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards f72b33a0f63 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards ac79bc9f4d4 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards b59b14df462 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 38b9760c2aa 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 91d7f41479b 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards eb43971b960 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 088fb501687 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 49fe39b7706 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 3c23666f0f8 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards d6b6e56605b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 0650d8d769d 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 6912ff399af 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 7ba3f7c37d4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 01d1dddadb3 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards bf6823a37d2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 333896d3763 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 343cde431ad 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 1118376323f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards e6e09b26377 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards a2275e6e0bf 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards d5e1afdb875 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 95b6dd74d1c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 16104aa3686 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 80d7d038190 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 6d08d1222d8 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 774f1059761 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 66a3f94ef3e 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards f28c6de1079 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 1943a053e7f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 6048baf8b5e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards ea4b981992f 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 5500282febf 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards fb3ab4bbaca 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards fc20a9a949e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards d3380f7aa87 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 74e63721ab4 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards c4d1de2758c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards c38cf1d72c4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 7bd0c00cede 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 48d690570d3 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 0d6c1ededfb 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 2150a699e77 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 5d02c6fd12f 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 36265db5a5e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 8dd1ee14f87 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards b847389b1b5 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards cb06b46ebce 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards fd999fc3a51 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 80a5cf230c2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 3388c13a4f7 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards fe5c38a1b28 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 0d7f92acba0 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 7ddfdd69b0a 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards f598f2e5f17 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards ddfafd94fc1 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 345a8053074 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 77633e87087 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 22f5e751e21 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 8b57098c656 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards a842fad81f8 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards dd543005005 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards fe39fb6260a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards c7b51602fd4 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 39884a7332b 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 5c94d2b5384 31: onsuccess: #38: 1: Success after linux: 14 commits discards cba7309e4ed 30: onsuccess: #36: 1: Success after binutils: 18 commits discards c2e6b17e211 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 938b5c682fc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 95613d0e707 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 310ca396c66 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 8b6542bd882 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards a71152e3d58 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 35e18a4469e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 5025bcbe019 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 059da8f4847 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 8903e24926c 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 51bc5bbfa8c 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards 816ab4051c4 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards ffd6434249f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new 03baf6d298c 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new ccf1e8131d6 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 3ee96fe0303 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new e5d6a98cd22 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new ca98fcdaf8a 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new aee2e47a29a 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 29a679fdc1b 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 8f9e623a9a4 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new f033a5a929e 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 2ecc62004a4 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 5bfa791e975 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 3d61a22e1fc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new ee758f106be 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 491339085d4 30: onsuccess: #36: 1: Success after binutils: 18 commits new 3c38605822b 31: onsuccess: #38: 1: Success after linux: 14 commits new 45e8b4e9638 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 01f14ffa845 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 3f4df179440 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 5ce81aaba08 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 4d49721db59 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 24337a0d4fe 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 31685603e94 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new d4d343a7f5b 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new e4bda099a20 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 7cf9d55e576 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new e4b0d1a08dc 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new bd6ac125422 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 815067a8ccd 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 5ce318569e2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 25f579f9fa4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new bc6bfa50e23 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 836f92aea6f 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 4b608cbcbce 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new b9b11fc912a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 6d70b10a11a 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new e53290b4138 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 55ac63d1011 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new c33554f18b6 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 7e300a2f0a5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 34c00197a38 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 895f4334038 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new bf3b4959b2e 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 88995276154 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new e8b5d92068e 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 3f00b200768 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 00721b37397 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 7224e341370 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 3d218c3b0c7 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new c332572c2fb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 7998c4506a0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 0677376f0d1 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 0054d9ba97e 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 35f551e1755 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new b6ed672f7e7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 38cb8d67c7d 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 23cf339ad0f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 9bed91787ce 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 98efb89399e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new ec963556763 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new e5f57966195 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 4c8733da6f5 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new d739f9cb32b 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 3a0a74218e4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 3110e7c5bc5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new b91c08ac394 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new eae2ed91a00 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new e618c1db353 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 62b2f3ebd1d 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5e3fa3bbe87 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new f9ccc745e0e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 03e2d47bdeb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new e88ea63ccda 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 8238eccbfeb 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 04a2550293f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 7248f3e620a 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new b7474e29dcc 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 309f98952bb 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 4aca07ffbd9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 2d3070ba814 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 2635b5bde2f 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 54a8000b745 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new c3718a19ad6 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 97c09ca871f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new a71107508ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new ebb3e9b6969 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 3b7f1a3cdec 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new a5f92988cb9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 2eb18287d56 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new ad0319b72ae 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new f738a4aabe7 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 2dddc281032 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a752abfeb54 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new c95620dc150 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 59f1230b805 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 3d1552fc000 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a2b233654bd 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 21a341e931d 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 0c2074f1212 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 508b9bfb88f 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1b0cdcd4cff 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 45fe97df612 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 20aa69ef099 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] 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 (5fe18b2a4f9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 1764 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 53404 -> 53544 bytes 04-build_abe-gcc/console.log.xz | Bin 238968 -> 239860 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 235504 -> 235624 bytes 08-build_abe-gdb/console.log.xz | Bin 51320 -> 50164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3744 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2464 -> 2384 bytes 11-check_regression/console.log.xz | Bin 5748 -> 5528 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 36 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 11932 -> 11932 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[gcc] branch master updated (8536c09108f -> f23dc726875)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 8536c09108f Docs: Fix typo in previous commit new 2246d576f92 middle-end: Revert can_special_div_by_const changes [PR108583] new 03c6ba86757 ranger: Add range-ops for widen addition and widen multipli [...] new 0b3c630fcc4 middle-end: don't form FMAs when multiplication is not sing [...] new 81fd62d1378 middle-end: Implement preferred_div_as_shifts_over_mult [PR108583] new f23dc726875 AArch64: Update div-bitmask to implement new optab instead [...] The 5 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: gcc/config/aarch64/aarch64-simd.md | 71 ++++---------- gcc/config/aarch64/aarch64-sve2.md | 57 +++-------- gcc/config/aarch64/aarch64.cc | 61 ++++-------- gcc/doc/tm.texi | 20 ++-- gcc/doc/tm.texi.in | 2 +- gcc/explow.cc | 4 +- gcc/expmed.cc | 23 ++--- gcc/expmed.h | 5 +- gcc/expr.cc | 24 ++--- gcc/gimple-range-op.cc | 53 ++++++++++ gcc/gimple-range-op.h | 1 + gcc/optabs.cc | 13 ++- gcc/range-op.cc | 131 +++++++++++++++++++++++++ gcc/range-op.h | 4 + gcc/target.def | 31 +++--- gcc/target.h | 1 - gcc/targhooks.cc | 17 ++-- gcc/targhooks.h | 4 +- gcc/testsuite/gcc.dg/mla_1.c | 40 ++++++++ gcc/testsuite/gcc.dg/vect/vect-div-bitmask-4.c | 25 +++++ gcc/testsuite/gcc.dg/vect/vect-div-bitmask-5.c | 58 +++++++++++ gcc/tree-ssa-math-opts.cc | 14 +++ gcc/tree-vect-generic.cc | 11 --- gcc/tree-vect-patterns.cc | 81 +++++++++++++-- gcc/tree-vect-stmts.cc | 9 -- 25 files changed, 509 insertions(+), 251 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/mla_1.c create mode 100644 gcc/testsuite/gcc.dg/vect/vect-div-bitmask-4.c create mode 100644 gcc/testsuite/gcc.dg/vect/vect-div-bitmask-5.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-fujitsu_speed-cpu2017speed/llvm-aarch64-master-O3 updated (8aa2605315a -> 52361fd36f6)

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_bmk-fujitsu_speed-cpu2017speed/llvm-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 8aa2605315a 4: force: #10: 1: [TCWG CI] 657.xz_s speeds up by -5% after [...] new 52361fd36f6 5: force: #11: 1: [TCWG CI] 623.xalancbmk_s slowed down by [...] 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 1864 -> 1728 bytes 02-build_bmk_llvm/console.log.xz | Bin 99524 -> 99576 bytes 03-benchmark/benchmark-build.log | 88 +- 03-benchmark/benchmark.log | 86 +- 03-benchmark/console.log.xz | Bin 3812 -> 3792 bytes .../607.cactuBSSN_s.symbols-regression | 2 + 04-check_regression/619.lbm_s.symbols-regression | 2 + 04-check_regression/654.roms_s.symbols-regression | 2 + .../compare-results-vs-first-internal.csv | 186 +- .../compare-results-vs-prev-internal.csv | 188 +- 04-check_regression/console.log.xz | Bin 9812 -> 10612 bytes .../csv-results-vs-first-1/md5sum.csv | 1774 +++++----- .../csv-results-vs-first-1/perf.csv | 3062 ++++++++--------- .../csv-results-vs-first-1/results.csv | 3232 +++++++++--------- .../csv-results-vs-first-1/size.csv | 10 +- .../csv-results-vs-prev-0/md5sum.csv | 2178 ++++++------ 04-check_regression/csv-results-vs-prev-0/perf.csv | 3120 +++++++++-------- .../csv-results-vs-prev-0/results.csv | 3558 ++++++++++---------- 04-check_regression/csv-results-vs-prev-0/size.csv | 266 +- .../csv-results-vs-prev-1/md5sum.csv | 1774 +++++----- 04-check_regression/csv-results-vs-prev-1/perf.csv | 3062 ++++++++--------- .../csv-results-vs-prev-1/results.csv | 3232 +++++++++--------- 04-check_regression/csv-results-vs-prev-1/size.csv | 10 +- 04-check_regression/exe.improvement | 2 - 04-check_regression/exe.regression | 2 + 04-check_regression/extra-bisect-params | 2 +- 04-check_regression/jira-body.txt | 14 +- 04-check_regression/mail-body.txt | 14 +- 04-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/exe.regression.diff | 1 + 04-check_regression/results-vs-first-brief.csv | 36 +- 04-check_regression/results-vs-first-full.csv | 3041 ++++++++--------- 04-check_regression/results-vs-first-internal.csv | 136 +- 04-check_regression/results-vs-first.csv | 136 +- 04-check_regression/results-vs-first.log | 506 +-- 04-check_regression/results-vs-prev-brief.csv | 36 +- 04-check_regression/results-vs-prev-compare.csv | 18 +- 04-check_regression/results-vs-prev-full.csv | 3225 +++++++++--------- 04-check_regression/results-vs-prev-internal.csv | 138 +- 04-check_regression/results-vs-prev.csv | 138 +- 04-check_regression/results-vs-prev.log | 596 ++-- 04-check_regression/results.regressions | 14 + 04-check_regression/symbol.regression | 6 + 04-check_regression/trigger-bisect | 3 + .../error_code-1 => trigger-notify} | 0 dashboard/dashboard-generate.sh | 2 +- .../600.perlbench_s/results-metadata.json | 10 +- .../600.perlbench_s/results-metrics.json | 2 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 10 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 2 +- .../603.bwaves_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metrics.json | 2 +- .../607.cactuBSSN_s/results-metadata.json | 10 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 10 +- .../620.omnetpp_s/results-metadata.json | 10 +- .../620.omnetpp_s/results-metrics.json | 2 +- .../squad-vs-first/621.wrf_s/results-metadata.json | 10 +- .../623.xalancbmk_s/results-metadata.json | 10 +- .../623.xalancbmk_s/results-metrics.json | 2 +- .../625.x264_s/results-metadata.json | 10 +- .../627.cam4_s/results-metadata.json | 10 +- .../628.pop2_s/results-metadata.json | 10 +- .../631.deepsjeng_s/results-metadata.json | 10 +- .../631.deepsjeng_s/results-metrics.json | 2 +- .../638.imagick_s/results-metadata.json | 10 +- .../641.leela_s/results-metadata.json | 10 +- .../641.leela_s/results-metrics.json | 2 +- .../squad-vs-first/644.nab_s/results-metadata.json | 10 +- .../648.exchange2_s/results-metadata.json | 10 +- .../648.exchange2_s/results-metrics.json | 2 +- .../649.fotonik3d_s/results-metadata.json | 10 +- .../654.roms_s/results-metadata.json | 10 +- .../squad-vs-first/657.xz_s/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 90 +- dashboard/squad-vs-first/summary-annotation.txt | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1059 ++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 25 +- mail/mail-body.txt | 25 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 14 + results_id | 2 +- 90 files changed, 18344 insertions(+), 17025 deletions(-) create mode 100644 04-check_regression/607.cactuBSSN_s.symbols-regression create mode 100644 04-check_regression/619.lbm_s.symbols-regression create mode 100644 04-check_regression/654.roms_s.symbols-regression delete mode 100644 04-check_regression/exe.improvement create mode 100644 04-check_regression/exe.regression create mode 100644 04-check_regression/results.regressions create mode 100644 04-check_regression/symbol.regression create mode 100644 04-check_regression/trigger-bisect copy 04-check_regression/{output-bmk-results/error_code-1 => trigger-notify} (100%) create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/interesting-commits] branch master updated (b46d3a02 -> 9946e057)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from b46d3a02 Add entry 6b03ce374e0dc64868b4b6665056dfc3fda0e98f from https [...] new 9946e057 Add entry a611b3f3059e4c3b9e7b914091c3edaef099fd5d from https [...] 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: .../llvm-aarch64-master-O3}/build_url | 2 +- .../llvm-aarch64-master-O3}/last_good | 0 .../llvm-aarch64-master-O3/summary.txt | 16 +++++++++++ .../tcwg_bmk-fujitsu_speed-cpu2017speed/status.txt | 32 ++++++++++++++++++++++ 4 files changed, 49 insertions(+), 1 deletion(-) copy llvm/sha1/{dd4a9c463b35e32e2e05e975fc04fa80200d39d5/tcwg_bmk-fujitsu_speed-cp [...] copy llvm/sha1/a611b3f3059e4c3b9e7b914091c3edaef099fd5d/{tcwg_bmk-code_speed-cpu20 [...] create mode 100644 llvm/sha1/a611b3f3059e4c3b9e7b914091c3edaef099fd5d/tcwg_bmk-fuj [...] create mode 100644 llvm/sha1/a611b3f3059e4c3b9e7b914091c3edaef099fd5d/tcwg_bmk-fuj [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allyesconfig updated (505df2dc70f -> 3eab6dfe147)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from 505df2dc70f 53: onsuccess: #6: 21252: Success after binutils/gcc/qemu: [...] new 3eab6dfe147 54: onsuccess: #7: 21210: Success after linux: 1124 commits 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 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30520 -> 30604 bytes 04-build_abe-stage1/console.log.xz | Bin 90364 -> 90900 bytes 05-build_abe-qemu/console.log.xz | Bin 29944 -> 31220 bytes 06-build_linux/console.log.xz | Bin 8996 -> 8764 bytes 08-check_regression/console.log.xz | Bin 3852 -> 3116 bytes 08-check_regression/mail-body.txt | 13 ++++++++++++- 08-check_regression/results.regressions | 11 +++++++++++ 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +++++++++++++-- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++++++------------ results | 13 ++++++++++++- 17 files changed, 62 insertions(+), 29 deletions(-) create mode 100644 08-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023