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 (771cdce398 -> 4423b08f40)

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 771cdce398 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards c8fabdfa31 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1728609b35 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 198abf17eb 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7eeaa22eb4 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 880bba8370 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards efac6678d1 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards a58208f3b2 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 53b99e8b36 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards bc54d00084 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 2632060e5c 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 9112f59c85 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 51c5616de6 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards c11372ae1b 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 989871a908 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 444c215f50 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ccd9297ae7 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards f2e8652102 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 74eb509564 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d1072bfbb6 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 370bbcc9e2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 7825ee3f86 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards b91228ff44 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 1f172b9107 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 9ce3f79fcd 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards a6d3aacb14 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 7336111276 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 708c2ab349 212: force: #24: 1: Success after binutils: 2 commits discards 5455eda74d 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8770d43e95 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards c54ffa1427 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards d003382895 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 40f1f4fe0d 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 3b1ac49cb4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ab48b14e03 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 1dc1841e36 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 72f57e9864 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards f1ff805494 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1615c8b744 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 6dd8b8cfbb 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 795de34adf 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards d80dfcd62f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7d958aa674 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 689fa18633 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 0026b89e08 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards ba48c836ea 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 037407000e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 6ab6bc3d06 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 46de3f3b7d 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 13a4a52c8b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 9674e8652b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 0fda204a83 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards d5e1e83f26 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards bc0c74a5b1 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards e9797acc1b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards c52e8ea3be 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 02fce028f4 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 002abd18fa 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 6493f1c245 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 5ebb3b5300 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards bb9d948dcb 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 59bb242bc3 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards b4b6689630 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 840810e613 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 80dd6bac4b 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards ceb4d80780 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards a800c39d85 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards d23cf955f7 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 63eff9d4f8 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 1e41b3dbaa 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards ce324cca81 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards cdb983ad32 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards a4a1cc03f3 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 757938866e 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards eb707e5a4a 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 349150c193 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 2e8fb57560 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 9da8c88a3b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 1ec9e0c305 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards df77fd212d 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards f4bd4cdd6d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 8c45a940a3 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 7dd5fd6ca5 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards a0b4a04ced 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 8576e20dca 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 0f8f440e6b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards fac997567c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards ec09728d1d 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 7afc7d1f6c 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards ff2a6282d5 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 30ed5c1599 149: onsuccess: #684: 1: Success after linux: 10 commits discards 72bf281c2e 148: onsuccess: #683: 1: Success after glibc: 9 commits discards cca5a5cf3c 147: onsuccess: #681: 1: Success after gcc: 6 commits discards dc8262a442 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 16e51309d6 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards f05a8dd3f1 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards d9ff4092fa 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 339018ae3a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 7915902884 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 39f34c3e44 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 4cad5de988 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 4ef217ceed 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 25c7e503a6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 7359cdb18f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new b39ef6b8e3 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 50cd86a5ec 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 267bfaf8f0 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new aeab48b09b 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new f99b8ddfcc 146: onsuccess: #680: 1: Success after binutils: 20 commits new 6973c0c88d 147: onsuccess: #681: 1: Success after gcc: 6 commits new aa03ff027b 148: onsuccess: #683: 1: Success after glibc: 9 commits new 9db7663ec1 149: onsuccess: #684: 1: Success after linux: 10 commits new 347306aaf6 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 3e50c1b9a9 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 5a2c3d7464 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 2e78365c52 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new c68d9d61a2 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 8e87784827 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new a5b24b97b4 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new c73c148116 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 045970016c 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 4ac51af86e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 3066a3c168 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new bc021bf64e 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 41d25f00e9 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 9716adbd69 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new a4077d0161 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new eae5495e74 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new c570383c43 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new bf4237e82e 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new e19bcc65b3 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 87adfd9eae 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 56f25b8078 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new d5bf851e7d 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 7f865e403d 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new e2a7665d31 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 01340a8a80 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 847c3623c2 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new dc1e251a78 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new f5ee21c3c7 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new a1f4897521 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new ff8499c389 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 96b6e056df 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new db8645a6d8 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new bc20be59a3 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new d1790b83b7 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new a9511209e3 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 9ebb8e88fd 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 0d7d5f9b66 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 2eb75d061a 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new f0a2bc392a 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 31773a28ae 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 1ee42c8b20 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 677cc497f6 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 616650e456 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 1c5a5ae3bf 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8e58ad4889 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 0801b41a96 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new e2096e20e5 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new c03e1dfd9e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 392bd8ddf6 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 2ac8f04b40 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 6a06a5ff0f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 216cde5d49 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 1567e93363 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 92b5cf26dd 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f27113c3a5 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 4770e2cc8c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 57b461f82c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 950f8795ae 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new b79aa9623e 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 5da017ccf3 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3e323d693c 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new fedfe9c385 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 1db846b89a 212: force: #24: 1: Success after binutils: 2 commits new b2b5ef0bd0 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new daf55ca643 214: onsuccess: #26: 1: Success after binutils: 12 commits new 0a3035f97d 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new be7376c12c 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 11b58730b5 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 456d013d8a 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 2b257ee1e2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new fbac3465d2 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f609ef8066 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 06b1dc6a56 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new fe9bf6612d 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new ebca4619a3 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new f0d855c823 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 73fd683ecc 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new fd2fe26734 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new eb168b0df2 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 9620bc5e5d 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 4f2ed16635 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new acea9ef875 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 3f0a0aef4c 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new ac8ed50415 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 4d41584ac7 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 687e441c96 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 5097194106 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f513d47f14 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5bcaace0bb 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 34077091c5 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 4423b08f40 240: force: #65: 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 (771cdce398) \ 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 1972 -> 2216 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35196 -> 35672 bytes 04-build_abe-gcc/console.log.xz | Bin 204320 -> 204260 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 241360 -> 240628 bytes 08-build_abe-gdb/console.log.xz | Bin 34656 -> 34608 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2304 -> 3000 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 | 2 +- 12-update_baseline/console.log | 46 ++++++++++++++--------------- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++--- mail/results.regressions | 8 ++--- manifest.sh | 10 +++---- results | 8 ++--- sumfiles/binutils.log.xz | Bin 62620 -> 62812 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150676 -> 150840 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122616 -> 122640 bytes sumfiles/ld.sum | 2 +- 27 files changed, 55 insertions(+), 55 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 (bbb5c669 -> 0c931306)

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 bbb5c669 Add entry fade906daab13c99fc329c1e08447f2aac168b62 from https [...] new 0c931306 Add entry b8d1a3a8ef9aff015ae963522287f7785bc552ec 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 +- .../{master-arm => master-aarch64}/last_good | 0 .../{master-arm => master-aarch64}/summary.txt | 2 +- .../tcwg_gnu_native_check_binutils/status.txt | 13 +++++++++++++ 4 files changed, 15 insertions(+), 2 deletions(-) copy binutils/sha1/{2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b => b8d1a3a8ef9aff015a [...] copy binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/tcwg_gnu_native_check_ [...] copy binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/tcwg_gnu_native_check_ [...] -- 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-stable-allmodconfig updated (e1871bbbca -> a2b15d02f6)

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-stable-allmodconfig in repository toolchain/ci/base-artifacts. from e1871bbbca 60: onsuccess: #12: 23923: [TCWG CI] https://ci.linaro.org/j [...] new a2b15d02f6 61: onsuccess: #13: 23923: [TCWG CI] https://ci.linaro.org/j [...] 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 2004 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2560 bytes 03-build_abe-binutils/console.log.xz | Bin 27300 -> 27704 bytes 04-build_abe-stage1/console.log.xz | Bin 71248 -> 71956 bytes 05-build_abe-qemu/console.log.xz | Bin 30220 -> 30888 bytes 06-build_linux/console.log.xz | Bin 9532 -> 10192 bytes 08-check_regression/console.log.xz | Bin 1312 -> 608 bytes dashboard/dashboard-generate.sh | 17 ------------- dashboard/dashboard-push.sh | 7 ------ dashboard/squad-vs-first/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 7 ------ jenkins/notify.sh | 2 +- manifest.sh | 30 +++++++++++------------ 17 files changed, 19 insertions(+), 53 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/results-functional.json delete mode 100755 jenkins/dashboard-push.sh -- 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/llvm-master-aarch64-next-allmodconfig updated (e3f37f8649 -> 87c74714b7)

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-allmodconfig in repository toolchain/ci/base-artifacts. from e3f37f8649 92: onsuccess: #17: all: [TCWG CI] https://ci.linaro.org/job [...] new 87c74714b7 93: onsuccess: #19: all: [TCWG CI] https://ci.linaro.org/job [...] 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 -> 1948 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 27264 -> 27184 bytes 04-build_kernel_llvm/console.log.xz | Bin 64736 -> 65256 bytes 05-build_abe-qemu/console.log.xz | Bin 31140 -> 30852 bytes 06-build_linux/console.log.xz | Bin 2972 -> 3068 bytes 08-check_regression/console.log.xz | Bin 1212 -> 524 bytes 09-update_baseline/console.log | 9 +++++++ dashboard/dashboard-generate.sh | 17 ------------- dashboard/dashboard-push.sh | 7 ------ dashboard/squad-vs-first/results-functional.json | 1 - git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 7 ------ jenkins/notify.sh | 2 +- manifest.sh | 29 ++++++++++------------- 17 files changed, 26 insertions(+), 52 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/results-functional.json delete mode 100755 jenkins/dashboard-push.sh -- 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_check_gdb/master-arm updated (64be7a05a2 -> fb7fa9b597)

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_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 64be7a05a2 263: force: #154: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards bfb77ea47f 262: onsuccess: #146: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 078afa0222 261: onsuccess: #145: 1: [TCWG CI] https://ci.linaro.org/job [...] discards d5fd6d13bf 260: force: #144: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 53902f4c07 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] discards c602d5ff5d 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] discards e32f6dfa89 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] discards 4548646df7 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] discards d2fbba451d 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] discards 9ef72ca3aa 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits discards 2e99270bfe 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards e6e4514be8 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards 356f4ec47a 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards de6e220dcf 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards 3599eaf050 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards e60a12555f 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards 14fe3553e2 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards efdca239aa 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards 0a93f86118 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 81e76587d7 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards f474e43762 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards fd2c3faa0b 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 0e3d452309 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 7c3020eef6 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards 64c3396f80 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards e06ca4a89c 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards d6aa480edb 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 4aba23ef0b 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards a82733d2f4 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 2c98fd4c08 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 8c7e03860b 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards d80b60d483 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 932793954a 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 3b3ee380d7 230: onsuccess: #78: 1: Success after gdb: 2 commits discards d4bd456ea4 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 531c0aa1ed 228: force: #74: 1: Success after gdb: 53 commits discards bab634321f 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 01f740ccac 226: force: #70: 1: Success after baseline build: no new commits discards 48ead27c17 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 464ea28858 224: force: #65: 1: Success after gdb: 50 commits discards f8e37e2e01 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards d11d0e5937 222: force: #60: 1: Success after gdb: 16 commits discards 6f10c7cf68 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards d27daed8a6 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 23ea8d9e22 219: force: #50: 1: Failure after linux: 2520 commits discards 02f63395f7 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards ab70d9ae56 217: force: #45: 1: Success after linux: 1 commits discards 8265f88c98 216: force: #43: : Failure after baseline build: no new commits discards 0bfefbb007 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 38c0d7ad78 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 34ee60a135 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards c61b434a45 212: force: #27: : Failure after baseline build: no new commits discards 37ec7da6b5 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 2ebd9e0edd 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 83e5cdcfd9 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 928e49a6da 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards d4545a6f6f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 1e88c36885 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 77bbbfd043 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 8ae887d8f6 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 249181bf0f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 4290915c61 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards ed22dab5a4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards e03d0016e9 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7a89e1e39a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 564d024bc2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 381375dac0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4a19272668 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 5d41286f11 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 504d7b6040 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards edba8bb8b5 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards e3ffd23884 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 4a324ec01a 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards ce50532f20 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards f6745487a4 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards a36ceaa6c3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 8c74c61ae7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 3c7917152d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 6c59b17b13 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards ca43071200 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 2f9bee385f 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 35d090bac2 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards db850d4ca6 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards ced0f88c50 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 51a96112cf 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 9b53dc1e2f 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards dee1321d85 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 14e8ce7261 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards e3e707e95c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards b50eebed55 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 4d1f9b9210 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards f722a6cba2 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 318be56140 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards d49f013333 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 3bb0bb4f00 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 7948f29606 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards aa2634de5e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 71cffd7843 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 2f5012d119 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 3aeb54fc54 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards d4104b8e3a 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 5593124478 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 112701ce79 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new ecbd5829ba 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 01d9a5d1d1 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new a9ce62e166 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new cca6ddf23e 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new bef9ee6aa8 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 0fb914721f 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new b6ac885be5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 056483810d 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 598e7498fc 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 1e8d73e1e8 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new aa42027328 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new b6907d3f87 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 316895edd4 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new c23e6ec44f 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 9128f9c65c 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 4ce6ee13ef 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 722a582203 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new eab1ac1e6b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 4211bb9bd6 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 54e43dd22c 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new d999bb4f43 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 34e9dd67bf 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 69411dc284 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new a7287f28da 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 0511636174 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 4e117053a0 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 511902766c 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 66c4866a56 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 82e06a0369 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 18ae656e84 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 907119c1b5 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 29679d2074 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new cd397ab80a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new e03c73cb85 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 7fcba3baad 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 8edc6c2156 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new fafd083475 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new f35936685d 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 277a513f6f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 384c35141e 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 8996274b13 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 848fd3c29f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new d89e3fd954 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 9995df7414 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 0f189a23b0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new adaa62bf54 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 9b95fa39ad 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new c1ce545454 212: force: #27: : Failure after baseline build: no new commits new 558ed76161 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 56fe0a5446 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 8f065672e6 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new be227250fe 216: force: #43: : Failure after baseline build: no new commits new 092ad01dfd 217: force: #45: 1: Success after linux: 1 commits new 098a592581 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new f8dd3d9d8e 219: force: #50: 1: Failure after linux: 2520 commits new 7642893572 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 860a36f1c3 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new dafd088d03 222: force: #60: 1: Success after gdb: 16 commits new dfe25a5ab2 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new ee5e097bb3 224: force: #65: 1: Success after gdb: 50 commits new c704910c26 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 044823f954 226: force: #70: 1: Success after baseline build: no new commits new 0c34c9d4ca 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new f7de627186 228: force: #74: 1: Success after gdb: 53 commits new 110eb115ff 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 00d05143dc 230: onsuccess: #78: 1: Success after gdb: 2 commits new 8ec450923a 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 6e58aa95d7 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 073533bc14 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 083592ccbc 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 2c36113b08 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new ee0d4fed7d 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 969003e336 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new afc7c7f244 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new a024f22fac 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new f7e7ed6bcb 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new f52ddc09f7 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new 5552426a96 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 280beeda8e 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 381ddd0450 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new e354b93784 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new 81afce56a8 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new b1ad9a1a34 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new d68df489c2 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new f5ca20fc5b 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new 8343c3f494 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new 3b6c67b983 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new ef1d14c360 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 008f960845 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 32519eaaef 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits new beb3d1a100 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] new 4f5972210d 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] new 6c4a4a4379 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] new d12338b94b 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] new fc3bc9c286 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] new 0cc0644867 260: force: #144: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 83b7e92b33 261: onsuccess: #145: 1: [TCWG CI] https://ci.linaro.org/job [...] new 7de05d0152 262: onsuccess: #146: 1: [TCWG CI] https://ci.linaro.org/job [...] new 243901fee5 263: force: #154: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new fb7fa9b597 264: onsuccess: #155: 0: [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 (64be7a05a2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2232 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 48868 -> 49020 bytes 04-build_abe-gcc/console.log.xz | Bin 236452 -> 236288 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8900 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 233044 -> 232932 bytes 08-build_abe-gdb/console.log.xz | Bin 46444 -> 46200 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3824 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1328 -> 1328 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 952 -> 548 bytes 11-check_regression/results.regressions | 3 -- 12-update_baseline/console.log | 48 ++++++++++++++++---------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- manifest.sh | 31 ++++++++++++--------- results | 3 -- 23 files changed, 50 insertions(+), 51 deletions(-) delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (06145c82e8 -> fa678383f5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. discards 06145c82e8 213: onsuccess: #58: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 00b0629ec5 212: onsuccess: #57: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7c6dae17f3 211: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards b0b912ad6e 210: onsuccess: #55: 2: [TCWG CI] https://ci.linaro.org/job/ [...] discards a7c5833dd8 209: onsuccess: #54: 2: [TCWG CI] Success after binutils/gcc [...] discards 35e6273b07 208: onsuccess: #53: 2: [TCWG CI] Success after binutils/gcc [...] discards cc622827a6 207: onsuccess: #52: 2: [TCWG CI] Success after binutils/gcc [...] discards 348c027d0d 206: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] discards a9af3092fd 205: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] discards e862f0b354 204: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] discards 9d76101be8 203: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] discards b32076983a 202: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] discards 3404840b11 201: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards e7b52c5012 200: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards 8dbcd1042d 199: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] discards 5a9b90473f 198: onsuccess: #42: 1: [TCWG CI] Success after gcc: 16 commits discards 989318873d 197: force: #41: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] discards 4c195a5f41 196: force: #40: 2: [TCWG CI] Success after gcc: 36 commits discards f8442749de 195: onsuccess: #38: 2: [TCWG CI] Success after binutils: 69 [...] discards 75a2f8b7e8 194: onsuccess: #35: 2: Success after binutils/gcc: 7 commits discards 9caa6220e3 193: onsuccess: #34: 2: Success after binutils/gcc: 3 commits discards 4bb9f4cb76 192: onsuccess: #33: 2: Success after binutils/gcc: 35 commits discards e955316bf2 191: onsuccess: #32: 2: Success after binutils/gcc: 31 commits discards 51b09499b6 190: onsuccess: #31: 2: Success after binutils/gcc: 30 commits discards 9e5216e6dd 189: onsuccess: #30: 2: Success after binutils/gcc: 45 commits discards 5094a4a334 188: onsuccess: #29: 2: Success after binutils/gcc: 31 commits discards e7eaa8c58b 187: onsuccess: #28: 2: Success after binutils/gcc: 16 commits discards 6031dd9121 186: onsuccess: #27: 2: Success after binutils/gcc: 29 commits discards 7a74b6a471 185: onsuccess: #26: 2: Success after binutils/gcc: 44 commits discards fdb334fbc0 184: onsuccess: #25: 2: Success after binutils/gcc: 36 commits discards 18afb1a96a 183: onsuccess: #24: 2: Success after binutils/gcc: 38 commits discards 826a2ba7e4 182: onsuccess: #23: 2: Success after binutils/gcc: 42 commits discards b3af363ca8 181: onsuccess: #22: 2: Success after binutils/gcc: 59 commits discards e9272f5654 180: onsuccess: #21: 2: Success after binutils/gcc: 13 commits discards f8346cf6e7 179: onsuccess: #20: 2: Success after binutils/gcc: 14 commits discards 70224d6471 178: onsuccess: #19: 2: Success after binutils/gcc: 60 commits discards f600f76ae8 177: onsuccess: #18: 2: Success after binutils/gcc: 34 commits discards 6ec34d3658 176: onsuccess: #17: 2: Success after binutils/gcc: 42 commits discards 9659513d36 175: onsuccess: #16: 0: Success after binutils: 24 commits discards 9d28ee1729 174: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] discards 56218b7945 173: force: #14: 2: Success after binutils: 10 commits discards c62330e0b4 172: onsuccess: #12: 2: Success after binutils/gcc: 41 commits discards 6da7d75be0 171: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 38304a365a 170: onsuccess: #10: 2: Success after binutils/gcc: 11 commits discards 0e56ae4b01 169: onsuccess: #9: 2: Success after binutils/gcc: 50 commits discards ba96bf917e 168: onsuccess: #8: 2: Success after binutils/gcc: 35 commits discards f39de09645 167: onsuccess: #7: 2: Success after binutils/gcc: 395 commits discards 328fdc4c0c 166: onsuccess: #581: 2: Success after binutils/gcc: 190 commits discards 1e5f163b5f 165: onsuccess: #575: 2: Success after binutils/gcc: 86 commits discards 2caedfedb7 164: onsuccess: #574: 2: Success after binutils/gcc: 114 commits discards 852b2319ed 163: onsuccess: #572: 2: Success after binutils/gcc: 147 commits discards 1b505ab2c6 162: onsuccess: #571: 2: Success after binutils/gcc: 75 commits discards 724f8ba20b 161: onsuccess: #570: 2: Success after binutils/gcc: 57 commits discards 5549b1fed9 160: onsuccess: #568: 2: Success after binutils/gcc: 20 commits discards d11e3dffcf 159: onsuccess: #567: 2: Success after binutils/gcc: 28 commits discards 3db3dffb9a 158: onsuccess: #566: 2: Success after binutils/gcc: 7 commits discards 6ea95287cc 157: onsuccess: #565: 2: Success after binutils/gcc: 79 commits discards 146d3ed55d 156: onsuccess: #562: 2: Success after binutils/gcc: 47 commits discards f4cd1937d8 155: onsuccess: #561: 2: Success after binutils/gcc: 108 commits discards 315ce66e55 154: onsuccess: #560: 2: Success after binutils/gcc: 59 commits discards 72b9894eab 153: onsuccess: #558: 2: Success after binutils/gcc: 28 commits discards 607dc6d966 152: onsuccess: #556: 2: Success after binutils/gcc: 129 commits discards f0ae1c44a6 151: onsuccess: #555: 2: Success after binutils/gcc: 27 commits discards 98cd0837c6 150: onsuccess: #554: 2: Success after binutils/gcc: 80 commits discards addbe6e889 149: onsuccess: #553: 2: Success after binutils/gcc: 28 commits discards 7c1188baff 148: onsuccess: #552: 2: Success after binutils/gcc: 35 commits discards 8f82c6df70 147: onsuccess: #551: 2: Success after binutils/gcc: 6 commits discards 8a1c5573c1 146: onsuccess: #550: 2: Success after binutils/gcc: 39 commits discards 9d4b867efd 145: onsuccess: #549: 2: Success after binutils/gcc: 33 commits discards d2bcc6f47d 144: onsuccess: #548: 2: Success after binutils/gcc: 35 commits discards 3cf8ab7052 143: onsuccess: #547: 2: Success after binutils/gcc: 77 commits discards 1166be6d57 142: onsuccess: #546: 2: Success after binutils/gcc: 37 commits discards c230ab85aa 141: onsuccess: #545: 2: Success after binutils/gcc: 123 commits discards c698a0a437 140: onsuccess: #544: 2: Success after binutils/gcc: 46 commits discards a8467ef411 139: onsuccess: #543: 2: Success after binutils/gcc: 111 commits discards 7d7bf36607 138: onsuccess: #542: 2: Success after binutils/gcc: 35 commits discards 12f5d7cf42 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits discards 0810e67846 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits discards 70d254a17b 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits discards cf99226eff 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits discards 156b008f0b 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits discards fcf4479c36 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits discards 0c4182df13 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits discards a4752a43a2 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits discards bb8739eb8d 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 64cc480611 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits discards 8bad176548 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits discards 79bc3d0ef1 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits discards 75d71553b2 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits discards e93113e6cc 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits discards ca01637f0e 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits discards 69ed4f3e65 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits discards b5fe7d09a8 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits discards 2a2956d678 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits discards 86bde1c38e 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits discards 12c067a7b3 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits discards 6d7d844562 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits discards 038b66d771 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits discards d53ad02a9f 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits discards 56371fd41c 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits discards 2b0af6f156 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits new efd8885b0c 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits new f2ade5d480 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits new 80bb6684a3 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits new bd881327be 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits new e0d6be180a 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits new 299f02e69b 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits new f115ac8cab 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits new bcb811fc95 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits new 0217781457 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits new b5a96d9355 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits new 03190eda7a 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits new e150729240 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits new 8c3a6f019d 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits new 03416ba52e 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits new 59d04956e0 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits new 94edca43b9 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits new 47449c5653 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new 78f5306a4b 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits new 23295ec502 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits new e4eaf91b3d 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits new 720a15ebe1 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits new cf8a3e3cfb 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits new e08db697af 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits new 926a0294a1 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits new d1e7bade24 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits new ccdbd438a1 138: onsuccess: #542: 2: Success after binutils/gcc: 35 commits new d135e1580a 139: onsuccess: #543: 2: Success after binutils/gcc: 111 commits new 60955a7804 140: onsuccess: #544: 2: Success after binutils/gcc: 46 commits new dca14c4b62 141: onsuccess: #545: 2: Success after binutils/gcc: 123 commits new c17f5356f6 142: onsuccess: #546: 2: Success after binutils/gcc: 37 commits new f4d2eba9e1 143: onsuccess: #547: 2: Success after binutils/gcc: 77 commits new a377d45293 144: onsuccess: #548: 2: Success after binutils/gcc: 35 commits new 9306241275 145: onsuccess: #549: 2: Success after binutils/gcc: 33 commits new 7730c2b46d 146: onsuccess: #550: 2: Success after binutils/gcc: 39 commits new dacb488935 147: onsuccess: #551: 2: Success after binutils/gcc: 6 commits new 36d28b6dcd 148: onsuccess: #552: 2: Success after binutils/gcc: 35 commits new 3498eebaac 149: onsuccess: #553: 2: Success after binutils/gcc: 28 commits new dd1f358e0b 150: onsuccess: #554: 2: Success after binutils/gcc: 80 commits new 98616519ab 151: onsuccess: #555: 2: Success after binutils/gcc: 27 commits new 119018e18f 152: onsuccess: #556: 2: Success after binutils/gcc: 129 commits new 110c1d470e 153: onsuccess: #558: 2: Success after binutils/gcc: 28 commits new eacec0d85f 154: onsuccess: #560: 2: Success after binutils/gcc: 59 commits new ecb672db05 155: onsuccess: #561: 2: Success after binutils/gcc: 108 commits new 76c250c78b 156: onsuccess: #562: 2: Success after binutils/gcc: 47 commits new c0fa08b350 157: onsuccess: #565: 2: Success after binutils/gcc: 79 commits new 052bc61112 158: onsuccess: #566: 2: Success after binutils/gcc: 7 commits new b7fc9da5bb 159: onsuccess: #567: 2: Success after binutils/gcc: 28 commits new 725f8079e2 160: onsuccess: #568: 2: Success after binutils/gcc: 20 commits new b703b7c101 161: onsuccess: #570: 2: Success after binutils/gcc: 57 commits new 500a79dcab 162: onsuccess: #571: 2: Success after binutils/gcc: 75 commits new f6df4a94aa 163: onsuccess: #572: 2: Success after binutils/gcc: 147 commits new a2f4f61eff 164: onsuccess: #574: 2: Success after binutils/gcc: 114 commits new afb56fe0c9 165: onsuccess: #575: 2: Success after binutils/gcc: 86 commits new 1807e044fe 166: onsuccess: #581: 2: Success after binutils/gcc: 190 commits new d4fd750d46 167: onsuccess: #7: 2: Success after binutils/gcc: 395 commits new 5177fa2baa 168: onsuccess: #8: 2: Success after binutils/gcc: 35 commits new 754c6f1e20 169: onsuccess: #9: 2: Success after binutils/gcc: 50 commits new efd016d0db 170: onsuccess: #10: 2: Success after binutils/gcc: 11 commits new c3a0d5a5d6 171: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new aed599883b 172: onsuccess: #12: 2: Success after binutils/gcc: 41 commits new a098c92563 173: force: #14: 2: Success after binutils: 10 commits new c55f44df65 174: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] new 42febc4d95 175: onsuccess: #16: 0: Success after binutils: 24 commits new 32dae92f3e 176: onsuccess: #17: 2: Success after binutils/gcc: 42 commits new 0c7c69be8f 177: onsuccess: #18: 2: Success after binutils/gcc: 34 commits new 61fa54d4d5 178: onsuccess: #19: 2: Success after binutils/gcc: 60 commits new 3d0e59ec9c 179: onsuccess: #20: 2: Success after binutils/gcc: 14 commits new abba4b407f 180: onsuccess: #21: 2: Success after binutils/gcc: 13 commits new 464bbc495f 181: onsuccess: #22: 2: Success after binutils/gcc: 59 commits new 50f7b84955 182: onsuccess: #23: 2: Success after binutils/gcc: 42 commits new 1b25dd4394 183: onsuccess: #24: 2: Success after binutils/gcc: 38 commits new c667a87750 184: onsuccess: #25: 2: Success after binutils/gcc: 36 commits new 9433b6977f 185: onsuccess: #26: 2: Success after binutils/gcc: 44 commits new 572829e04a 186: onsuccess: #27: 2: Success after binutils/gcc: 29 commits new 2d759eae2a 187: onsuccess: #28: 2: Success after binutils/gcc: 16 commits new ee7d35790e 188: onsuccess: #29: 2: Success after binutils/gcc: 31 commits new 8539136acc 189: onsuccess: #30: 2: Success after binutils/gcc: 45 commits new 344f9ce8ae 190: onsuccess: #31: 2: Success after binutils/gcc: 30 commits new 8ca3c86fef 191: onsuccess: #32: 2: Success after binutils/gcc: 31 commits new 54f2800764 192: onsuccess: #33: 2: Success after binutils/gcc: 35 commits new ba8b284e1b 193: onsuccess: #34: 2: Success after binutils/gcc: 3 commits new 2a57bf5a4c 194: onsuccess: #35: 2: Success after binutils/gcc: 7 commits new ed02662138 195: onsuccess: #38: 2: [TCWG CI] Success after binutils: 69 [...] new 278975d6c1 196: force: #40: 2: [TCWG CI] Success after gcc: 36 commits new 88161d3134 197: force: #41: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] new f2bf816bfa 198: onsuccess: #42: 1: [TCWG CI] Success after gcc: 16 commits new 7bceb4543e 199: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] new 7852949d4a 200: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new ad95feea7a 201: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new 879b8aa5dc 202: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] new e3b7a75be7 203: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] new 4802563bac 204: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] new f5c9624a20 205: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] new 7765c2b674 206: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] new af1ac90dfb 207: onsuccess: #52: 2: [TCWG CI] Success after binutils/gcc [...] new 18628b063a 208: onsuccess: #53: 2: [TCWG CI] Success after binutils/gcc [...] new b9078c91f6 209: onsuccess: #54: 2: [TCWG CI] Success after binutils/gcc [...] new 21d1e01c7c 210: onsuccess: #55: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 06f730a0ef 211: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new a0888855c0 212: onsuccess: #57: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new 8202bc7935 213: onsuccess: #58: 2: [TCWG CI] https://ci.linaro.org/job/ [...] new fa678383f5 214: onsuccess: #59: 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 (06145c82e8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1940 -> 2116 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2524 bytes 04-build_abe-binutils/console.log.xz | Bin 48476 -> 48648 bytes .../console.log.xz | Bin 602688 -> 602820 bytes 06-check_regression/console.log.xz | Bin 552 -> 552 bytes 07-update_baseline/console.log | 70 ++++++++++----------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 14 ++--- 10 files changed, 45 insertions(+), 45 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_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O3_LTO updated (dd110998b3 -> bbc2bb4c75)

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 dd110998b3 74: force: #38: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new bbc2bb4c75 75: force: #40: 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 2088 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 26884 -> 27024 bytes 04-build_abe-stage1/console.log.xz | Bin 87576 -> 87828 bytes 06-build_abe-newlib/console.log.xz | Bin 12480 -> 12556 bytes 07-build_abe-stage2/console.log.xz | Bin 162000 -> 162736 bytes 08-benchmark/benchmark-build.log | 90 ++++++++++++++-------------- 08-benchmark/benchmark.log | 88 +++++++++++++-------------- 08-benchmark/console.log.xz | Bin 4048 -> 4040 bytes 09-check_regression/console.log.xz | Bin 2736 -> 2756 bytes 09-check_regression/trigger-bisect | 4 +- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 8 +-- results-vs-first/tcwg-benchmark-results.log | 2 +- results-vs-prev/tcwg-benchmark-results.log | 4 +- results_id | 2 +- 17 files changed, 101 insertions(+), 101 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 (ec22a4a2 -> bbb5c669)

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 ec22a4a2 Add entry 2134fcfee8b338a6f10273457145fc071dc8f092 from https [...] new bbb5c669 Add entry fade906daab13c99fc329c1e08447f2aac168b62 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: binutils/gdb-13-branchpoint-1898-gfade906daab | 1 + .../gnu_eabi-arm_eabi-master-O3_LTO/build_url | 2 +- .../gnu_eabi-arm_eabi-master-O3_LTO/last_good | 1 + .../gnu_eabi-arm_eabi-master-O3_LTO/summary.txt | 8 +++---- .../tcwg_bmk-code_speed-coremark/status.txt | 26 +++++++++++++--------- 5 files changed, 22 insertions(+), 16 deletions(-) create mode 120000 binutils/gdb-13-branchpoint-1898-gfade906daab copy binutils/sha1/{ca26b8030e8c184bdeca7280e31c10c6e9fc3f78 => fade906daab13c99fc [...] create mode 100644 binutils/sha1/fade906daab13c99fc329c1e08447f2aac168b62/tcwg_bmk [...] copy {gcc/sha1/d339e9802f758e051b0a1ef6db732ff846cbf4e3 => binutils/sha1/fade906da [...] copy {gcc/sha1/d339e9802f758e051b0a1ef6db732ff846cbf4e3 => binutils/sha1/fade906da [...] -- 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_check_binutils/master-arm updated (82e5cb4afd -> 8a9411c75f)

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-arm in repository toolchain/ci/base-artifacts. discards 82e5cb4afd 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards cce5d46bb8 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards e81b6a8692 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 55591dfb99 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards eeb2bd0c8f 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 040240ad3d 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 39e5b717dc 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 2876191fe8 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards b2e855f87e 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 43e8c0ba1e 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1a4561b97f 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 496eae0edd 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 0db3e58492 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 43decccef9 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 7f373a8a95 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 121f2471e9 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 52b6abf3b9 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 1433fa18a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 23132dc147 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards ca14037e01 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 82d19be59e 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 51350e4574 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 130080b5ff 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards d944736cd3 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards d5f05eb858 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 9b2930acff 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 2c126c3743 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 6a9d428314 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 5fa48545b2 215: onsuccess: #26: 1: Success after binutils: 10 commits discards a48e0c7ca8 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 8e7a6372c0 213: force: #24: 1: Success after binutils: 2 commits discards 5744b45fca 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 18c1dc4f8d 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards f2ecc8ea53 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards e552e253da 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 69c98ed286 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 17d940ba98 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 4b080c673f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards a1193d9b5b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards afdd0d1d06 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1688e250d0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards ebb3e73b1a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards d7e9239a2a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 3561c3949a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards cc621bd3cf 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 68246e81df 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 5378f123d2 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e0f326bb0c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 607ac5e5fa 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 0302295643 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 7e2954f799 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 0386ea237a 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 7d4510b20b 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 654e5abbae 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 82fde81bc2 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards df73088f55 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 8256880019 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards 1a5e9f41ad 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 4c51adfcd3 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards ccd1485c95 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards ccf4dfbb94 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards ae05ca0e3e 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 874d506e49 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 9e3a9abdb8 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards bdd18100cd 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards a4de8b8ca9 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards a7d9085c2c 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 71b8d686b4 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards da6047524f 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 8bfbbc6e58 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 61e8397f56 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards a4e872998a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 1ca1f619ea 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards a68c36b650 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards c65f82292d 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 78ac2b4812 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards bc1bff2e77 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 44df1c7d7b 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards be60b70530 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 96d2132504 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards e6d9920d73 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 697202a16a 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards c303cf64cd 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards d9b1542b89 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards fddb970158 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 3fa7d860ce 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 00f62df265 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 0d2496d01b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 94683d4bb3 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 9d6afa7e50 154: onsuccess: #583: 1: Success after linux: 10 commits discards 70d4add427 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 70e094bba1 152: onsuccess: #580: 1: Success after gcc: 6 commits discards f0541a54a8 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 0e466b8350 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 90f9f62064 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 00eb590df9 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards fb5030b43e 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 8035946959 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards a35e9115d4 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 35ca02f27c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards b3c14cbe8b 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new a9c498437e 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new c9419b24f9 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 329f291332 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new c254655f8c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 66d3ed1ecf 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 3ed73e91b1 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 08d3db46c3 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 8d78b2d3ba 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new c6216410ff 151: onsuccess: #579: 1: Success after binutils: 21 commits new 2b24168a06 152: onsuccess: #580: 1: Success after gcc: 6 commits new 00af46f5d7 153: onsuccess: #582: 1: Success after glibc: 9 commits new 562cca4b81 154: onsuccess: #583: 1: Success after linux: 10 commits new 67a6464e71 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 01ba643934 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 7278126480 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new d58c0b33f2 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new dc10b8ba72 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 194226bdb6 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 8be8256de1 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 413b2309a0 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new e3725f3e08 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 99c4ef015c 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new b85ec9aeb7 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new cce9219706 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 70436f10de 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 55f18433d3 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 66ee325176 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new c6d4c492cf 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 7bca46d216 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new b7424e9804 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 35ff3e3489 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new b86d879a19 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 498bbf2e57 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 74a2cf2140 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 73ebc1c407 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 787439a098 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 7e856f6b93 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new db5498ac6e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new d26f721b9b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 0877973277 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new a70ceab67b 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new da008d977d 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new c032445da7 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new a992134d04 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new e80d679494 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new 44f495b55f 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 626b7738cc 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 09de3cdb50 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new d66ca29593 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new d08c158614 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 6f52eee66f 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 55c40855c4 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 28c7613931 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4514839688 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new a36eec4294 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b3170d23e5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new eb0a34dc19 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 0d2f12d578 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f9eca89737 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 3fbb881f00 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new b8b3fe97af 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 98d41cc764 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new dd859c3f17 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new d87232228d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 833d34a82d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 3e21b0ec45 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f59018d451 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 94cd46d2a6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2b79367a03 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new f2ca01476b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 3dcc623cf8 213: force: #24: 1: Success after binutils: 2 commits new 486b90b700 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new f3f0e48838 215: onsuccess: #26: 1: Success after binutils: 10 commits new 0bd4a77594 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new c3b41db06d 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 94135bc5c3 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 3bce1fd6e7 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 064f7447df 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 9c0b5b8a89 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 78cf88b960 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 32e6e09cf2 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 33a831a2c0 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 3b07c842e8 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 0e7899f8a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 7183a48e79 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 2bba3677b8 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 61e4831f2a 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8f8a02d159 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new a97acaa86f 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new c31513f171 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 990d0aef04 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8e2b2f5f9b 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 37773fb565 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 2f4ef10de0 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new cb20c0d00f 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 00378f76c7 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 398cba2a4b 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0a43d565a1 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8a3d09756e 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 50374da001 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 3df2d79599 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 8a9411c75f 244: force: #67: 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 (82e5cb4afd) \ 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 2176 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 49896 -> 50120 bytes 04-build_abe-gcc/console.log.xz | Bin 236504 -> 236604 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8904 -> 8952 bytes 07-build_abe-glibc/console.log.xz | Bin 235272 -> 233040 bytes 08-build_abe-gdb/console.log.xz | Bin 46728 -> 46604 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3888 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3024 -> 3072 bytes 11-check_regression/console.log.xz | Bin 1604 -> 1628 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.regressions | 8 +++--- 11-check_regression/trigger-bisect | 4 +-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++--- mail/results.regressions | 8 +++--- manifest.sh | 8 +++--- results | 8 +++--- sumfiles/binutils.log.xz | Bin 62476 -> 62016 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100592 -> 100576 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132300 -> 132344 bytes sumfiles/ld.sum | 2 +- 27 files changed, 54 insertions(+), 54 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 (264daddf -> ec22a4a2)

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 264daddf Add entry 7639bf34fa1942b0a56a0ba441637c1ce75e1127 from https [...] new ec22a4a2 Add entry 2134fcfee8b338a6f10273457145fc071dc8f092 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-7177-g2134fcfee8b | 1 + .../master-arm/build_url | 2 +- .../master-arm/last_good | 1 + .../master-arm/summary.txt | 11 ++++++ .../tcwg_gnu_native_check_binutils/status.txt | 45 ++++++++++++++++++++++ 5 files changed, 59 insertions(+), 1 deletion(-) create mode 120000 gcc/basepoints/gcc-13-7177-g2134fcfee8b copy {binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec => gcc/sha1/2134fcfee [...] create mode 100644 gcc/sha1/2134fcfee8b338a6f10273457145fc071dc8f092/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/2134fcfee8b338a6f10273457145fc071dc8f092/tcwg_gnu_nati [...] create mode 100644 gcc/sha1/2134fcfee8b338a6f10273457145fc071dc8f092/tcwg_gnu_nati [...] -- 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