Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-cpu2017fast/llvm-aarch64-master-O3_LTO updated (803184b4ab -> 968d76e988)

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_vect-cpu2017fast/llvm-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. from 803184b4ab 5: onsuccess: #10: 1: [TCWG CI] Success after llvm: 890 commits new 968d76e988 6: onsuccess: #11: 1: [TCWG CI] Success after llvm: 421 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 1992 -> 1996 bytes 02-build_bmk_llvm/console.log.xz | Bin 99820 -> 101596 bytes 03-benchmark/benchmark-build.log | 107 +- 03-benchmark/benchmark.log | 105 +- 03-benchmark/console.log.xz | Bin 3832 -> 3816 bytes .../compare-results-vs-first-internal.csv | 59 +- .../compare-results-vs-prev-internal.csv | 65 +- 04-check_regression/console.log.xz | Bin 6056 -> 6136 bytes .../csv-results-vs-first-1/perf.csv | 145 +- .../csv-results-vs-first-1/results.csv | 677 ++--- .../csv-results-vs-first-1/size.csv | 552 ++-- 04-check_regression/csv-results-vs-prev-0/perf.csv | 140 +- .../csv-results-vs-prev-0/results.csv | 3062 ++++++++++---------- 04-check_regression/csv-results-vs-prev-0/size.csv | 2952 +++++++++---------- 04-check_regression/csv-results-vs-prev-1/perf.csv | 145 +- .../csv-results-vs-prev-1/results.csv | 677 ++--- 04-check_regression/csv-results-vs-prev-1/size.csv | 552 ++-- 04-check_regression/results-vs-first-brief.csv | 46 +- 04-check_regression/results-vs-first-full.csv | 151 +- 04-check_regression/results-vs-first-internal.csv | 61 +- 04-check_regression/results-vs-first.csv | 61 +- 04-check_regression/results-vs-first.log | 1188 ++++---- 04-check_regression/results-vs-prev-brief.csv | 46 +- 04-check_regression/results-vs-prev-full.csv | 153 +- 04-check_regression/results-vs-prev-internal.csv | 61 +- 04-check_regression/results-vs-prev.csv | 61 +- 04-check_regression/results-vs-prev.log | 1238 ++++---- dashboard/dashboard-generate.sh | 2 +- .../508.namd_r/results-metadata.json | 8 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 8 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 8 +- .../511.povray_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 8 +- .../526.blender_r/results-metrics.json | 2 +- .../600.perlbench_s/results-metadata.json | 8 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 8 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 2 +- .../603.bwaves_s/results-metadata.json | 8 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 8 +- .../607.cactuBSSN_s/results-metadata.json | 8 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 8 +- .../squad-vs-first/619.lbm_s/results-metrics.json | 2 +- .../620.omnetpp_s/results-metadata.json | 8 +- .../squad-vs-first/621.wrf_s/results-metadata.json | 8 +- .../623.xalancbmk_s/results-metadata.json | 8 +- .../623.xalancbmk_s/results-metrics.json | 2 +- .../625.x264_s/results-metadata.json | 8 +- .../squad-vs-first/625.x264_s/results-metrics.json | 2 +- .../627.cam4_s/results-metadata.json | 8 +- .../628.pop2_s/results-metadata.json | 8 +- .../631.deepsjeng_s/results-metadata.json | 8 +- .../631.deepsjeng_s/results-metrics.json | 2 +- .../638.imagick_s/results-metadata.json | 8 +- .../641.leela_s/results-metadata.json | 8 +- .../squad-vs-first/644.nab_s/results-metadata.json | 8 +- .../648.exchange2_s/results-metadata.json | 8 +- .../648.exchange2_s/results-metrics.json | 2 +- .../649.fotonik3d_s/results-metadata.json | 8 +- .../654.roms_s/results-metadata.json | 8 +- .../squad-vs-first/657.xz_s/results-metadata.json | 8 +- .../squad-vs-first/657.xz_s/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 102 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 12 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 14 +- manifest.sh | 14 +- results_id | 2 +- 71 files changed, 6353 insertions(+), 6323 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (381fecf5a5 -> 8a868996a2)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 381fecf5a5 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d098b6c3c1 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 3144670189 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 54fdb1717b 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards baed829562 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 367fddfb0a 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 894ab7281e 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 435ccc01f3 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 1dc131a7aa 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 29acad32dd 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 8e261db9ca 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 0db3c4fa13 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards c4ed7b818f 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 35d9f94c81 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 6e063f18c4 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 25b8e380e3 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards ae9bdcff94 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 12ddb6b14a 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards c8d6eccded 212: force: #24: 1: Success after binutils: 2 commits discards fb000a7dd2 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8c863863be 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 96c29d4429 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 56fa491ee8 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards d52d2e7332 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards bbd578ffb8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards f8d8b9fe1e 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 914ee2f99a 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 49b6462926 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards b75327ab37 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 2b8ead3792 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 09ef13a98c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 56fce32fa1 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards d4be09ccb5 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards e03204de14 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards f61db2cbd4 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 4df5747a58 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4da350f493 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards d1da52d4a9 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards eeb487c12f 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 474433420e 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 7760302bc8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 8c884d01c0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 57e75c76a8 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 220d7b478d 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards ddf209323d 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards eec40378ca 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards d5546f577a 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards bbfc09541f 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 16eb115338 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 684b21ee4c 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 885e06b034 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 90fa632daf 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 57e0ed29cc 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 325fa8d8fc 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards ef1eec7b0f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 0ce0df3dba 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 02339085fe 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 0787993e49 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 2e09f93645 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 34333c9f62 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 3b919620d5 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 541729d3d0 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 7690aae308 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards e930695747 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 65f5239a70 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 04fa6d3c0c 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards e485dc6419 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards d98de22b28 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 193bf00eba 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 620c598767 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 625046292e 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 6a5612d45d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards d7bcb8bc67 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards a3c8bcc71f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 402e40a284 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 5f62baeca5 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards de7c4ef58e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards ff85a260ca 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 308d199ff5 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 7fa5c0ecb2 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards fd4cf21b27 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 4916da7399 149: onsuccess: #684: 1: Success after linux: 10 commits discards 99e9955646 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 18d982f9a6 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 52b9b5dac5 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 27a39229b4 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 7072371de8 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards fbe992caf7 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 70552a95a2 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 981cf358f1 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 263c83a9f7 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 2058620d0a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards e6719a8792 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards fe03b33bac 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards ec56d6f061 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards a5ea02f539 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards d5c4c4d4df 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards d5f0ca2936 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 4cba947ed5 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards bdd45a3cc3 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards de51b841f9 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 7face8fdb1 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 29c4e986bd 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 153b7babaa 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new c2b399a03b 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 91b5d9adcb 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 3c9a46e5d6 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new e968d26310 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 934d0df149 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 936ceff840 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 046133f22d 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 1a18bb7221 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new eec9717dba 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new a128f5b52a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 1faf22d051 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new d2ec0ca702 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new b858e6981c 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new c370462dd1 146: onsuccess: #680: 1: Success after binutils: 20 commits new 6e508dea88 147: onsuccess: #681: 1: Success after gcc: 6 commits new 6bcc9cf6b6 148: onsuccess: #683: 1: Success after glibc: 9 commits new ed5f7251be 149: onsuccess: #684: 1: Success after linux: 10 commits new 52beface80 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 3ba523c86f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 243d677a10 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new ea438cf888 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 491b8fec95 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new fb94f69f9a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new b82df59a82 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 99a1c7fa6b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new b06ab93d28 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 7e89b871f1 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 3a7fe8b91b 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new ba993358d7 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new d6fdfe22fd 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new ee7d4db11c 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new ea23ff756d 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new 1a108154e2 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 6bf1947053 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new f76f54ae2e 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new bf0428a6ae 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 84e5c9b6eb 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 798c63936b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 8bbe5ce923 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 9149031835 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 48bd514c15 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new cb9a410c15 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 96d0aba18b 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 19d4e66499 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 2a1195d322 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new e3ace85615 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 80926727f9 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 02c2085ef5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 9e5c765b6a 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 49d4b63a24 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 2c98fcb45b 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 830b0393af 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new a2360cbaef 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 370d8ade33 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 1718869d74 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new c8fcca39be 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new a4ad71f491 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new fc188178d6 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 377869f210 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new dff6976434 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 42be39a80a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 6031607c19 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new d043479864 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a2c9b469d8 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 7635033097 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 281847a24a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 13a2b4c16e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new e1e1352322 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new cbc5c60039 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new a000eb015f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 7b0b0e2704 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 0205eb3a9c 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1b5bfde78f 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a882545888 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new f28386bb94 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 470463d589 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 83a14c2c6b 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2737c4ab60 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new def10a83fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new ab4aa4d416 212: force: #24: 1: Success after binutils: 2 commits new 60e5a7df27 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new de7fd3c03c 214: onsuccess: #26: 1: Success after binutils: 12 commits new 88bb9909e1 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new d64a488118 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 8f72b0b1f6 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new fe4e97d1d6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 5e8c010161 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 2c71c4c32f 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f347b942b3 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 91cef9cb38 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new f3dff46b19 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 73c68ca10c 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new dfb8bd24f1 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 22845bf622 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new d6481d1aed 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 944082d039 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new b18050e28e 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 48000fff39 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8a868996a2 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] 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 (381fecf5a5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 2028 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35212 -> 35192 bytes 04-build_abe-gcc/console.log.xz | Bin 204024 -> 203488 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 9468 bytes 07-build_abe-glibc/console.log.xz | Bin 241364 -> 241216 bytes 08-build_abe-gdb/console.log.xz | Bin 34748 -> 34908 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2176 -> 2404 bytes 11-check_regression/console.log.xz | Bin 4948 -> 5124 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 40 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 56 +++++++++++++++-------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++---------- manifest.sh | 38 ++++++++++---------- sumfiles/binutils.log.xz | Bin 63076 -> 62992 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150792 -> 150688 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122636 -> 122608 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 106 insertions(+), 102 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (a1fd0f69bd -> 53565e9252)

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 a1fd0f69bd 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards c9b3a8451e 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards fcc15cb89f 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 1c1827b85a 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards b9b1022422 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards c4711ed31d 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards cb558561d6 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 23dd297e21 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 62b1f799d0 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards e11d5dd82b 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 6676bc661c 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards db379d7e0a 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards dfa635c872 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards b51ef31ec4 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards a4c4e030c5 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards d66e6f8012 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 6a3fb83237 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e9cd7ccb79 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 96acb65fee 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 0f553444a7 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards dcf31ceb47 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards edbfa88437 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 832c8bbfe9 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] discards 995cf7117a 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards 6d66716ad1 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards b542f1a250 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards 1279223d84 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 3c0e33756f 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 33048a77e1 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 27722afd28 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 120ab2fa3e 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 02026d9fcf 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 45009e1dc5 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5f18b197c3 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards ee62c0a4a2 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 068e6837cd 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 1476b65a01 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards af27a563af 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9a2538e2df 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards f788de607f 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 53d222f244 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 6f5db4352e 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 39ec80210c 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards ab7ad7ca03 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards a1abe4f0c2 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 57700736b4 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 1dacec8143 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 6b72961cc2 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 1a5b24da57 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards aea2c0ebcb 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 9de5095d17 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 9a1ea07ce9 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 5dd02c1a1e 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards d394b00f28 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards c996fbac77 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 03113adb92 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 1642f54d7d 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards a791f352fc 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards afd930ba2b 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 4e59a3f8bd 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 00e3c5c2eb 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards b25f65a4d6 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 216bd95ea6 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards eeb1bd1cca 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards a4e957e56b 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 002fc8a920 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards b6f1ae4937 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 94bd28a3c3 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards a7e86f03e2 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 1a690c20c5 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards d98cbf9999 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards f314ab3419 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 6c50438371 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards d77a35122f 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards c5be76af03 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 64700f45e9 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 2b420bef9f 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards b03161c6d9 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 39317afe8a 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 24f4c8f54c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 2c7bbdefb1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards cf5d3d0e20 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 7f2e163d54 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 856b174260 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 49c057762f 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 000196d87e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards ba5840ee54 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards b3803bfaeb 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards d8ff9bb634 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 799b528d44 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 0bcf57d452 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 6e927fb54f 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards a1905be1e6 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards fb29485b8d 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards bec83f8d16 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 14a971e174 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 001045c3f9 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 984f4c1709 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 8ffbf5aca7 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards e1cc0ffd90 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards ce780fbd1e 384: onsuccess: #2205: 1: Success after gcc: 2 commits new aecf224f1d 384: onsuccess: #2205: 1: Success after gcc: 2 commits new a52b48cb36 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new ed7f3d777a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 710c1049be 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 08ef6fe583 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 2be9e86dcf 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 3dade6c362 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 6f9caf11c2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 6cb239ef8b 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 440761e9dc 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new ce1ccc28b8 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 8db34364dc 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new cac5b31d63 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 483a18eb59 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new fe32b78fba 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new bef976f008 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new d66fe2b127 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new d3a648ff67 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new a81eb710d1 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new a63f0dcc10 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new ac32d86bd5 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 04e48f0a6d 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new c49a73287f 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 2e37082fdd 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 04c20e9e51 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 811e5d6811 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 3306eb12e0 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 6b0756af37 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 19fb41521f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new eef3b31751 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 5102899cf6 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 0e4764dacd 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 58d222ad22 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new d45f2b8a6e 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 659e994c8a 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new c6e5e4f53d 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 4434489fba 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new dc7efd9eed 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 8967f553e9 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 3208cbaff2 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 8edb249a42 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 9aed488b2a 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 770b7496bf 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 0f0b6abda3 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new eb98b1b76a 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 8b230231e0 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new ad5a8438f4 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new ba015cfb54 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 34cbe9dc8f 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 8215ddd05d 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 9bcdc0e583 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 7f9d7c27b0 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 19db7e6f59 436: onsuccess: #2260: 1: Success after gcc: 7 commits new dc429bf32e 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 9932334a71 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 79f3c466ca 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 6936eab0a0 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 00ccec90a9 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new e60384632a 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 0885088943 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 7debe70111 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 384fa02f9e 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 51ce56cf63 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 26623e3925 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new ed8f0a12f9 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 604579fdef 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new e242374fc1 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new fdd5c6b0aa 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new fe0414c8b2 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 8139ba1b32 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 7ff94018d6 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 1cb1d29a48 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new c450716815 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 1b03b3c799 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 753a18ad22 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 03138ce67c 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new ebca880d3d 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 01281da0bb 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 46876b0d78 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] new ba1f72c771 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new bb55a4d5f2 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new 53f723d1c0 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 43da29d4d7 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 62d3fdd08c 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 8de528688a 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 5bc9a7dc77 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 98d3f66d5a 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new f002432b25 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 4568fc96d4 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 9096336c40 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f7c310ae0d 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 1c3c93dbf7 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 8abd6366de 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 4ac5909270 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 67bafbe022 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new f338bcf803 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 85a85d949e 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 77833b3540 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new a4e6cb4f12 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new d0bbf514b6 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 82a66a1515 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 53565e9252 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] 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 (a1fd0f69bd) \ 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 2136 -> 2100 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 26692 -> 27240 bytes 04-build_abe-stage1/console.log.xz | Bin 88484 -> 88588 bytes 06-build_abe-linux/console.log.xz | Bin 8720 -> 9540 bytes 07-build_abe-glibc/console.log.xz | Bin 232248 -> 232960 bytes 08-build_abe-stage2/console.log.xz | Bin 224344 -> 225096 bytes 09-build_abe-gdb/console.log.xz | Bin 34396 -> 34568 bytes 10-build_abe-qemu/console.log.xz | Bin 31020 -> 30676 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 5856 -> 6444 bytes 13-check_regression/console.log.xz | Bin 6764 -> 13764 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/results.compare | 23 +- 13-check_regression/results.compare2 | 2210 +++++- 13-check_regression/results.regressions | 23 +- 14-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 66 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 46 +- manifest.sh | 48 +- results | 23 +- sumfiles/g++.log.sep.xz | Bin 208416 -> 124404 bytes sumfiles/g++.log.xz | Bin 2681264 -> 2662184 bytes sumfiles/g++.sum | 1966 +++--- sumfiles/g++.sum.sep | 11165 +++++++++++++++++++++++++++++- sumfiles/gcc.log.sep.xz | Bin 165520 -> 136876 bytes sumfiles/gcc.log.xz | Bin 2208956 -> 2236584 bytes sumfiles/gcc.sum | 14 +- sumfiles/gcc.sum.sep | 10934 +---------------------------- sumfiles/gfortran.log.sep.xz | Bin 85248 -> 60952 bytes sumfiles/gfortran.log.xz | Bin 896740 -> 901568 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 7650 +++++++++----------- sumfiles/libatomic.log.xz | Bin 2288 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216832 -> 217200 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 19196 -> 14916 bytes sumfiles/libstdc++.log.xz | Bin 439580 -> 447508 bytes sumfiles/libstdc++.sum | 5 +- sumfiles/libstdc++.sum.sep | 755 +- 51 files changed, 18175 insertions(+), 16833 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[gcc] branch master updated (804208a2ab8 -> 939fb3fffeb)

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 804208a2ab8 [testsuite] enable -maltivec like vect_int for signbit-2.c new 939fb3fffeb MAINTAINERS: Add myself as CTF and BTF reviewer 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: MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig updated (a9c8f5c285 -> 10b07450ac)

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-next-allnoconfig in repository toolchain/ci/base-artifacts. from a9c8f5c285 57: onsuccess: #9: boot: [TCWG CI] Success after binutils/ll [...] new 10b07450ac 58: onsuccess: #10: boot: [TCWG CI] Success after binutils/l [...] 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 2012 -> 2000 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 27128 -> 27468 bytes 04-build_kernel_llvm/console.log.xz | Bin 65596 -> 66152 bytes 05-build_abe-qemu/console.log.xz | Bin 32124 -> 30588 bytes 06-build_linux/console.log.xz | Bin 3404 -> 3412 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4252 -> 4208 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 48 +++++++++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++------------ manifest.sh | 32 +++++++++++------------ 17 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017speed/llvm-aarch64-master-O3_LTO updated (2d2567504c -> 615940591d)

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-cpu2017speed/llvm-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. from 2d2567504c 3: force: #12: 1: [TCWG CI] No change after llvm: 331 commits new 615940591d 4: force: #21: 1: [TCWG CI] Failure after llvmorg-17-init-48 [...] 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 1768 -> 1876 bytes 02-build_bmk_llvm/console.log.xz | Bin 99548 -> 99564 bytes 03-benchmark/benchmark-build.log | 125 +- 03-benchmark/benchmark.log | 123 +- 03-benchmark/console.log.xz | Bin 3864 -> 3788 bytes .../compare-results-vs-first-internal.csv | 32 +- .../compare-results-vs-prev-internal.csv | 52 +- 04-check_regression/console.log.xz | Bin 6192 -> 7244 bytes .../csv-results-vs-first-1/perf.csv | 145 +- .../csv-results-vs-first-1/results.csv | 462 +- .../csv-results-vs-first-1/size.csv | 101214 ++++++------ 04-check_regression/csv-results-vs-first-1/sve.csv | 16 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 144 +- .../csv-results-vs-prev-0/results.csv | 148939 +++++++++--------- 04-check_regression/csv-results-vs-prev-0/size.csv | 122731 ++++++++------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 17 + 04-check_regression/csv-results-vs-prev-1/perf.csv | 145 +- .../csv-results-vs-prev-1/results.csv | 462 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 101214 ++++++------ 04-check_regression/csv-results-vs-prev-1/sve.csv | 16 +- 04-check_regression/exe.improvement | 1 + 04-check_regression/exe.regression | 2 + 04-check_regression/extra-bisect-params | 2 +- 04-check_regression/jira-body.txt | 1 - 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 + .../output-bmk-results/symbol.regression.diff | 0 04-check_regression/results-vs-first-brief.csv | 34 +- 04-check_regression/results-vs-first-full.csv | 142 +- 04-check_regression/results-vs-first-internal.csv | 42 +- 04-check_regression/results-vs-first.csv | 42 +- 04-check_regression/results-vs-first.log | 824 +- 04-check_regression/results-vs-prev-brief.csv | 42 +- 04-check_regression/results-vs-prev-compare.csv | 8 +- 04-check_regression/results-vs-prev-full.csv | 166 +- 04-check_regression/results-vs-prev-internal.csv | 50 +- 04-check_regression/results-vs-prev.csv | 50 +- 04-check_regression/results-vs-prev.log | 1103 +- 04-check_regression/results.regressions | 18 + 04-check_regression/trigger-bisect | 3 + .../symbol.improvement.diff => trigger-notify} | 0 dashboard/dashboard-generate.sh | 2 +- .../600.perlbench_s/results-metadata.json | 10 +- .../600.perlbench_s/results-metrics.json | 4 +- .../602.gcc_s/results-functional.json | 2 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 10 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 3 +- .../603.bwaves_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 10 +- .../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 +- .../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 +- .../638.imagick_s/results-metadata.json | 10 +- .../638.imagick_s/results-metrics.json | 2 +- .../641.leela_s/results-metadata.json | 10 +- .../squad-vs-first/644.nab_s/results-metadata.json | 10 +- .../squad-vs-first/644.nab_s/results-metrics.json | 2 +- .../648.exchange2_s/results-metadata.json | 10 +- .../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/657.xz_s/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 86 +- git/llvm_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 5 + mail/changes-list-short.txt | 1 + mail/jira-body.txt | 7 - manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 19 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 14 +- results | 18 + results_id | 2 +- 85 files changed, 243931 insertions(+), 234832 deletions(-) create mode 100644 04-check_regression/exe.improvement create mode 100644 04-check_regression/exe.regression delete mode 100644 04-check_regression/jira-body.txt delete mode 100644 04-check_regression/output-bmk-results/symbol.regression.diff create mode 100644 04-check_regression/results.regressions create mode 100644 04-check_regression/trigger-bisect rename 04-check_regression/{output-bmk-results/symbol.improvement.diff => trigger- [...] create mode 100755 jenkins/notify.sh create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/interesting-commits] branch master updated (22ac9a39 -> 1f210f3c)

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 22ac9a39 Add entry 16439f419b270184ec501c531bf20d83b6745fb0 from https [...] new 1f210f3c Add entry f242291f59bf5cced08e8f6e7c3068cfe4dff06c 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_LTO}/build_url | 2 +- .../llvm-aarch64-master-O3_LTO/last_good | 0 .../llvm-aarch64-master-O3_LTO}/summary.txt | 28 +++++----- .../tcwg_bmk-code_speed-cpu2017speed/status.txt | 63 ++++++++++++++++++++++ 4 files changed, 79 insertions(+), 14 deletions(-) copy llvm/sha1/{6b03ce374e0dc64868b4b6665056dfc3fda0e98f/tcwg_bmk-code_speed-cpu20 [...] copy llvm/sha1/f242291f59bf5cced08e8f6e7c3068cfe4dff06c/{tcwg_bmk-code_speed-cpu20 [...] copy llvm/sha1/{e8bc77ec085cf23a743bf203d526000df8f45946/tcwg_bmk-code_size-spec2k [...] create mode 100644 llvm/sha1/f242291f59bf5cced08e8f6e7c3068cfe4dff06c/tcwg_bmk-cod [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig updated (078d3857d7 -> da7c699f1a)

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-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 078d3857d7 56: onsuccess: #9: boot: [TCWG CI] Success after binutils/ll [...] new da7c699f1a 57: onsuccess: #10: boot: [TCWG CI] Success after binutils/l [...] 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 2008 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27348 -> 27572 bytes 04-build_kernel_llvm/console.log.xz | Bin 65156 -> 67208 bytes 05-build_abe-qemu/console.log.xz | Bin 32488 -> 31172 bytes 06-build_linux/console.log.xz | Bin 3456 -> 2928 bytes 08-check_regression/console.log.xz | Bin 4172 -> 3776 bytes 09-update_baseline/console.log | 9 +++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- 16 files changed, 63 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O2_LTO updated (36404be3d2 -> b0dc03b9e1)

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/gnu-arm-master-O2_LTO in repository toolchain/ci/base-artifacts. from 36404be3d2 12: force: #17: 1: [TCWG CI] Success after glibc: 25 commits new b0dc03b9e1 13: force: #18: 1: [TCWG CI] Failure after glibc-2.37.9000-2 [...] 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 2088 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2572 -> 2580 bytes 03-build_abe-binutils/console.log.xz | Bin 27224 -> 27404 bytes 04-build_abe-stage1/console.log.xz | Bin 90224 -> 89848 bytes 06-build_abe-linux/console.log.xz | Bin 7632 -> 7632 bytes 07-build_abe-glibc/console.log.xz | Bin 235004 -> 234724 bytes 08-build_abe-stage2/console.log.xz | Bin 212000 -> 210936 bytes 09-benchmark/benchmark-build.log | 126 +- 09-benchmark/benchmark.log | 124 +- 09-benchmark/console.log.xz | Bin 4128 -> 4116 bytes .../compare-results-vs-first-internal.csv | 68 +- .../compare-results-vs-prev-internal.csv | 68 +- 10-check_regression/console.log.xz | Bin 8016 -> 8984 bytes .../csv-results-vs-first-1/perf.csv | 165 +- .../csv-results-vs-first-1/results.csv | 120955 ++-- .../csv-results-vs-first-1/size.csv | 549379 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 39538 +- .../csv-results-vs-first-1/vect.csv | 58 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 161 +- .../csv-results-vs-prev-0/results.csv | 360643 ++++++------ 10-check_regression/csv-results-vs-prev-0/size.csv | 530722 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 39710 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 48 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 165 +- .../csv-results-vs-prev-1/results.csv | 120955 ++-- 10-check_regression/csv-results-vs-prev-1/size.csv | 549379 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 39538 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 58 +- 10-check_regression/exe.regression | 1 + 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/mail-body.txt | 3 + 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.regression | 1 + .../output-bmk-results/exe.regression.diff | 2 + 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 175 +- 10-check_regression/results-vs-first-internal.csv | 68 +- 10-check_regression/results-vs-first.csv | 68 +- 10-check_regression/results-vs-first.log | 1336 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 2 +- 10-check_regression/results-vs-prev-full.csv | 179 +- 10-check_regression/results-vs-prev-internal.csv | 68 +- 10-check_regression/results-vs-prev.csv | 68 +- 10-check_regression/results-vs-prev.log | 1682 +- 10-check_regression/results.regressions | 17 + 10-check_regression/trigger-bisect | 3 + .../trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 8 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 8 +- .../503.bwaves_r/results-metadata.json | 8 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 8 +- .../507.cactuBSSN_r/results-metadata.json | 8 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 8 +- .../510.parest_r/results-metadata.json | 8 +- .../511.povray_r/results-metadata.json | 8 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 8 +- .../520.omnetpp_r/results-metadata.json | 8 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 8 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 8 +- .../525.x264_r/results-metadata.json | 8 +- .../squad-vs-first/525.x264_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 8 +- .../527.cam4_r/results-metadata.json | 8 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 8 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 8 +- .../541.leela_r/results-metadata.json | 8 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 8 +- .../548.exchange2_r/results-metadata.json | 8 +- .../548.exchange2_r/results-metrics.json | 2 +- .../549.fotonik3d_r/results-metadata.json | 8 +- .../554.roms_r/results-metadata.json | 8 +- .../squad-vs-first/557.xz_r/results-metadata.json | 8 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/glibc_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 11 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 24 +- mail/short-diag.txt | 2 +- manifest.sh | 18 +- results | 17 + results_id | 2 +- 93 files changed, 1176637 insertions(+), 1179405 deletions(-) create mode 100644 10-check_regression/exe.regression create mode 100644 10-check_regression/output-bmk-results/exe.regression create mode 100644 10-check_regression/output-bmk-results/exe.regression.diff create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/trigger-bisect copy dashboard/squad-vs-first/summary-annotation.txt => 10-check_regression/trigge [...] create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/interesting-commits] branch master updated (bb2a67f8 -> 22ac9a39)

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 bb2a67f8 Add entry 429a7a88438cc80e7c58d9f63d44838089899b12 from https [...] new 22ac9a39 Add entry 16439f419b270184ec501c531bf20d83b6745fb0 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: glibc/glibc-2.37.9000-233-g16439f419b | 1 + .../gnu-arm-master-O2_LTO/build_url | 1 + .../gnu-arm-master-O2_LTO/last_good | 1 + .../gnu-arm-master-O2_LTO}/summary.txt | 34 +++---- .../tcwg_bmk-code_speed-cpu2017rate/status.txt | 102 +++++++++++++++++++++ 5 files changed, 122 insertions(+), 17 deletions(-) create mode 120000 glibc/glibc-2.37.9000-233-g16439f419b create mode 100644 glibc/sha1/16439f419b270184ec501c531bf20d83b6745fb0/tcwg_bmk-co [...] create mode 100644 glibc/sha1/16439f419b270184ec501c531bf20d83b6745fb0/tcwg_bmk-co [...] copy {gcc/sha1/429a7a88438cc80e7c58d9f63d44838089899b12/tcwg_bmk-code_size-cpu2017 [...] create mode 100644 glibc/sha1/16439f419b270184ec501c531bf20d83b6745fb0/tcwg_bmk-co [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023