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-aarch64 in repository toolchain/ci/base-artifacts.

discards 2925cc44502 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards bdd9d1b4653 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 86ac13abf78 121: onsuccess: #908: 1: Success after glibc: 2 commits discards c15f784f60d 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 495dfb416ab 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards acf38cda127 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards b4fd463af65 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 3110ffbde9e 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 98a75f89fd0 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards e54d9da6648 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards b81f2aa138b 113: onsuccess: #898: 1: Success after linux: 3 commits discards 52975d14ea3 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 4095c9535c6 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards cc1ed472467 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards cc139638aba 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards d398ef07c6e 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 64e3713685b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 2cffe64a224 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 5b7ac4a5a94 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 6c422e05ce8 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 2fa44ad556d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards ed99e5312bc 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards e2cc3d1df72 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 6e2eb968741 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 905cde1738d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 36e207e5e95 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 530a11bc1c3 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards eea6e884c0d 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards cd3892f8b37 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 41da9223693 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards f4ff1d7e343 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards a7916d29927 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 8e2d5be2198 91: onsuccess: #870: 1: Success after binutils: 5 commits discards aaf4c481437 90: onsuccess: #867: 1: Success after binutils: 4 commits discards d18e9a13708 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 59974dd44aa 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 6da23d4dd4f 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards a992edac7c8 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 8674794025f 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 9e3c3dc101e 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 08169044641 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 908848c9773 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards dd98e64d7ef 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 96a6a6d6b89 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 17bcc64fea0 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 1141bdcdd88 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards b83ae86a7d6 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards bae025566e1 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards ce9f66cc127 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards c3178af5c6c 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards f23474536b0 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards da0bec8fd0e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 26c0511a961 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 130e1537726 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 770914260f1 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 0f69e5f51c1 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards afea4342f1e 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 3f24ad2454b 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 2c49d7201ca 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards ae2bcfab3e1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards e9cb70cfed1 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards d93633c5691 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 604be087ef5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 05cb069dda6 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards efef68f87a5 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 0455349bd00 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 93f23afe617 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 3f3df356ce0 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 5566f79d897 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 96b5bea14dc 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 46bada752f5 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 3075cd101ab 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 631165a23d6 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 25cb70ffc99 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 9f4a24a6cc4 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 7c80c27a8e6 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards f5009c18522 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards a73ef0fa6fb 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 91b5a15e53c 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 56ac08a7798 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards f9424d7c319 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 489d753602f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards ff55115b72f 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 11155118f6e 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards ce535b4ed96 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 5908ff09947 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 48470e42cdd 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 31c693f27c8 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 32512ab7e91 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 3ebdfac809a 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 533d87dda8b 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 91a4b388b00 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 79563cb8428 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 1ff863dac4e 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 8cef0dc403b 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 5f72b2772a4 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards f30839e7e6f 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards d3c4a83a607 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 078026c0cb4 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards e22825108d9 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 4eb73096d75 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new c1e5fd0b89a 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 4a29203d6c4 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 2ea393654d9 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new ff1c2ae4f5c 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new b47bb9f898b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new b7faddf104c 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new e4fbb4fb5d0 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 82221283d29 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 013b73b5360 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 5d0ba372fc6 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new ceebdfcb78a 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new ea53a3bec0a 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 55266a6a944 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 43a190fe542 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new e707c63d14e 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 4aaf0a1be5f 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 7de4b7bb19d 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new b1cb63cd1f3 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 121cc420f84 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 15e7171dcfc 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new f2f0a692b56 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new a4f80e5e7a0 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 9a468d1e7a5 45: onsuccess: #815: 1: Success after binutils: 6 commits new df8cf418480 46: onsuccess: #818: 1: Success after binutils: 10 commits new 4f5bf0a01fb 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 2972f9cfe9a 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new eaf79aa99da 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new c82fd1b2a61 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 5334bd0336a 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new a47fb55801b 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 912c87d1030 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 4863ab70252 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 55b60b86886 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new fbbe5f7fca6 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new ee39fdfd6ba 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new b2a357abc44 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new bb8b5e9b894 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 1a48fb3be11 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new b80c940e402 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new c11ba7103f2 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new e634ebcc1f7 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new bbc28993433 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 3d09c8060c4 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 85855007f50 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 0793ea4af42 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 4770f7e7270 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 9a862740337 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new b9ddd77fc6d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 1c4edab444d 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new f276cc36d24 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 8b9238e0a20 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 1ece9c7c755 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new ab0d07af309 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new d3efcb43594 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 1e81633f0da 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 2c5b48b87ef 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new b1951e2376f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new fa2aafbd646 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 0d41d9c2c19 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 193a6f1730f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new efd0a0de00c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 26a4494feed 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 5a499ba4add 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new bd2f7955163 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new f18250a6292 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 29300372779 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 490a8ea70be 89: onsuccess: #864: 1: Success after binutils: 25 commits new 968345a4e1c 90: onsuccess: #867: 1: Success after binutils: 4 commits new de0f1d00a24 91: onsuccess: #870: 1: Success after binutils: 5 commits new 950c85fe576 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new a42bfc5da1a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 34dcba89e46 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new d2326e3e18a 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new dcddcbf2acc 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new f515ee8856c 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new a252b475b9f 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 2d09c6b917b 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new e98fae5fdc7 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new da27d8bea2f 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new f251b72c3f9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 6d37df0d963 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new a6867763103 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 2f91aa65a6a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new c46dcc7bcaa 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 22e1fae8ce4 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 7b00199296a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new c046c63282a 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 78c4fa092cb 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 8a97f7297af 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 9d8f3f2eaca 112: onsuccess: #896: 1: Success after binutils: 24 commits new 02df89bc76a 113: onsuccess: #898: 1: Success after linux: 3 commits new adb5e6e775b 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 0b25e357bdd 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 7e01dee5b07 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new ee8cce80ef8 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new c895d243532 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 00560ba3bcd 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new d10f550274a 120: onsuccess: #906: 1: Success after binutils: 29 commits new 51bbc36a6f2 121: onsuccess: #908: 1: Success after glibc: 2 commits new 72e9b315398 122: onsuccess: #909: 1: Success after linux: 2753 commits new ac6dcec6660 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 43b1857a858 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...]

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 (2925cc44502) \ 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 1904 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40000 -> 39232 bytes 04-build_abe-gcc/console.log.xz | Bin 215580 -> 214008 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 10232 -> 9572 bytes 07-build_abe-glibc/console.log.xz | Bin 245808 -> 243312 bytes 08-build_abe-gdb/console.log.xz | Bin 39272 -> 39260 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2380 -> 2132 bytes 11-check_regression/console.log.xz | Bin 20328 -> 11964 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 102 +- 11-check_regression/mail-body.txt | 190 +- 11-check_regression/results.compare | 124 +- 11-check_regression/results.compare2 | 6400 +++++-------------------------- 11-check_regression/results.regressions | 132 +- 12-update_baseline/console.log | 46 +- 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 | 192 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 132 +- sumfiles/gdb.log.xz | Bin 1866856 -> 1949464 bytes sumfiles/gdb.sum | 5568 +++++++++++++++------------ 30 files changed, 4533 insertions(+), 8401 deletions(-)