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 b4db6ef172c 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 44a3d78503a 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 1f23af32156 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 8f6b0eae5ed 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards f2f74bbbbbd 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 7a93a85cf4a 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 1754cbc45b5 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards c7f29f2e7fc 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards ebf5e903bc6 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards de2d5018402 113: onsuccess: #898: 1: Success after linux: 3 commits discards fdc3616ebb4 112: onsuccess: #896: 1: Success after binutils: 24 commits discards c6682bb83d0 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards f1207b3640f 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 83c649ac50c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards ccbb58e2659 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards a43c6db7e74 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 6edf5fc0b30 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 04edcda9646 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 3e7d21c1ec5 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 23458dd6a1f 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards df0f1cf143f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 3adb3bacab0 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 01c76d6444a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 7c376090559 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 5970e712bd7 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards b7266caeea8 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards bfb935c0704 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards f7c265b111b 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards fd5543767bf 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 7880959bb64 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 24f9968fba4 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 1c69e817bf0 91: onsuccess: #870: 1: Success after binutils: 5 commits discards f35e80b7ddd 90: onsuccess: #867: 1: Success after binutils: 4 commits discards fb6a5cca091 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 3d4c7a483f8 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 4b182094900 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 73f8df6df60 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 73d46c078bd 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 74441ab6bec 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards fd320b420ed 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 3be95eb7035 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 2059f510e1c 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 3691154d2e0 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards fa6db29df3f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 9db24e7741a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards c9fba1980ab 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards b8d92aa6136 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 8392ab9bced 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 35857718450 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 39426617120 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards e0d2a994785 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards c16239c115a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 6ade667d860 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 6f9c68172e2 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards ef6e99e8720 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 332e162e886 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 07d5ca83caa 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 3adca640f40 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 52f85dbbee0 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 72ab51f73fe 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 49c8bab2591 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 22cdc92d568 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 5afde210a32 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards acc332c2480 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards f02bc30540d 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 62a89001e7f 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 703a455d8f0 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards e5ad7a046e4 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards ced550a3e6e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 740b6ae86d7 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 467ca3efab8 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards a963805df66 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 5242fc7dc49 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards b8ebbb7e940 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards fdd8eab1bc7 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards aa5473073ad 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 1cdee43c7a5 46: onsuccess: #818: 1: Success after binutils: 10 commits discards aea62e9ff13 45: onsuccess: #815: 1: Success after binutils: 6 commits discards f5eddae75c6 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards f6367b351ea 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 6fcfefd4d1f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 6df8bc54b87 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 12537bedd7b 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 04aa20cee7d 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 832db14453d 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 719dff9c87a 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards b51e9bf785f 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards cb86af264c6 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards fae629941d6 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 198f538161c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 28203277767 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards cf450d5466d 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards c5b2d4f4868 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 2177f645755 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 9fbaae72a74 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards fd374b5fd9f 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards e589a2e7ce8 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards c127bfb5376 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 1de0d2c7efd 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 03ffdbf9ac7 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards f87daa07b40 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 7855e660b55 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 4eb73096d75 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new e22825108d9 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 078026c0cb4 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new d3c4a83a607 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new f30839e7e6f 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 5f72b2772a4 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 8cef0dc403b 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 1ff863dac4e 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 79563cb8428 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 91a4b388b00 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 533d87dda8b 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 3ebdfac809a 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 32512ab7e91 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 31c693f27c8 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 48470e42cdd 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 5908ff09947 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new ce535b4ed96 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 11155118f6e 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new ff55115b72f 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 489d753602f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new f9424d7c319 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 56ac08a7798 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 91b5a15e53c 45: onsuccess: #815: 1: Success after binutils: 6 commits new a73ef0fa6fb 46: onsuccess: #818: 1: Success after binutils: 10 commits new f5009c18522 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 7c80c27a8e6 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 9f4a24a6cc4 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 25cb70ffc99 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 631165a23d6 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 3075cd101ab 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 46bada752f5 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 96b5bea14dc 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 5566f79d897 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 3f3df356ce0 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 93f23afe617 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 0455349bd00 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new efef68f87a5 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 05cb069dda6 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 604be087ef5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new d93633c5691 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new e9cb70cfed1 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new ae2bcfab3e1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 2c49d7201ca 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 3f24ad2454b 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new afea4342f1e 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 0f69e5f51c1 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 770914260f1 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 130e1537726 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 26c0511a961 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new da0bec8fd0e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new f23474536b0 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new c3178af5c6c 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new ce9f66cc127 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new bae025566e1 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new b83ae86a7d6 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 1141bdcdd88 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 17bcc64fea0 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 96a6a6d6b89 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new dd98e64d7ef 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 908848c9773 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 08169044641 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 9e3c3dc101e 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 8674794025f 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new a992edac7c8 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 6da23d4dd4f 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 59974dd44aa 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new d18e9a13708 89: onsuccess: #864: 1: Success after binutils: 25 commits new aaf4c481437 90: onsuccess: #867: 1: Success after binutils: 4 commits new 8e2d5be2198 91: onsuccess: #870: 1: Success after binutils: 5 commits new a7916d29927 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new f4ff1d7e343 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 41da9223693 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new cd3892f8b37 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new eea6e884c0d 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 530a11bc1c3 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 36e207e5e95 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 905cde1738d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 6e2eb968741 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new e2cc3d1df72 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new ed99e5312bc 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 2fa44ad556d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 6c422e05ce8 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 5b7ac4a5a94 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 2cffe64a224 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 64e3713685b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new d398ef07c6e 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new cc139638aba 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new cc1ed472467 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 4095c9535c6 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 52975d14ea3 112: onsuccess: #896: 1: Success after binutils: 24 commits new b81f2aa138b 113: onsuccess: #898: 1: Success after linux: 3 commits new e54d9da6648 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 98a75f89fd0 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 3110ffbde9e 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new b4fd463af65 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new acf38cda127 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 495dfb416ab 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new c15f784f60d 120: onsuccess: #906: 1: Success after binutils: 29 commits new 86ac13abf78 121: onsuccess: #908: 1: Success after glibc: 2 commits new bdd9d1b4653 122: onsuccess: #909: 1: Success after linux: 2753 commits new 2925cc44502 123: onsuccess: #910: 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 (b4db6ef172c) \ 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 1792 -> 1904 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 40556 -> 40000 bytes 04-build_abe-gcc/console.log.xz | Bin 217328 -> 215580 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9804 -> 10232 bytes 07-build_abe-glibc/console.log.xz | Bin 245772 -> 245808 bytes 08-build_abe-gdb/console.log.xz | Bin 39520 -> 39272 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2136 -> 2380 bytes 11-check_regression/console.log.xz | Bin 20152 -> 20328 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 70 +- 11-check_regression/mail-body.txt | 155 +- 11-check_regression/results.compare | 97 +- 11-check_regression/results.compare2 | 1526 +---- 11-check_regression/results.regressions | 98 +- 12-update_baseline/console.log | 42 +- 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 | 157 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 98 +- sumfiles/gdb.log.xz | Bin 1930420 -> 1866856 bytes sumfiles/gdb.sum | 9959 ++++++++++++++++++++++++------- 31 files changed, 8481 insertions(+), 3773 deletions(-)