Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (121bb04074 -> 494c02f2a4)

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 121bb04074 251: force: #87: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 9193d763a0 250: force: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 088ea5bda8 249: force: #83: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 45eaf14290 248: force: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 533e20f2e7 247: force: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards ca45687a58 246: force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 2db286a4b1 245: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 322f12c510 244: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 6b637d646a 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 4a2781e573 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards da225f88d2 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards a348df646c 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 01b4923a8f 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 5ff0cb9061 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3b2d7dfedd 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 04bd6548c1 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c0370bc755 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards fcfa0a8ce9 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards e78bf9eb31 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards dc2174b884 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 7e9f028a4d 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 14d53efc54 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards b38436e1bb 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards a3da0f3fc4 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards cacd3cf299 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 11686c4f6d 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6789af3079 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 429ffbbdc4 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 38f5563729 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards b2ede97ec6 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 65f8c8ebc0 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 7bb51ba065 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards aa4bbd8e9b 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards e2a2769979 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards f8911e0bc3 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards e52ca14253 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 3de4fcfbd1 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 697d8a6060 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 4d68de5e2a 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 517b2b78c1 212: force: #24: 1: Success after binutils: 2 commits discards 4de1ce33d6 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8c8510e293 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards f1603cf52e 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a36b26e49f 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 3b6255ac8f 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards df0656026d 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards dd502f9c5b 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 3586639927 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 632d88bef0 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 2c166391f4 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 6dcb0fa711 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 1f8d639c4c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a47e5714af 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9c6e93e651 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 1a75582927 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 15001335a2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 2fdaa3d9e7 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 89c8da731b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 2e552353d3 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 19c6dcf8e9 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards c1a23bb3d9 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b094acf6da 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 507c6e8d8c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 90614a55c3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 23e1a16ed3 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards ffe7325c5e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 821c1988fe 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 8d7dfc5547 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards f6a5cbc376 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards f596e3888e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 4b14153d76 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 6f9b0a3f37 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 107b96f5a0 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 89a14ccfb2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards b735b3240b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards c135acf113 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards ffe1ab68f3 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 3d9d3ab9d3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards ad7a44c287 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 0da22cc336 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 41095f8dcc 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards aac904dc51 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 33a8c82d1d 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards bd3b77cecb 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards c78a73331a 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards a2efe33827 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 9e4bf4b049 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 6594300836 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards c75540f262 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards ae9ee9c524 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 45fa556e34 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 18fe5dc190 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards c5fa1da392 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 553f47cd15 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 4bb82a541b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards ea2eb113c0 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 7587bb557f 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards f05fc837c4 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards f8561c0af3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 9b69ee814f 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 707f7cf613 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new e969d98077 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 031b224363 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 3f7caac99c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 6647b7518e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 03915801ed 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 90c778fc89 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new d1d117571a 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 889f29f207 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 9a16c80e93 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new f173ab94dc 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new fa55091b33 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 89ace709bf 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new fb93e52e31 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 821b902a0c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new 983100102d 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new b7cf0562f2 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new d81a01f0fa 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 8fec9fc34b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 85b5f9b890 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new f2bf653be9 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 7547cf47d4 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new e4000e339a 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 1ca9feb739 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new dc3d15ffc0 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new f46798977f 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 5b94986be6 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 9ca961d2ae 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new d70a593336 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new c8cf191b29 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 6a4c695f81 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new b8451cae4c 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new d8c774e99c 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 16c182a520 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new a9c0b7e594 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 3b5318a7d8 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 4d9f9841bd 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new e54712704e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new ed9a04db59 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 8b2b707451 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new a032eec958 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new e86b94b010 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3dd6ad1fc2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new ae9bafd7a0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 03985bc5ad 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new ced925e1cd 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2076d3ec94 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 9ab1831d97 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 400a06f142 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 44bcf062db 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 76ef630983 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new aa2f3d25e4 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new b49b6e2402 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 214b8131b8 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new eca65e7bf2 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ff4a357a81 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 6fd487d9eb 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 90fe7098db 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new df52fb0667 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 1f8d6fe7d4 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3632a26bf4 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 1f55ed18bc 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 5b7f1a7519 212: force: #24: 1: Success after binutils: 2 commits new e1798985ff 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 6715f5ad62 214: onsuccess: #26: 1: Success after binutils: 12 commits new 559b471695 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new f7a699b508 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 9251ea0b45 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 5976d7b94e 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new e80e750c5f 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 193e21bf57 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 2f8fb317c2 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new cdf6a47217 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 8958ed3227 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 9f1960825e 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 1160f582a3 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 54b59ee51a 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new c7fd2b6dce 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 670bd130a8 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 5cf3995c0f 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new c813297d66 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8cc54bfc71 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new d30d4d5bc0 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new db661fc3b9 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 3a81e36eda 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 0d4e2eba9f 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new c7c7ad4205 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d8e6cc218e 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1f9944748d 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2fdc4c8f52 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new fa5fb0417e 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new b53bd0f955 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 107266cc0f 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new baac532242 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 34ff0fe760 244: force: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new cbc8ec45a2 245: force: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new f036eb7065 246: force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 3fde5e3616 247: force: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 372e01a149 248: force: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 5691ef1529 249: force: #83: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7fd718601d 250: force: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 5ca94b8b24 251: force: #87: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 494c02f2a4 252: force: #89: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] 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 (121bb04074) \ 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 2144 -> 2156 bytes 02-prepare_abe/console.log.xz | Bin 2440 -> 2416 bytes 03-build_abe-binutils/console.log.xz | Bin 35940 -> 35880 bytes 04-build_abe-gcc/console.log.xz | Bin 205232 -> 204500 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8776 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 241792 -> 241968 bytes 08-build_abe-gdb/console.log.xz | Bin 35688 -> 35004 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3872 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2740 -> 2744 bytes 11-check_regression/console.log.xz | Bin 1600 -> 1604 bytes 11-check_regression/results.compare | 8 ++-- 11-check_regression/results.regressions | 8 ++-- 11-check_regression/trigger-bisect | 4 +- 12-update_baseline/console.log | 72 ++++++++++++++--------------- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++-- mail/results.regressions | 8 ++-- manifest.sh | 12 ++--- results | 8 ++-- sumfiles/binutils.log.xz | Bin 62692 -> 62732 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150732 -> 150776 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122604 -> 122640 bytes sumfiles/ld.sum | 2 +- 27 files changed, 70 insertions(+), 70 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (314c3927 -> aac4127a)

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 314c3927 Add entry 94a21e008c4778e446321b1355f61abc75a076be from https [...] new aac4127a Add entry e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722 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: .../tcwg_gnu_native_check_binutils/master-aarch64/build_url | 2 +- .../tcwg_gnu_native_check_binutils/master-aarch64/last_good | 0 .../master-aarch64/summary.txt | 0 .../tcwg_gnu_native_check_binutils/status.txt | 13 +++++++++++++ 4 files changed, 14 insertions(+), 1 deletion(-) copy {binutils/sha1/2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b => gdb/sha1/e10d82fc3 [...] copy {binutils => gdb}/sha1/e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722/tcwg_gnu_nati [...] copy {binutils => gdb}/sha1/e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-O2 updated (799b643c97 -> 1b4e5a11d0)

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_size-spec2k6/gnu-arm-master-O2 in repository toolchain/ci/base-artifacts. from 799b643c97 5: onsuccess: #7: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 1b4e5a11d0 6: onsuccess: #8: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] 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 2060 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 27948 -> 28464 bytes 04-build_abe-stage1/console.log.xz | Bin 89916 -> 90568 bytes 06-build_abe-linux/console.log.xz | Bin 7596 -> 7644 bytes 07-build_abe-glibc/console.log.xz | Bin 234164 -> 234448 bytes 08-build_abe-stage2/console.log.xz | Bin 211824 -> 214160 bytes 09-benchmark/benchmark-build.log | 96 +- 09-benchmark/benchmark.log | 94 +- 09-benchmark/console.log.xz | Bin 4112 -> 4136 bytes 10-check_regression/bmk-specific-variability.csv | 170 +- 10-check_regression/console.log.xz | Bin 15652 -> 15616 bytes .../output-bmk-results/exe.improvement | 3 +- .../output-bmk-results/exe.regression | 12 - .../output-bmk-results/exe.regression.diff | 1 - .../output-bmk-results/symbol.improvement | 7 +- .../output-bmk-results/symbol.regression | 19 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 32 +- results-vs-first/compare-results-internal.csv | 230 +- results-vs-first/csv-results-0/md5sum.csv | 26 +- results-vs-first/csv-results-0/results.csv | 26 +- results-vs-first/csv-results-1/md5sum.csv | 1669 +++--- results-vs-first/csv-results-1/perf.csv | 2541 ++++---- results-vs-first/csv-results-1/results.csv | 3712 ++++++------ results-vs-first/csv-results-1/size.csv | 716 +-- results-vs-first/csv-results-1/sve.csv | 6200 ++++++++++---------- results-vs-first/interesting-symbols.csv | 18 +- results-vs-first/results-brief.csv | 68 +- results-vs-first/results-full.csv | 2565 ++++---- results-vs-first/results-internal.csv | 240 +- results-vs-first/results.csv | 240 +- results-vs-first/tcwg-benchmark-results.log | 2848 ++++----- results-vs-prev/compare-results-internal.csv | 238 +- results-vs-prev/compare-results.csv | 18 +- results-vs-prev/csv-results-0/md5sum.csv | 1663 +++--- results-vs-prev/csv-results-0/perf.csv | 2726 ++++----- results-vs-prev/csv-results-0/results.csv | 3412 +++++------ results-vs-prev/csv-results-0/size.csv | 432 +- results-vs-prev/csv-results-0/sve.csv | 4674 +++++++-------- results-vs-prev/csv-results-1/md5sum.csv | 1669 +++--- results-vs-prev/csv-results-1/perf.csv | 2541 ++++---- results-vs-prev/csv-results-1/results.csv | 3712 ++++++------ results-vs-prev/csv-results-1/size.csv | 716 +-- results-vs-prev/csv-results-1/sve.csv | 6200 ++++++++++---------- results-vs-prev/interesting-symbols.csv | 18 +- results-vs-prev/results-brief.csv | 68 +- results-vs-prev/results-full.csv | 2837 +++++---- results-vs-prev/results-internal.csv | 248 +- results-vs-prev/results.csv | 248 +- results-vs-prev/tcwg-benchmark-results.log | 3342 ++++++----- results_id | 2 +- 56 files changed, 28134 insertions(+), 28173 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/exe.regression delete mode 100644 10-check_regression/output-bmk-results/exe.regression.diff -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gcc/master-aarch64 updated (c280d5786c -> 264ff76398)

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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. from c280d5786c 52: force: #88: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 264ff76398 53: force: #90: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] 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 2100 -> 2096 bytes 02-prepare_abe/console.log.xz | Bin 2424 -> 2440 bytes 03-build_abe-binutils/console.log.xz | Bin 35884 -> 35672 bytes 04-build_abe-gcc/console.log.xz | Bin 204260 -> 204072 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8880 -> 8916 bytes 07-build_abe-glibc/console.log.xz | Bin 241400 -> 241464 bytes 08-build_abe-gdb/console.log.xz | Bin 35820 -> 35376 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3860 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9492 -> 9984 bytes 11-check_regression/console.log.xz | Bin 1676 -> 1684 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.regressions | 16 +- 11-check_regression/trigger-bisect | 4 +- 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 9 - git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 16 +- mail/results.regressions | 16 +- manifest.sh | 12 +- results | 16 +- sumfiles/g++.log.sep.xz | Bin 1436 -> 1436 bytes sumfiles/g++.log.xz | Bin 1408 -> 1408 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 4 +- sumfiles/gcc.log.sep.xz | Bin 6360 -> 5048 bytes sumfiles/gcc.log.xz | Bin 372472 -> 371316 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 755 +++++++++++++------------------- sumfiles/gfortran.log.sep.xz | Bin 1448 -> 1444 bytes sumfiles/gfortran.log.xz | Bin 55636 -> 55736 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 4 +- sumfiles/libatomic.log.xz | Bin 432 -> 432 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 432 -> 432 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 432 -> 432 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 440 -> 440 bytes sumfiles/libstdc++.log.xz | Bin 424 -> 424 bytes sumfiles/libstdc++.sum.sep | 2 +- 43 files changed, 362 insertions(+), 524 deletions(-) create mode 100644 11-check_regression/trigger-notify -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (d2fb5b9a -> 314c3927)

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 d2fb5b9a Add entry 50dc52e853ff267ad1f4c98571c262017b0536f8 from https [...] new 314c3927 Add entry 94a21e008c4778e446321b1355f61abc75a076be 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: gcc/basepoints/gcc-13-7187-g94a21e008c4 | 1 + .../master-aarch64/build_url | 2 +- .../master-aarch64/last_good | 1 + .../master-aarch64/summary.txt | 8 +++--- .../tcwg_gnu_native_fast_check_gcc/status.txt | 33 ++++++++++++++++++++++ 5 files changed, 40 insertions(+), 5 deletions(-) create mode 120000 gcc/basepoints/gcc-13-7187-g94a21e008c4 copy {binutils/gcc/linux/glibc/gdb/sha1 => gcc/sha1/94a21e008c4778e446321b1355f61a [...] create mode 100644 gcc/sha1/94a21e008c4778e446321b1355f61abc75a076be/tcwg_gnu_nati [...] copy gcc/sha1/{2ab0d83e8880fe747af3f137aef382d2d4c09e4c => 94a21e008c4778e446321b1 [...] create mode 100644 gcc/sha1/94a21e008c4778e446321b1355f61abc75a076be/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (29261712e0 -> d1f2d1130f)

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 in repository toolchain/ci/base-artifacts. discards 29261712e0 229: onsuccess: #52: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5fc1dfd68e 228: onsuccess: #51: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 709e2169a0 227: onsuccess: #50: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6af63d0ce0 226: onsuccess: #49: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards f18cb9c833 225: onsuccess: #48: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards f1a98c4243 224: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] discards f94e74293c 223: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] discards b5bd0ac21e 222: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards f096ed3468 221: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards 2b782c4d61 220: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] discards 6352b36ccc 219: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] discards ce8031d4c9 218: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] discards 644053226a 217: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] discards e1381bf3e0 216: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] discards 19a61cc0fa 215: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] discards 1d8e25c2f3 214: onsuccess: #36: 2: [TCWG CI] Success after binutils/gcc [...] discards c650b24fde 213: onsuccess: #35: 2: [TCWG CI] Success after binutils/gcc [...] discards e501043933 212: onsuccess: #34: 2: [TCWG CI] Success after binutils/gcc [...] discards 501a77f555 211: onsuccess: #32: 2: Success after binutils/gcc: 7 commits discards ae0d47d707 210: onsuccess: #31: 2: Success after binutils/gcc: 7 commits discards aad74ea112 209: onsuccess: #30: 2: Success after binutils/gcc: 32 commits discards d09f8f1067 208: onsuccess: #29: 2: Success after binutils/gcc: 32 commits discards af0e4006e0 207: onsuccess: #28: 2: Success after binutils/gcc: 38 commits discards ab4adc9287 206: onsuccess: #27: 2: Success after binutils/gcc: 70 commits discards 649da86017 205: onsuccess: #25: 2: Success after binutils/gcc: 13 commits discards 312eb939cf 204: onsuccess: #24: 2: Success after binutils/gcc: 33 commits discards 1ca56f1df9 203: onsuccess: #23: 2: Success after binutils/gcc: 81 commits discards 000d5b3f33 202: onsuccess: #21: 2: Success after binutils/gcc: 37 commits discards 6918404b09 201: onsuccess: #20: 2: Success after binutils/gcc: 56 commits discards c21db72760 200: onsuccess: #19: 2: Success after binutils/gcc: 42 commits discards 01f4bac50b 199: onsuccess: #18: 2: Success after binutils/gcc: 15 commits discards 5707a49107 198: onsuccess: #17: 2: Success after binutils/gcc: 15 commits discards 4f8276d70a 197: onsuccess: #16: 2: Success after binutils/gcc: 57 commits discards db1c4cd636 196: onsuccess: #15: 2: Success after binutils/gcc: 33 commits discards 1575a85f70 195: onsuccess: #14: 2: Success after binutils/gcc: 28 commits discards 0d44fcd78c 194: onsuccess: #13: 2: Success after binutils/gcc: 62 commits discards 642902d970 193: onsuccess: #12: 2: Success after binutils/gcc: 27 commits discards 0ff926dfd7 192: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 9443434d26 191: onsuccess: #10: 2: Success after binutils/gcc: 17 commits discards 1035f8381e 190: onsuccess: #9: 2: Success after binutils/gcc: 53 commits discards 6322a1aff6 189: onsuccess: #8: 2: Success after binutils/gcc: 40 commits discards 199f6d04d4 188: onsuccess: #7: 2: Success after binutils/gcc: 24 commits discards 733e2275ae 187: onsuccess: #6: 2: Success after binutils/gcc: 47 commits discards 893a394d4c 186: onsuccess: #5: 2: Success after binutils/gcc: 40 commits discards 62f920792a 185: onsuccess: #4: 2: Success after binutils/gcc: 3 commits discards 9f399c9ca4 184: onsuccess: #3: 2: Success after binutils/gcc: 12 commits discards 4bd458b63e 183: onsuccess: #2: 2: Success after binutils/gcc: 19 commits discards 242424220b 182: onsuccess: #1: 2: Success after binutils/gcc: 67 commits discards c1cfaaeddc 181: onsuccess: #593: 2: Success after binutils/gcc: 31 commits discards 1b770a08e5 180: onsuccess: #592: 2: Success after binutils/gcc: 147 commits discards c3ab1b041f 179: onsuccess: #591: 2: Success after binutils/gcc: 51 commits discards dbbe1a2ea9 178: onsuccess: #590: 2: Success after binutils/gcc: 6 commits discards af1a34cb28 177: onsuccess: #589: 2: Success after binutils/gcc: 22 commits discards a93db8d52c 176: onsuccess: #588: 2: Success after binutils/gcc: 19 commits discards 6411089a96 175: onsuccess: #587: 2: Success after binutils/gcc: 38 commits discards 4ed795b0bf 174: onsuccess: #586: 2: Success after binutils/gcc: 102 commits discards 6ca86fbfd4 173: onsuccess: #585: 2: Success after binutils/gcc: 32 commits discards 124f86de9b 172: onsuccess: #584: 2: Success after binutils/gcc: 92 commits discards 705f1cca74 171: onsuccess: #583: 2: Success after binutils/gcc: 51 commits discards 9915b823b3 170: onsuccess: #582: 2: Success after binutils/gcc: 120 commits discards 6a1c9128b4 169: onsuccess: #581: 2: Success after binutils/gcc: 67 commits discards dcd0325c9f 168: onsuccess: #580: 2: Success after binutils/gcc: 23 commits discards c82cbc2094 167: onsuccess: #579: 2: Success after binutils/gcc: 43 commits discards e0da71400f 166: onsuccess: #578: 2: Success after binutils/gcc: 16 commits discards c2bb1f954f 165: onsuccess: #577: 2: Success after binutils/gcc: 31 commits discards a4f8db2d4a 164: onsuccess: #576: 2: Success after binutils/gcc: 5 commits discards d7890ad9f5 163: onsuccess: #575: 2: Success after binutils/gcc: 30 commits discards 63faf51b9a 162: onsuccess: #574: 2: Success after binutils/gcc: 55 commits discards 4601d6f855 161: onsuccess: #573: 2: Success after binutils/gcc: 41 commits discards ebb55418ae 160: onsuccess: #572: 2: Success after binutils/gcc: 107 commits discards 610e6b91a3 159: onsuccess: #571: 2: Success after binutils/gcc: 55 commits discards b8951c265a 158: onsuccess: #570: 2: Success after binutils/gcc: 13 commits discards bea70bb9d8 157: onsuccess: #569: 2: Success after binutils/gcc: 43 commits discards ccb7745940 156: onsuccess: #568: 2: Success after binutils/gcc: 117 commits discards c48809abed 155: onsuccess: #567: 2: Success after binutils/gcc: 27 commits discards 4cf1e8bd3c 154: onsuccess: #566: 2: Success after binutils/gcc: 65 commits discards 3305c14a95 153: onsuccess: #565: 2: Success after binutils/gcc: 52 commits discards 066b85290f 152: onsuccess: #564: 2: Success after binutils/gcc: 11 commits discards 4277ef71f0 151: onsuccess: #563: 2: Success after binutils/gcc: 5 commits discards 569eefed2b 150: onsuccess: #562: 2: Success after binutils/gcc: 39 commits discards cc56761d3d 149: onsuccess: #561: 2: Success after binutils/gcc: 41 commits discards 84d1ecce39 148: onsuccess: #560: 2: Success after binutils/gcc: 32 commits discards 2fbd403f2d 147: onsuccess: #559: 2: Success after binutils/gcc: 76 commits discards 47879c7d35 146: onsuccess: #558: 2: Success after binutils/gcc: 34 commits discards cb8cb80894 145: onsuccess: #557: 2: Success after binutils/gcc: 137 commits discards a9cc8d7ee5 144: onsuccess: #556: 2: Success after binutils/gcc: 36 commits discards f72babd2c9 143: onsuccess: #555: 2: Success after binutils/gcc: 139 commits discards 9c8db15dd4 142: onsuccess: #553: 2: Success after binutils/gcc: 6 commits discards 7c53a61c64 141: onsuccess: #552: 2: Success after binutils/gcc: 9 commits discards 2d54627485 140: onsuccess: #551: 2: Success after binutils/gcc: 68 commits discards 2201d987ca 139: onsuccess: #549: 2: Success after binutils/gcc: 104 commits discards 99d14628ed 138: onsuccess: #548: 1: Success after gcc: 3 commits discards c255e2fbea 137: force: #547: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards b7ac7e4169 136: force: #546: 2: Success after gcc: 8 commits discards f16f091fb5 135: onsuccess: #543: 2: Success after binutils: 14 commits discards 2e2f3074c4 134: onsuccess: #541: 2: Success after binutils/gcc: 13 commits discards 9c1ca7edde 133: onsuccess: #540: 2: Success after binutils/gcc: 16 commits discards 013c6e846e 132: onsuccess: #539: 2: Success after binutils/gcc: 28 commits discards e4269855cf 131: onsuccess: #538: 2: Success after binutils/gcc: 5 commits discards cf6e992a9a 130: onsuccess: #537: 2: Success after binutils/gcc: 15 commits discards fd05685611 129: onsuccess: #536: 2: Success after binutils/gcc: 23 commits new c4b3638e35 129: onsuccess: #536: 2: Success after binutils/gcc: 23 commits new db775f572b 130: onsuccess: #537: 2: Success after binutils/gcc: 15 commits new 9e0befad2d 131: onsuccess: #538: 2: Success after binutils/gcc: 5 commits new 89c86feb0c 132: onsuccess: #539: 2: Success after binutils/gcc: 28 commits new e92e88872d 133: onsuccess: #540: 2: Success after binutils/gcc: 16 commits new f235a8f1bf 134: onsuccess: #541: 2: Success after binutils/gcc: 13 commits new 3f1feae2b6 135: onsuccess: #543: 2: Success after binutils: 14 commits new a9bbc64e08 136: force: #546: 2: Success after gcc: 8 commits new 728d5186de 137: force: #547: 1: Failure after basepoints/gcc-13-4953-g3 [...] new de953094cc 138: onsuccess: #548: 1: Success after gcc: 3 commits new 265f126b8e 139: onsuccess: #549: 2: Success after binutils/gcc: 104 commits new 651305e29d 140: onsuccess: #551: 2: Success after binutils/gcc: 68 commits new fe0b95940e 141: onsuccess: #552: 2: Success after binutils/gcc: 9 commits new d4f807072b 142: onsuccess: #553: 2: Success after binutils/gcc: 6 commits new 81b5d7b8ad 143: onsuccess: #555: 2: Success after binutils/gcc: 139 commits new 2c11bd5639 144: onsuccess: #556: 2: Success after binutils/gcc: 36 commits new 19f4c83150 145: onsuccess: #557: 2: Success after binutils/gcc: 137 commits new 4f6db34c2e 146: onsuccess: #558: 2: Success after binutils/gcc: 34 commits new 2fe64a96d1 147: onsuccess: #559: 2: Success after binutils/gcc: 76 commits new 5cf7cfb508 148: onsuccess: #560: 2: Success after binutils/gcc: 32 commits new 4af4379711 149: onsuccess: #561: 2: Success after binutils/gcc: 41 commits new 3a90fd57cb 150: onsuccess: #562: 2: Success after binutils/gcc: 39 commits new 3e2f3e6436 151: onsuccess: #563: 2: Success after binutils/gcc: 5 commits new 2b2807abc0 152: onsuccess: #564: 2: Success after binutils/gcc: 11 commits new 095470cc79 153: onsuccess: #565: 2: Success after binutils/gcc: 52 commits new e594330425 154: onsuccess: #566: 2: Success after binutils/gcc: 65 commits new 79383af5d5 155: onsuccess: #567: 2: Success after binutils/gcc: 27 commits new 444475241a 156: onsuccess: #568: 2: Success after binutils/gcc: 117 commits new 12b9184450 157: onsuccess: #569: 2: Success after binutils/gcc: 43 commits new 1d8205f923 158: onsuccess: #570: 2: Success after binutils/gcc: 13 commits new 14fe423569 159: onsuccess: #571: 2: Success after binutils/gcc: 55 commits new aa1d089f1c 160: onsuccess: #572: 2: Success after binutils/gcc: 107 commits new 9e61e8399f 161: onsuccess: #573: 2: Success after binutils/gcc: 41 commits new a7ccbd5e05 162: onsuccess: #574: 2: Success after binutils/gcc: 55 commits new 630ae575dd 163: onsuccess: #575: 2: Success after binutils/gcc: 30 commits new ebec54095b 164: onsuccess: #576: 2: Success after binutils/gcc: 5 commits new f15ad8521d 165: onsuccess: #577: 2: Success after binutils/gcc: 31 commits new 8df9a181ed 166: onsuccess: #578: 2: Success after binutils/gcc: 16 commits new bc91d27292 167: onsuccess: #579: 2: Success after binutils/gcc: 43 commits new dedad320dc 168: onsuccess: #580: 2: Success after binutils/gcc: 23 commits new 07ffee61af 169: onsuccess: #581: 2: Success after binutils/gcc: 67 commits new 5026a98bf5 170: onsuccess: #582: 2: Success after binutils/gcc: 120 commits new 719f2bab03 171: onsuccess: #583: 2: Success after binutils/gcc: 51 commits new e92765f380 172: onsuccess: #584: 2: Success after binutils/gcc: 92 commits new a5287cda86 173: onsuccess: #585: 2: Success after binutils/gcc: 32 commits new 7e01814855 174: onsuccess: #586: 2: Success after binutils/gcc: 102 commits new df828f3e01 175: onsuccess: #587: 2: Success after binutils/gcc: 38 commits new 51d85e639d 176: onsuccess: #588: 2: Success after binutils/gcc: 19 commits new 0b18bcd010 177: onsuccess: #589: 2: Success after binutils/gcc: 22 commits new f72472eeae 178: onsuccess: #590: 2: Success after binutils/gcc: 6 commits new debb9e6ae6 179: onsuccess: #591: 2: Success after binutils/gcc: 51 commits new 94a38d15a1 180: onsuccess: #592: 2: Success after binutils/gcc: 147 commits new bcc93747f8 181: onsuccess: #593: 2: Success after binutils/gcc: 31 commits new 63ebd6b5be 182: onsuccess: #1: 2: Success after binutils/gcc: 67 commits new 64ca6ecae9 183: onsuccess: #2: 2: Success after binutils/gcc: 19 commits new 1da523e084 184: onsuccess: #3: 2: Success after binutils/gcc: 12 commits new 40d90ea669 185: onsuccess: #4: 2: Success after binutils/gcc: 3 commits new 562a22698b 186: onsuccess: #5: 2: Success after binutils/gcc: 40 commits new 64b0ed1e9a 187: onsuccess: #6: 2: Success after binutils/gcc: 47 commits new 7ab1678588 188: onsuccess: #7: 2: Success after binutils/gcc: 24 commits new 9d57aae4c3 189: onsuccess: #8: 2: Success after binutils/gcc: 40 commits new a399656374 190: onsuccess: #9: 2: Success after binutils/gcc: 53 commits new 5ed7085647 191: onsuccess: #10: 2: Success after binutils/gcc: 17 commits new e178901edf 192: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new 98dafc0b19 193: onsuccess: #12: 2: Success after binutils/gcc: 27 commits new c99f76484d 194: onsuccess: #13: 2: Success after binutils/gcc: 62 commits new 1d32507da9 195: onsuccess: #14: 2: Success after binutils/gcc: 28 commits new d52a49277e 196: onsuccess: #15: 2: Success after binutils/gcc: 33 commits new f12a039168 197: onsuccess: #16: 2: Success after binutils/gcc: 57 commits new 7e666f8735 198: onsuccess: #17: 2: Success after binutils/gcc: 15 commits new b94678585a 199: onsuccess: #18: 2: Success after binutils/gcc: 15 commits new 23939dc91c 200: onsuccess: #19: 2: Success after binutils/gcc: 42 commits new 858e099192 201: onsuccess: #20: 2: Success after binutils/gcc: 56 commits new 85e2677cd5 202: onsuccess: #21: 2: Success after binutils/gcc: 37 commits new 53658067b9 203: onsuccess: #23: 2: Success after binutils/gcc: 81 commits new 661831109e 204: onsuccess: #24: 2: Success after binutils/gcc: 33 commits new 205cf520ed 205: onsuccess: #25: 2: Success after binutils/gcc: 13 commits new d4e8cf0cda 206: onsuccess: #27: 2: Success after binutils/gcc: 70 commits new abe13b714f 207: onsuccess: #28: 2: Success after binutils/gcc: 38 commits new 2db9ef6dc2 208: onsuccess: #29: 2: Success after binutils/gcc: 32 commits new 214146cb20 209: onsuccess: #30: 2: Success after binutils/gcc: 32 commits new 41c066878c 210: onsuccess: #31: 2: Success after binutils/gcc: 7 commits new 5a8b34514d 211: onsuccess: #32: 2: Success after binutils/gcc: 7 commits new b00b30c211 212: onsuccess: #34: 2: [TCWG CI] Success after binutils/gcc [...] new a4cdd79c2d 213: onsuccess: #35: 2: [TCWG CI] Success after binutils/gcc [...] new aa3ca30e2d 214: onsuccess: #36: 2: [TCWG CI] Success after binutils/gcc [...] new ebbb7cd9a8 215: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] new 4609c7ef36 216: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] new d5179e57a2 217: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] new 2ace6ebf5d 218: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] new 09dbcccc3c 219: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] new ab2f68eb94 220: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] new 16c5ecc63f 221: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new b80306b5cf 222: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new 5c56098269 223: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] new 598ede044a 224: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] new 8c588a0cbd 225: onsuccess: #48: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 2d74ef6e50 226: onsuccess: #49: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 23453b9bfb 227: onsuccess: #50: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 4acf9b17d5 228: onsuccess: #51: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new b8362325c5 229: onsuccess: #52: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new d1f2d1130f 230: onsuccess: #54: 2: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (29261712e0) \ 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 1940 -> 1896 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2428 bytes 04-build_abe-binutils/console.log.xz | Bin 34992 -> 35588 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 300964 -> 301140 bytes 06-check_regression/console.log.xz | Bin 552 -> 548 bytes 07-update_baseline/console.log | 70 ++++++++++++------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 16 +++--- 10 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig updated (ba32d3a363 -> f33234ed6d)

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-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from ba32d3a363 65: onsuccess: #20: 21834: [TCWG CI] https://ci.linaro.org/j [...] new f33234ed6d 66: onsuccess: #21: : [TCWG CI] https://ci.linaro.org/job/tc [...] 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 1972 -> 1948 bytes 02-prepare_abe/console.log.xz | Bin 2412 -> 2432 bytes 03-build_abe-binutils/console.log.xz | Bin 28076 -> 28156 bytes 04-build_abe-stage1/console.log.xz | Bin 71420 -> 71596 bytes 05-build_abe-qemu/console.log.xz | Bin 29700 -> 29868 bytes 06-build_linux/console.log.xz | Bin 8228 -> 8840 bytes 08-check_regression/console.log.xz | Bin 612 -> 1036 bytes 08-check_regression/results.regressions | 12 ++++++++++++ git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 15 +++++++-------- results | 14 +++++++++++++- 12 files changed, 34 insertions(+), 11 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, 2 months

[gcc] branch master updated (6d4ad4cca5d -> 2245459c85a)

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 6d4ad4cca5d PHIOPT: Remove gate_hoist_loads prototype new 60524be1e39 RISC-V: optimize stack manipulation in save-restore new 2245459c85a c++: bound ttp level lowering [PR109531] The 2 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/riscv/riscv.cc | 50 +++++++++++----------- gcc/cp/pt.cc | 39 +++++++++-------- gcc/testsuite/g++.dg/template/canon-type-20.C | 18 ++++++++ gcc/testsuite/g++.dg/template/ttp36.C | 12 ++++++ .../gcc.target/riscv/stack_save_restore.c | 40 +++++++++++++++++ 5 files changed, 116 insertions(+), 43 deletions(-) create mode 100644 gcc/testsuite/g++.dg/template/canon-type-20.C create mode 100644 gcc/testsuite/g++.dg/template/ttp36.C create mode 100644 gcc/testsuite/gcc.target/riscv/stack_save_restore.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (ea10c5a5c5 -> 3b22680a8b)

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-aarch64 in repository toolchain/ci/base-artifacts. discards ea10c5a5c5 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 840605e1a0 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 53498c0fc5 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 6fce410605 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 274be53d03 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a8acfe1582 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards edb7bf2bcd 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards bc65cea118 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 07f2cc3396 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 5be55e8539 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 734d7d80e6 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 4517e1e2d3 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 736e61364a 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d60076c066 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 4dff8fd6f6 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards a38e1ff17d 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 9d5eca028b 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards a29650bad8 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 462026cf0e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 7f75f79fa8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards c62c9b0a2b 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 7374dc120a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 43ccd9d35b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 54f9137a3c 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 6a581a6b48 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 41927e90d9 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 76f7b2ea3d 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards eea0feccdc 127: force: #27: : Failure after baseline build: no new commits discards 41962840f1 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards ef85666416 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 017ddf6eb0 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 6a9d0d490e 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards a2361a7948 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e26c32fb1b 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8ec2d5536f 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 30b380d3b6 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards dec560f05b 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 067f3bd97d 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 0823a15e2c 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 052774f25e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards bf7f3aef90 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 82a12d258b 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 9ff6c36c29 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards c7f4a4e369 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 613d1f43e8 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards f00bdc406a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 4836a622c4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards aebfc5b579 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards befe3ce298 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards e3a45c9bc9 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 575fec0c37 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards bcbad1739f 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 3ea0d4d28c 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards e5c0d25cf6 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards d3612cc239 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 18d75290f0 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 4fdbf4fc14 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 3490eabe48 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 52f9c98f23 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 0fbe107053 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards bcb45df58e 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards c0abcae656 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 4c3fafbdb3 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards c9cb19bac3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards a0ad95b6ef 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 050ee1cfe1 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards aa6777b342 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 01b901881e 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards c122506a9b 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 832b68b8f3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 4786223d34 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5d60e0f8b2 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards fc24179aef 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards a109139c60 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 83ae4b5d55 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 6f512bb30c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards d9a43afb22 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards a0c50803eb 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards fad79bcb92 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 6558f3e596 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 36b9b8c1c9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 788083bee4 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 625067a114 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards f69ef3845b 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 5cbbe20f2f 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards e068d014d3 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 8c4d674acf 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 3284cf79e9 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 611728d06d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards af21a64858 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 2df2e00018 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 4b0e4149e4 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 60cd1ebbe7 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 6286c6e189 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 0e8caa4974 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards d3f2d625f8 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 91acff30ad 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards fc30a74c02 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards c9c76dfdea 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 2393595b88 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 9159522dab 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 68df263038 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new b1841a1c15 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 0c7d762ba1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 25778184cb 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 640ccab5fe 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 7aa34b9087 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 41239cb5fd 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new db74053877 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 614468d6b0 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 89bbea0f8a 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 5ab3f2e51c 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 9eb0deb09c 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 2f2c01b2e6 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 5359b11468 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 331e565e69 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 303ef14f87 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new e4e9e962a5 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 5ab14927b5 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 2b91489146 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 11c77c04d6 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new e45dfede3e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 2ff376f12f 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 373654c8ce 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 05b1b507b7 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new c4c443385a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 454dcfa884 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 2e7aeb6e19 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 6a9a17258a 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 39dd9e8f3a 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 4656f19f60 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new edca9b948c 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 6f30745cd2 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new b9d10954b0 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 8935c03f6a 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 889e2a58ca 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 0525b8af1d 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 9be3c8d91d 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 562f60d14c 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new a15f0c1b87 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 6f6f9763f5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new c7061a2a2d 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 2b40aa2a11 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new d5fa1b195f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new d77ca16f99 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 2d72b594a8 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 6d8187dd59 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new ecd735c43c 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 99b5de7151 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new cef4f57c46 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new a7a08f80d4 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 1fd30647b5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 238456e2ac 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new fd1aa3ad6b 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 43bde4adba 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new b7e9dd8cb3 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 46867f819e 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3b4e35c273 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 7a8371153d 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 558ed251e0 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 8b9890124f 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 4f5b7af083 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 9a760b2e0e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new c501165294 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 8b593e6ad7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 7171dfa583 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new dbb0b32245 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f47a7bac69 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 04ebc0dc7c 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a69c13956e 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new e47ad6fa77 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new d083b009a2 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 1fee0dda4e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 4e88ed7485 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new bba96cd0ef 127: force: #27: : Failure after baseline build: no new commits new 0d9d99efc7 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 871b33b18b 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 4295540714 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 00a1371302 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new ed5cdca2ef 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 78dd74651c 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 6e32405ceb 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 4e3657caf8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 543eae9725 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new ab23c8b058 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new bfdcbee50e 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 441ee2e8eb 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new deb55763b3 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 66e8f934db 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new c31d1a66e1 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 7a2a23e986 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new bdba1a34e3 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new c6f9ea49d0 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new ce0cf31489 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 781060aded 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new db96c4c850 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new d23a270f86 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f10cc2ebfd 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 54853b1f76 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9b56920c33 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new bb93255b7e 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 787810f7e9 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 3b22680a8b 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (ea10c5a5c5) \ 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 2028 -> 2196 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2428 bytes 03-build_abe-binutils/console.log.xz | Bin 35312 -> 35828 bytes 04-build_abe-gcc/console.log.xz | Bin 203788 -> 203380 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8288 bytes 07-build_abe-glibc/console.log.xz | Bin 241520 -> 241564 bytes 08-build_abe-gdb/console.log.xz | Bin 34828 -> 35196 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3916 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1712 -> 3760 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 548 bytes 12-update_baseline/console.log | 40 ++-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 34 +-- results | 2 +- sumfiles/gdb.log.xz | Bin 0 -> 14440 bytes sumfiles/gdb.sum | 409 ++++++++++++++++++++++++++++++++++ sumfiles/xfails.xfail | 0 24 files changed, 454 insertions(+), 45 deletions(-) create mode 100644 sumfiles/gdb.log.xz create mode 100644 sumfiles/gdb.sum create mode 100644 sumfiles/xfails.xfail -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O3_LTO updated (2964f34b07 -> 74a318f96a)

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-coremark/gnu_eabi-arm_eabi-master-O3_LTO in repository toolchain/ci/base-artifacts. from 2964f34b07 78: force: #46: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 74a318f96a 79: force: #48: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] 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 1960 -> 2144 bytes 02-prepare_abe/console.log.xz | Bin 2544 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 27692 -> 28324 bytes 04-build_abe-stage1/console.log.xz | Bin 87488 -> 88144 bytes 06-build_abe-newlib/console.log.xz | Bin 12428 -> 12692 bytes 07-build_abe-stage2/console.log.xz | Bin 162240 -> 163664 bytes 08-benchmark/benchmark-build.log | 96 ++++++++++++----------- 08-benchmark/benchmark.log | 94 +++++++++++----------- 08-benchmark/console.log.xz | Bin 3976 -> 4092 bytes 09-check_regression/bmk-specific-variability.csv | 1 + 09-check_regression/console.log.xz | Bin 2736 -> 5156 bytes 09-check_regression/extra-bisect-params | 1 + 09-check_regression/trigger-bisect | 2 - 09-check_regression/trigger-notify | 0 git/newlib_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- manifest.sh | 10 +-- results-vs-first/tcwg-benchmark-results.log | 4 +- results-vs-prev/compare-results.csv | 2 + results-vs-prev/tcwg-benchmark-results.log | 4 +- results_id | 2 +- 22 files changed, 114 insertions(+), 108 deletions(-) create mode 100644 09-check_regression/bmk-specific-variability.csv create mode 100644 09-check_regression/extra-bisect-params delete mode 100644 09-check_regression/trigger-bisect delete mode 100644 09-check_regression/trigger-notify create mode 100644 results-vs-prev/compare-results.csv -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023