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 94e3e7e2b3 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 1080614f98 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 5adacfd122 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 3add301e69 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards f87627a933 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 9dbcb44f5c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 9f00ad7a23 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards d2a18fe1df 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards ec54a7121d 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards eab259259e 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 54c869fd35 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 250605e0a1 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 6d00f7df24 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards ed74daae6b 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards cc16ee8dd2 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 638631261d 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 89c775af03 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards f72e0948d2 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 7a478d4d23 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 6af0dcf774 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 04bc8430d6 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 9166365068 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 66a1d9b54d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 2f8b9c2270 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 0e681f5416 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards cb66ebc4df 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 3fd874b28f 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 0fe2568ca8 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 9db4cfa1af 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards aac7a077c7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 4f795b8463 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 714ba5caa9 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 0e94e3efe5 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 3617b16b53 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 44650a13a4 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 21e3fb1029 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards ff60140d5f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards c28bc154d7 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 58d87dfc57 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 09c6a298e3 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 2c2b03458d 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 957a99c349 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 36b7050b5b 125: onsuccess: #614: 1: Success after linux: 12 commits discards 30f136a116 124: onsuccess: #612: 1: Success after binutils: 18 commits discards ca594b6bb1 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 0b2d4bc81e 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 8da8d98383 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards b3e9cca347 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 29c2e0f40a 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards d5343def6f 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards da501cf72b 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards fcdb3f90de 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards b0c50bdd1e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards ae1801e837 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 7ccab5d7fd 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 76b9deb04f 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 785517e81f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 0788d5065b 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards cca54294d7 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards eec914c191 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards ef67db2c52 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards c79af2ef69 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards ff1922de2d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards f603e330d6 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 2c5bc430c3 103: onsuccess: #589: 1: Success after binutils: 3 commits discards de91c9331c 102: onsuccess: #586: 1: Success after binutils: 5 commits discards c19efe862e 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards a15f1ea0c7 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards b1f79ba155 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 817c6feb8f 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 36bee5b396 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 9a0cd182d4 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 5e09ea96fe 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards d5424af32a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards f16aa4eb32 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 5fc4fcfbea 92: onsuccess: #575: 1: Success after linux: 34 commits discards e4c871e274 91: onsuccess: #574: 1: Success after glibc: 3 commits discards b20fb0f8a4 90: onsuccess: #572: 1: Success after binutils: 15 commits discards fcb2c90a22 89: onsuccess: #570: 1: Success after linux: 11 commits discards 0881dc8a0e 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 3a77a6eb7c 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 20467d4ebe 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 78ea13ef1a 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 32079a8cab 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards a6b335dd1c 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 7a164365de 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards cf00956a84 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 451f69c65b 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 66c18172d3 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards c14dc745d6 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards dfa46dc159 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards e389f70868 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards e9bd45dd70 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards baa3503036 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 1b96752f23 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 2d59db2e76 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards f674a80064 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 78ae579a14 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards e0930434e9 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 6352c20de1 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 3622fea97d 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new f4ac4ade22 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new d09de136ac 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 997d9081a6 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new c43975f044 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 3565ca9088 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 6d8433e872 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 91d4db77c9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 2b3fb6e58d 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new c65999019c 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new ba04fbbf82 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 1cfd567e01 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new c2ce463e89 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 3df7bcb369 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new acbc9b633e 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 7c12c7a7a3 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 773a7203e7 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new e564ea0c01 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new cfcb1b5101 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 2c4e9d04f1 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 9f725a70ee 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new e99766f43f 87: onsuccess: #567: 1: Success after binutils: 8 commits new f0d453f5be 88: onsuccess: #569: 1: Success after glibc: 10 commits new 59ef6317e4 89: onsuccess: #570: 1: Success after linux: 11 commits new 9e2ccba190 90: onsuccess: #572: 1: Success after binutils: 15 commits new 4472f72ea9 91: onsuccess: #574: 1: Success after glibc: 3 commits new c8f2e52fe5 92: onsuccess: #575: 1: Success after linux: 34 commits new f1b487bbe9 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 46b68c7779 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 6c56cccf94 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new c0bcf84aa4 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 1ae1c69bb8 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 8ff9b09405 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new b779df2f36 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new f47082405d 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new e389da1b79 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 591f436712 102: onsuccess: #586: 1: Success after binutils: 5 commits new 5fe3a273f0 103: onsuccess: #589: 1: Success after binutils: 3 commits new e579e67699 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 3e0c070b59 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new c14b74c9d3 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 1ddf1fc14e 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 8662e5f2de 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new e197fa2591 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 519844c668 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new f36487ad9f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 36e57f603e 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new f8a0bc54a0 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 2b4a45596a 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 1fbf57d50a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new d16c81a3e3 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new a51a85cb48 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 89aa156a27 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 0c36a93da8 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new d171018ffb 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new c354c07150 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 2c13f81f6c 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 032afdcfc7 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new f8e42fa054 124: onsuccess: #612: 1: Success after binutils: 18 commits new 0f12d268c9 125: onsuccess: #614: 1: Success after linux: 12 commits new 1a82363a55 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new fd36534531 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new ad73dd5814 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 6f98214558 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 5706ad3662 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 0c2df9d8be 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new df149e01cd 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 6958f1a21f 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new f7445f02fb 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 624840fc43 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 3f76f78bc2 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 00efbc10b1 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 53b4fa2f75 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 4e69f9c6a6 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new a8adbc00c5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new ac16d4074d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 93112f2aca 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new a3ddbd8a87 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 6145b87eaa 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new eb07fcb1c0 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 5e197ca726 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 729bfccb4f 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 7b7f4c9f7e 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new c5a839d6d2 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 60adedfe0b 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 90c578e988 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 840f752e8c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new e2f58a1fde 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new a803fe896c 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new cf9bf9a34f 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new d88ec85355 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new ed9e56edc7 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 492557b067 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 0561c30a69 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new ac84b29330 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 9447b6a8c9 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new e86741f247 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 1c40a9091a 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 0d1426dd69 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new dd36003b09 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 1e468c2a71 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new f4ebc589ee 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 051efbed0a 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...]

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 (94e3e7e2b3) \ 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 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 51796 -> 51756 bytes 04-build_abe-gcc/console.log.xz | Bin 237052 -> 236536 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8632 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 236192 -> 236264 bytes 08-build_abe-gdb/console.log.xz | Bin 51080 -> 50480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2132 -> 2140 bytes 11-check_regression/console.log.xz | Bin 19420 -> 15204 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 50 +- 11-check_regression/mail-body.txt | 200 +- 11-check_regression/results.compare | 87 +- 11-check_regression/results.compare2 | 1455 +---- 11-check_regression/results.regressions | 82 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 202 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 82 +- sumfiles/gdb.log.xz | Bin 1732124 -> 1854676 bytes sumfiles/gdb.sum | 9261 ++++++++++++++++++++++--------- 30 files changed, 7233 insertions(+), 4272 deletions(-)