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 001eac1285 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards aaf6efe102 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 63d7f69861 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards d9797e64ea 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 36e0993d6d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 353984ecc1 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 07f39b9463 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards bacc0907d5 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 0843272a32 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 3180860a97 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 44b03c006c 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards cf0f208c4a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards b3f287e2f9 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 3a9dff103c 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards f3fd4873c3 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 2f8557f91b 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 022c0a24b4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 3e36eb9411 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 863f3d0d6e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards e9432f579e 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 188dfda93a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 26ee42bbd4 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards a268dc73f3 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 55d08a4182 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 7bbd6df282 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 6fb7e86c66 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards a7377886f1 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards ed95950054 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards f1dff39100 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 40c83d4105 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards b956dcb8fa 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards f64367b8ee 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards a654bdb0ce 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 50e5ee540f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards e59670e86f 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8021276627 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards ab17f86b18 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards a2f11867ca 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards f12c194469 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards e9246ccfd2 125: onsuccess: #614: 1: Success after linux: 12 commits discards 5793e193ea 124: onsuccess: #612: 1: Success after binutils: 18 commits discards cea8df590a 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards e5286ad2cb 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards e64fd547ed 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 3abbffd3a6 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 0e897ff86d 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 06481dc7ce 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 0090eeb730 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 4bfc461344 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 16ab0aa98d 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 84e5d57460 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 12380649a1 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards a5783558fc 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards b138880517 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 1c869d1e72 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 7509d760fb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards d1051c4e60 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards b235e879ea 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 95dda72d2c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 4dff8bfab8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 3edd6bbe08 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards f4c720910c 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 95f4697d33 102: onsuccess: #586: 1: Success after binutils: 5 commits discards bbb85b6fc3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards daeacaf61d 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards f15bd14bcd 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards a0044dc3a8 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards cf13680f49 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 7caddac2db 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 0bd84ae8df 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 794ce110cc 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards ec8560b518 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 67b3411f74 92: onsuccess: #575: 1: Success after linux: 34 commits discards 9ace9edfb9 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 89a990c888 90: onsuccess: #572: 1: Success after binutils: 15 commits discards c9aa058884 89: onsuccess: #570: 1: Success after linux: 11 commits discards b29820d989 88: onsuccess: #569: 1: Success after glibc: 10 commits discards f14b42bc8e 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 126cb29c4a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f8949ab7e6 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 8fdefaaf77 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards cf85425442 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 62db076dae 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 4030097922 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 60462e6c2a 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 6fe44cf12d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards afe807d0c7 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 11312ec788 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 373aed3151 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards e9ecb2fe39 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 328cc67336 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards e9bb50516f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 96fe16be37 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 9250f8c99c 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards ae5b6fcd16 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 3e2b9c5c34 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards eef6a4f980 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 129cd36af2 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 56b81acc4b 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 78bd3ccd81 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 27ae63c048 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new ec7ea3680e 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new a7a99f2c06 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 3a542b369f 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new c164334e96 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7a01908fe7 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 25319b8307 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 3d8d049a4f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 19b3d1859a 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new e9afda2c75 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 9b422b110c 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 1d5a0b4e09 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new e488fb5137 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 12926a7fd3 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 805e92749d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 6aeedcbea5 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 1800be6507 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 0c9d47accf 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 72763aa430 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new dac991a51a 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 24de51630c 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 402e02e7f4 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 76c51e6768 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 0cd25dfe6d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 35168bee63 87: onsuccess: #567: 1: Success after binutils: 8 commits new 6cca8cb4a6 88: onsuccess: #569: 1: Success after glibc: 10 commits new caa59ea6e2 89: onsuccess: #570: 1: Success after linux: 11 commits new acb47d17a6 90: onsuccess: #572: 1: Success after binutils: 15 commits new bb057975ef 91: onsuccess: #574: 1: Success after glibc: 3 commits new 288980f034 92: onsuccess: #575: 1: Success after linux: 34 commits new b89dfc0885 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new cf83a4d7b0 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 21962abe8c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new b3e5755860 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 38367f4f9c 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new ee69446698 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 4686ebb3e3 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new c4e847cb5b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new ee997a1431 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new d57d2af18a 102: onsuccess: #586: 1: Success after binutils: 5 commits new a6b7bda777 103: onsuccess: #589: 1: Success after binutils: 3 commits new 9ec2572110 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new aea3f9c65b 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new fc9a60c4ef 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 7b380f914d 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new acfca53285 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 245ca37045 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new e051eedc07 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new dd535a907d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 72d8bfce61 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 4fe8039d3d 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 05e6138aa2 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 82436199fb 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 00a99b54ae 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 36bd668f42 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new d96133501a 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 9f25842e60 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 38fc5a92ce 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new ec73125011 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 542c8b1a22 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 65be05e0cd 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 5b62c85e00 124: onsuccess: #612: 1: Success after binutils: 18 commits new b549ab83ca 125: onsuccess: #614: 1: Success after linux: 12 commits new bf00ac4c37 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 3d99ee6d55 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new e5693e426a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 6ff7c02aef 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 5b836755fa 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 483547868d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 055af74fad 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 000f7bbe47 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 459ab2d9bc 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new d1828c1675 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 537adffd84 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new cc364318da 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new a24531487a 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new faf4c65ccf 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 116d7f2ccd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new f8cd98d1ae 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 118fe9fbaa 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new d178d64d72 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new a9f3f91b04 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 7f7c0818ac 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 46a95de768 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f555d1b414 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 7369f81a11 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 22dc6025db 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 7b224bdaf0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 3e01c8fa63 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 212feb2bb4 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 39fd7f59bf 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 2a733bf8fe 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 764df0185a 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new c9081ea2e8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 102edb92f0 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 53dda8b9f9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 709d1046ed 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 5734acf629 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 1642b573df 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 83deef39ae 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 6137b165d9 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new f90c105d66 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new c112aebfc6 165: onsuccess: #659: 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 (001eac1285) \ 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 1760 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52520 -> 52716 bytes 04-build_abe-gcc/console.log.xz | Bin 236744 -> 237940 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 8884 bytes 07-build_abe-glibc/console.log.xz | Bin 235920 -> 236384 bytes 08-build_abe-gdb/console.log.xz | Bin 51556 -> 51568 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2188 -> 2408 bytes 11-check_regression/console.log.xz | Bin 8020 -> 15916 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 31 +- 11-check_regression/mail-body.txt | 130 +- 11-check_regression/results.compare | 55 +- 11-check_regression/results.compare2 | 4022 ++++++++++++++++++++++++++++++- 11-check_regression/results.regressions | 55 +- 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 | 132 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 55 +- sumfiles/gdb.log.xz | Bin 1797548 -> 1716192 bytes sumfiles/gdb.sum | 3958 +----------------------------- 30 files changed, 4236 insertions(+), 4294 deletions(-)