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 5deb2cc768 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards a450e3b144 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards a0e5c8fccd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 2728b20bfe 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards a837068782 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards c9249648f5 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards f39b439be7 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 68c3c9bb93 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 0a213f0ef4 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 702fa5536f 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards e14a3efefc 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards eb22b0d838 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards c4fdd15c32 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards f636ba562b 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards e98380b989 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 990f216a89 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards e0d6135812 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 751731ded0 125: onsuccess: #614: 1: Success after linux: 12 commits discards 50ae00315d 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 43934b36ca 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 1f97d3dfd4 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 6ea93c5617 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 4e5f91cf0c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards a9402546b8 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards cae230f90f 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 48441f6205 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards b7eaff97b1 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards c8237f8611 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 763c84c19a 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards afd366ab6a 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 6f3630c636 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards c90b19867f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards a549f7804a 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 45fdd9336f 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 075b0983fa 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards feaae6aa43 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards c9f5dadfeb 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards deb6a305bd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards c052cd62c4 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 1fece58186 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 80ddd9a17a 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 9c04c0d64b 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards a0bbf54835 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards c8a01b5af4 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 2a5319ddc4 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 8f798e394b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards e386db9f10 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards a33c7cb5a1 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards cb85ae6cda 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards a8e482c73a 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards da0be430f4 92: onsuccess: #575: 1: Success after linux: 34 commits discards 263a16fdd8 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 27ad8423b5 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 3eb13ba3f5 89: onsuccess: #570: 1: Success after linux: 11 commits discards 44793017e8 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 60f88acfbe 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 1359c8733f 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards eec8aec7a0 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 88a10332bc 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 9679c165da 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards a870af3040 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards ffa0105960 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 159ca5af87 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 5289c69b9b 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards d0ce457120 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards b83e4c7ba8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 1947b4e61f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards e05fd8a140 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 8e4e014c8c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 130caefeda 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 7c8bf56159 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards c55e8b4290 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 85c97762f4 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 1483373987 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 6d45adab86 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 79a2118acb 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards dec7003fe4 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 389a1f0ce4 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 8d34c2d4f0 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards dab7bbd2da 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 38ad9a79d7 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 63020d9579 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 8a675febb5 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards ecdce3dca6 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 48f7221a3d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards a9e4408ffd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 78640bf7cd 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 60ef2f739b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards fa31c1107f 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards f59fca0363 53: onsuccess: #531: 1: Success after binutils: 12 commits discards b5708906dd 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 42be672e6a 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 2c38f98fd7 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 74b6bb89b7 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 53e338a1d9 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 0b3bf1ca1a 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 8b8cc76bc7 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 4a47320064 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards a4d29e4fbc 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 69313cc12e 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 4f96794414 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 46fdcba379 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 23b498248e 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new cdc23907c1 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new c06606bfb2 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 9f3d5ebf9e 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new ebd9927c1d 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 952ab76a77 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 4424c3de72 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 5fbcfd4fe0 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 398f0f985a 51: onsuccess: #525: 1: Success after binutils: 8 commits new f4aba34dac 52: onsuccess: #528: 1: Success after binutils: 8 commits new 1ab1769896 53: onsuccess: #531: 1: Success after binutils: 12 commits new fd08c8848b 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 95d0f80520 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new f943b5c118 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 785ee0779b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 22274ff25c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 75bbc4e2a7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new a2c7c406e6 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new fff1c1d000 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 9bebad5a91 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 0b216ebd84 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 66f80319fa 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new df1598d38b 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 18b5d12166 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new aeefdd53db 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new bd8769c1f1 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 8c65556a85 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 10b8243b67 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 97d93301c0 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new e0b2ac0e29 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new fd50e5945b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new f713b5371c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 795e85ea32 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 30d1178920 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 2ed87d6144 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new aa5ad4e0fc 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 0b0df2dd12 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new b0e33ff894 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 6c0a3064ae 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 5b608a2269 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 3a2f4d4bd4 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 801eb3106b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new e26ac9080d 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 1fcec8e630 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 4500f7c8f6 87: onsuccess: #567: 1: Success after binutils: 8 commits new 3e7d53b849 88: onsuccess: #569: 1: Success after glibc: 10 commits new 4002c6518a 89: onsuccess: #570: 1: Success after linux: 11 commits new 49ba7c115c 90: onsuccess: #572: 1: Success after binutils: 15 commits new b60f13254a 91: onsuccess: #574: 1: Success after glibc: 3 commits new cdefe266f8 92: onsuccess: #575: 1: Success after linux: 34 commits new d51768c61b 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 9f8b9ffb77 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 9cb45e1ca1 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 455e43720f 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new d0e2c97f73 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new e2d46917e9 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 0b3c922f40 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new fe26c94663 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 1a27f5c4f8 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new b8204cc686 102: onsuccess: #586: 1: Success after binutils: 5 commits new e8d47ea9fe 103: onsuccess: #589: 1: Success after binutils: 3 commits new 1fad9c6f13 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 3d12d101e8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 50b7b8c329 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 4d7bdbdb69 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 48e7aa9c3e 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 7090c7c310 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 7ca0da4eb7 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new ef6846ae3c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new b9e37fc8e6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 217f16700c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 124be2f86c 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new d34ee6b171 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new a6de659c46 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new a7e0863217 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 3dc1fec06e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new d0d31a13c3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 0b3cb4aa2c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 02209a60e2 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 43c43b1119 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 1f24c0d766 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 9028a56659 124: onsuccess: #612: 1: Success after binutils: 18 commits new eaa825d194 125: onsuccess: #614: 1: Success after linux: 12 commits new 6b2bbdd8a3 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new b650f0cff6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new a68b025f0a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 3502fa7d24 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 06b7edaad4 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new dbeb014f56 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new dabe18e4f0 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new acb57a7234 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 8b19aad341 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new ae2fb5a32f 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 08919da6c4 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new e6fc57e58a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new f3bce4460e 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 8b60beb8fb 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new f4e6437742 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 30bc7b84d5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new f72bc9eb1a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 2eeb88938f 143: onsuccess: #635: 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 (5deb2cc768) \ 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 1728 -> 1916 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 53256 -> 53708 bytes 04-build_abe-gcc/console.log.xz | Bin 240668 -> 237980 bytes 06-build_abe-linux/console.log.xz | Bin 8808 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 239560 -> 238580 bytes 08-build_abe-gdb/console.log.xz | Bin 52188 -> 53128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3888 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2428 -> 2644 bytes 11-check_regression/console.log.xz | Bin 9160 -> 17400 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 45 +- 11-check_regression/mail-body.txt | 209 +- 11-check_regression/results.compare | 124 +- 11-check_regression/results.compare2 | 4505 +++++++++++++++++++++++++++++-- 11-check_regression/results.regressions | 118 +- 12-update_baseline/console.log | 50 +- 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 | 211 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 118 +- sumfiles/gdb.log.xz | Bin 1809512 -> 1719388 bytes sumfiles/gdb.sum | 4382 ++---------------------------- 29 files changed, 4959 insertions(+), 4851 deletions(-)