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 4598fb8e9b 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 1bf21de603 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 7173e12341 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards db835cec10 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards e3d523dace 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards ae6f7f5f2b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 2dcfaef0c6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 858b6c9f60 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 979814e821 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 12083f0608 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 4e5808643f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 1f8fb2921b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 2a44c7666c 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 36b752b26f 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards d33f37f2d8 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 00211691b6 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 06857203fc 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 566185caae 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards c53bd5ff55 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 3dacb83820 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 8cd0b974d5 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards a2f1ca6b3b 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 80b007e7b3 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 2e3ace197f 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 3ee7b45c6b 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 377ec5e4c2 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 8275afe1de 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 7c3b9ab93b 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards b966db0449 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 873484615b 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 39ca2b65bf 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards ecb3b28604 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 3f3d94ed46 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 87d6064b53 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8222239db1 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 57f70a99c4 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 5c1d9581cb 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 84d9eb3c88 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 0789a38c27 125: onsuccess: #614: 1: Success after linux: 12 commits discards f94f938fa1 124: onsuccess: #612: 1: Success after binutils: 18 commits discards e7337c461e 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 6a5a1e9dc0 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 97d4434cc4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards f3db0ab1c0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards aa9b43c49f 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards f35546dd24 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 4328ac8d2b 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 9ef6400f15 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards ee4d7bea96 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards a4c16d6ce3 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards fba61fcbee 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 7baf485bbd 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards d5a276679d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 3ab1afc41c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards c31394c079 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards e039280bf2 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 36902a26e4 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 075d853a10 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 08fff4fb7d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 5ec099f5af 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 0146ac6b26 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 306b5cae23 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 8143317db6 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards cba631cc90 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 7ed48f41b8 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 59d2f307f3 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards bdf354bb38 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards ac575494b0 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards d1569e5688 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 706aaf1671 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 82de2be767 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards d5a0182a22 92: onsuccess: #575: 1: Success after linux: 34 commits discards 42e9459b5e 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 40ebf0d499 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 17bc98ce7b 89: onsuccess: #570: 1: Success after linux: 11 commits discards 800fff1586 88: onsuccess: #569: 1: Success after glibc: 10 commits discards c96c3d8b41 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 77f16be738 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 297c81288a 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 3df9552444 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 758286b5f1 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards c50ae79cab 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 1ef089e631 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 49b6825f46 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 26057d2fa5 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards cd1da1dc6c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 9a3ed47fc8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 4ede0b6b62 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 6d64a73198 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards d982b7f39a 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards b067cdfb7f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards f359c15cfe 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 6acb8e4537 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 43d70e1edf 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 42f703ef44 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 1e017ce809 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards b69105a00e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 1695ae6180 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 1763885486 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 8286ebda7f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards feeb0a4b75 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new afc41cc5a5 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 27ae63c048 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 78bd3ccd81 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 56b81acc4b 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 129cd36af2 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new eef6a4f980 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 3e2b9c5c34 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new ae5b6fcd16 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 9250f8c99c 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 96fe16be37 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new e9bb50516f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 328cc67336 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new e9ecb2fe39 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 373aed3151 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 11312ec788 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new afe807d0c7 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 6fe44cf12d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 60462e6c2a 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 4030097922 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 62db076dae 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new cf85425442 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 8fdefaaf77 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new f8949ab7e6 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 126cb29c4a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new f14b42bc8e 87: onsuccess: #567: 1: Success after binutils: 8 commits new b29820d989 88: onsuccess: #569: 1: Success after glibc: 10 commits new c9aa058884 89: onsuccess: #570: 1: Success after linux: 11 commits new 89a990c888 90: onsuccess: #572: 1: Success after binutils: 15 commits new 9ace9edfb9 91: onsuccess: #574: 1: Success after glibc: 3 commits new 67b3411f74 92: onsuccess: #575: 1: Success after linux: 34 commits new ec8560b518 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 794ce110cc 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 0bd84ae8df 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 7caddac2db 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new cf13680f49 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new a0044dc3a8 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new f15bd14bcd 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new daeacaf61d 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new bbb85b6fc3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 95f4697d33 102: onsuccess: #586: 1: Success after binutils: 5 commits new f4c720910c 103: onsuccess: #589: 1: Success after binutils: 3 commits new 3edd6bbe08 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 4dff8bfab8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 95dda72d2c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new b235e879ea 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new d1051c4e60 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 7509d760fb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 1c869d1e72 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new b138880517 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new a5783558fc 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 12380649a1 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 84e5d57460 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 16ab0aa98d 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 4bfc461344 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 0090eeb730 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 06481dc7ce 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 0e897ff86d 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 3abbffd3a6 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new e64fd547ed 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new e5286ad2cb 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new cea8df590a 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 5793e193ea 124: onsuccess: #612: 1: Success after binutils: 18 commits new e9246ccfd2 125: onsuccess: #614: 1: Success after linux: 12 commits new f12c194469 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new a2f11867ca 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new ab17f86b18 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 8021276627 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new e59670e86f 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 50e5ee540f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new a654bdb0ce 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new f64367b8ee 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new b956dcb8fa 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 40c83d4105 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new f1dff39100 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new ed95950054 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new a7377886f1 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 6fb7e86c66 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 7bbd6df282 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 55d08a4182 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new a268dc73f3 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 26ee42bbd4 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 188dfda93a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new e9432f579e 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 863f3d0d6e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 3e36eb9411 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 022c0a24b4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 2f8557f91b 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new f3fd4873c3 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 3a9dff103c 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new b3f287e2f9 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new cf0f208c4a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 44b03c006c 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 3180860a97 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 0843272a32 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new bacc0907d5 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 07f39b9463 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 353984ecc1 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 36e0993d6d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new d9797e64ea 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 63d7f69861 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new aaf6efe102 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 001eac1285 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...]
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 (4598fb8e9b) \ 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 1752 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52884 -> 52520 bytes 04-build_abe-gcc/console.log.xz | Bin 238728 -> 236744 bytes 06-build_abe-linux/console.log.xz | Bin 8344 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 236152 -> 235920 bytes 08-build_abe-gdb/console.log.xz | Bin 51048 -> 51556 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2088 -> 2188 bytes 11-check_regression/console.log.xz | Bin 15380 -> 8020 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 24 +- 11-check_regression/mail-body.txt | 151 +- 11-check_regression/results.compare | 75 +- 11-check_regression/results.compare2 | 4014 +------------------------------ 11-check_regression/results.regressions | 75 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 153 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 75 +- sumfiles/gdb.log.xz | Bin 1825092 -> 1797548 bytes sumfiles/gdb.sum | 130 +- 30 files changed, 463 insertions(+), 4328 deletions(-)