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 43b1857a858 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards ac6dcec6660 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 72e9b315398 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 51bbc36a6f2 121: onsuccess: #908: 1: Success after glibc: 2 commits discards d10f550274a 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 00560ba3bcd 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards c895d243532 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards ee8cce80ef8 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 7e01dee5b07 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 0b25e357bdd 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards adb5e6e775b 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 02df89bc76a 113: onsuccess: #898: 1: Success after linux: 3 commits discards 9d8f3f2eaca 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 8a97f7297af 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 78c4fa092cb 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards c046c63282a 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 7b00199296a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 22e1fae8ce4 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards c46dcc7bcaa 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 2f91aa65a6a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards a6867763103 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 6d37df0d963 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards f251b72c3f9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards da27d8bea2f 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards e98fae5fdc7 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 2d09c6b917b 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards a252b475b9f 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards f515ee8856c 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards dcddcbf2acc 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards d2326e3e18a 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 34dcba89e46 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards a42bfc5da1a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 950c85fe576 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards de0f1d00a24 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 968345a4e1c 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 490a8ea70be 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 29300372779 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards f18250a6292 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards bd2f7955163 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 5a499ba4add 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 26a4494feed 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards efd0a0de00c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 193a6f1730f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 0d41d9c2c19 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards fa2aafbd646 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards b1951e2376f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 2c5b48b87ef 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 1e81633f0da 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards d3efcb43594 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards ab0d07af309 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 1ece9c7c755 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 8b9238e0a20 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards f276cc36d24 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 1c4edab444d 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards b9ddd77fc6d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 9a862740337 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 4770f7e7270 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 0793ea4af42 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 85855007f50 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 3d09c8060c4 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards bbc28993433 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards e634ebcc1f7 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards c11ba7103f2 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards b80c940e402 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 1a48fb3be11 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards bb8b5e9b894 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards b2a357abc44 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards ee39fdfd6ba 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards fbbe5f7fca6 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 55b60b86886 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 4863ab70252 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 912c87d1030 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards a47fb55801b 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 5334bd0336a 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards c82fd1b2a61 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards eaf79aa99da 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 2972f9cfe9a 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 4f5bf0a01fb 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards df8cf418480 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 9a468d1e7a5 45: onsuccess: #815: 1: Success after binutils: 6 commits discards a4f80e5e7a0 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards f2f0a692b56 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 15e7171dcfc 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 121cc420f84 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards b1cb63cd1f3 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 7de4b7bb19d 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 4aaf0a1be5f 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards e707c63d14e 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 43a190fe542 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 55266a6a944 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards ea53a3bec0a 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards ceebdfcb78a 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 5d0ba372fc6 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 013b73b5360 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 82221283d29 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards e4fbb4fb5d0 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards b7faddf104c 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards b47bb9f898b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards ff1c2ae4f5c 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 2ea393654d9 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 4a29203d6c4 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new b9f9b93f17c 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 6a278457467 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 067e5f8e548 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 69934afb53e 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 33d5565cd80 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 23c5cafeb11 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new a6b51b7f077 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 9c0c8d820c1 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 810842ecd3d 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 60a88deb24c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new d8a62b30d09 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new f32d9d783cc 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new ace734ad179 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new b69ebc65a59 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new b7814a0a3aa 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 4c1596d6376 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 21d7f90aada 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new c5e2d210b4d 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new ec32c650d12 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 5b4a7953fa1 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 3d051436f60 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 01d7abf5cf6 45: onsuccess: #815: 1: Success after binutils: 6 commits new addf2952761 46: onsuccess: #818: 1: Success after binutils: 10 commits new 90fe930d80d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new f655ce44793 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new e78e58c8fb0 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 6b73751b11d 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 132f483db33 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new cf2ca79efb8 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 6b40e863373 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 200c7108410 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 5febc8e9357 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new e77fe3f762f 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 0bc4ca229d5 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new c1d6563167b 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 49fc6ef2b52 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new db3fe0ab610 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new ee0699d2464 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 457a5b88cc1 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new cf9769d1f8b 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 24270aa1d84 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 982c713b4d0 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 44f8dd6eeb6 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 251f51ba6aa 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 1330611b8b3 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new a38f9b69d0c 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 3d0b11c20a8 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 4d3d2093ed3 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new ef3b11a883e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new ec843574eed 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new eea50855d65 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 832dcbe4952 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new a6d29d4cea3 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 3ffdddc3b88 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 35705ef605c 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new dc138739a43 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new d7345247453 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 0472ccbf56e 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 06b20983365 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 9325aec5e5d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 7a4477983b7 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new f95da051275 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new a7067f7f947 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 4aeec750402 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new c27885171f6 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new c0586c079d2 89: onsuccess: #864: 1: Success after binutils: 25 commits new 1c90813c015 90: onsuccess: #867: 1: Success after binutils: 4 commits new 0d0c120b4b5 91: onsuccess: #870: 1: Success after binutils: 5 commits new b2ef61fb8af 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 2fc1f1fe178 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new c240b740047 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 91736ff5162 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new df60167d4e2 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 20a444a4150 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new b568b215fe7 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 6523144b5db 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new e6e23823eb6 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 2af31cbcd75 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 0aaa2fb0ca7 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 90b050f56bf 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 4e4cfde8f73 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new c8bea7ef1e2 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 0c169e296bd 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 3247ead8385 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new cdafa889b75 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new f9ef6a4acf2 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new fd99de50989 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new e1c707278a4 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 334901cfc19 112: onsuccess: #896: 1: Success after binutils: 24 commits new 56a84387bab 113: onsuccess: #898: 1: Success after linux: 3 commits new 27538fda93a 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 4941efed4f0 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new b17f92b379c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 27844d31028 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new a6d5feddd72 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new ed472112dff 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 11f7040357e 120: onsuccess: #906: 1: Success after binutils: 29 commits new 698294b6805 121: onsuccess: #908: 1: Success after glibc: 2 commits new e86ca96f02a 122: onsuccess: #909: 1: Success after linux: 2753 commits new 0bf1a5c045f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new cb4884bc04b 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new c74710368a4 125: onsuccess: #912: 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 (43b1857a858) \ 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 1744 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39232 -> 40456 bytes 04-build_abe-gcc/console.log.xz | Bin 214008 -> 214604 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9572 -> 8796 bytes 07-build_abe-glibc/console.log.xz | Bin 243312 -> 246188 bytes 08-build_abe-gdb/console.log.xz | Bin 39260 -> 39104 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2132 -> 2156 bytes 11-check_regression/console.log.xz | Bin 11964 -> 11936 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 72 +- 11-check_regression/mail-body.txt | 217 +- 11-check_regression/results.compare | 128 +- 11-check_regression/results.compare2 | 2130 +++++++--- 11-check_regression/results.regressions | 87 +- 12-update_baseline/console.log | 46 +- 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 | 219 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 87 +- sumfiles/gdb.log.xz | Bin 1949464 -> 1966144 bytes sumfiles/gdb.sum | 6427 ++++++++++++------------------- 31 files changed, 4285 insertions(+), 5182 deletions(-)