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 c74710368a40 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] discards cb4884bc04b8 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] discards 0bf1a5c045f2 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] discards e86ca96f02af 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 698294b68058 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 11f7040357ee 120: onsuccess: #906: 1: Success after binutils: 29 commits discards ed472112dffe 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] discards a6d5feddd72b 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] discards 27844d310286 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] discards b17f92b379cc 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] discards 4941efed4f01 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] discards 27538fda93a0 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] discards 56a84387bab3 113: onsuccess: #898: 1: Success after linux: 3 commits discards 334901cfc197 112: onsuccess: #896: 1: Success after binutils: 24 commits discards e1c707278a4e 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards fd99de509890 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] discards f9ef6a4acf2b 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] discards cdafa889b75c 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] discards 3247ead83857 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] discards 0c169e296bd1 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] discards c8bea7ef1e28 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] discards 4e4cfde8f73f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] discards 90b050f56bfc 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] discards 0aaa2fb0ca77 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] discards 2af31cbcd759 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards e6e23823eb61 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 6523144b5db7 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] discards b568b215fe7a 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] discards 20a444a41508 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] discards df60167d4e26 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] discards 91736ff51626 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] discards c240b740047f 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] discards 2fc1f1fe1784 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] discards b2ef61fb8af3 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] discards 0d0c120b4b5a 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 1c90813c0155 90: onsuccess: #867: 1: Success after binutils: 4 commits discards c0586c079d2d 89: onsuccess: #864: 1: Success after binutils: 25 commits discards c27885171f67 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] discards 4aeec7504027 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] discards a7067f7f9478 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] discards f95da0512754 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 7a4477983b7d 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 9325aec5e5db 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 06b20983365a 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 0472ccbf56ee 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards d73452474539 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards dc138739a438 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 35705ef605c0 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 3ffdddc3b88e 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] discards a6d29d4cea31 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] discards 832dcbe4952e 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] discards eea50855d653 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] discards ec843574eed6 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards ef3b11a883e1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 4d3d2093ed38 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] discards 3d0b11c20a80 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] discards a38f9b69d0c9 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 1330611b8b34 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 251f51ba6aab 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 44f8dd6eeb64 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] discards 982c713b4d0b 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards 24270aa1d841 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards cf9769d1f8b8 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 457a5b88cc1b 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] discards ee0699d24649 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] discards db3fe0ab6102 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] discards 49fc6ef2b526 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] discards c1d6563167b4 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] discards 0bc4ca229d54 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] discards e77fe3f762f1 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 5febc8e93574 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards 200c7108410e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 6b40e8633736 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards cf2ca79efb8e 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards 132f483db33d 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 6b73751b11d9 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards e78e58c8fb0a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards f655ce44793d 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 90fe930d80de 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards addf29527612 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 01d7abf5cf66 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 3d051436f601 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards 5b4a7953fa19 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards ec32c650d12a 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards c5e2d210b4d7 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 21d7f90aadab 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] discards 4c1596d63768 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards b7814a0a3aa7 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] discards b69ebc65a598 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards ace734ad1797 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] discards f32d9d783ccb 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards d8a62b30d097 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] discards 60a88deb24c9 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards 810842ecd3db 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 9c0c8d820c10 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards a6b51b7f0774 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards 23c5cafeb114 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] discards 33d5565cd808 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards 69934afb53ef 27: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] discards 067e5f8e548c 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/g [...] discards 6a2784574675 25: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] new dba3f9ad20ee 25: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] new a97b5e194d57 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/g [...] new d1fa9df0392a 27: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new 4d29bf895f16 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new 1053761aa93e 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] new b752bfcbc82b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 23ccc7b837fa 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 581f326197e0 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new 5a2f712b9e89 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new af9898a58810 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] new 601d191fdd29 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 03ad31833b5a 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] new c6d7c4d992f7 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new 7582b6e3c007 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] new 5ec7abf5a944 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 53612fd6360f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] new 3dc51bf61630 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new 5a8cba946ed0 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new a599feef2f51 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new 63d21d1964f8 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 76a7188d0900 45: onsuccess: #815: 1: Success after binutils: 6 commits new 6806473b34f4 46: onsuccess: #818: 1: Success after binutils: 10 commits new 1a3428979398 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new 50eee8e35f91 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new 3f53f0e696bb 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new 07cfa39d72d5 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new b0cce3c70df0 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new 8e35730c2909 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new 31b3a05afc49 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new cc3fc04c8b26 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 5a4cd4862f83 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new f201e2c6126b 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new 3cae9df2b72c 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] new 0b27ac5d7429 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] new 6f64c2722856 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] new b74df565d598 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] new 62d4756705af 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] new 8b064209e1b3 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] new 033e98ef2d07 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new 53838658f0bc 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new d6f2fba93e24 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new 7922048a2f2b 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] new 48f15457bd31 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 1dc1bc153309 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 3abf142d525e 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 51d6ec4f18e5 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] new 7c3f2c59cb82 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] new d223a0903470 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new f0674c05338c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 61835cd9eb25 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] new d778303db0dc 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] new b4673e2094b5 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] new 39e8e037a7a0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] new 6d9a469e24e7 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new c7e8faa9a414 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 94c2c8d450eb 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new e5edb58eb206 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new bc5b0249597a 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new ad4703ae1364 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new f4222086b379 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 3ab348576810 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 6593f825ced8 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] new e6f6ccd94d0b 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] new bf0d077ce402 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] new 5e9acb34d7fc 89: onsuccess: #864: 1: Success after binutils: 25 commits new 0d84d4e93792 90: onsuccess: #867: 1: Success after binutils: 4 commits new e68c28b69729 91: onsuccess: #870: 1: Success after binutils: 5 commits new 4c15fcfc823e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] new a284503b832e 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] new 140582297719 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] new d0c18ab2f110 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] new e20bf0a38d22 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] new a6468fc1ee14 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] new a0ce84c0c119 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] new 01e621d74442 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] new 4b422503bf3d 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new f5cbf2c978cb 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new dfc9ca9898fb 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] new e1066c5c5530 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] new 83a1384cc977 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] new 439e802c426d 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] new c0b6c98a00d8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] new 29c3be77657e 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] new 8e874de2792f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] new 03dafac3c984 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] new 3791e5b0142d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] new 94a5300d34c8 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new b5a14eedac9e 112: onsuccess: #896: 1: Success after binutils: 24 commits new 5755852cb93b 113: onsuccess: #898: 1: Success after linux: 3 commits new 35d535ea83a9 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] new 3d6216579997 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] new 3da7b16c4bda 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] new d485b864eafe 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] new d72f3852b099 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] new aab9b357c1b5 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] new ee9419efb46b 120: onsuccess: #906: 1: Success after binutils: 29 commits new 7354860dccaa 121: onsuccess: #908: 1: Success after glibc: 2 commits new ea9310dcd637 122: onsuccess: #909: 1: Success after linux: 2753 commits new 2d9bc2dc86cd 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] new 6248e4eceb41 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] new b69dddf87289 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] new 1a010c8199c1 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...]

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 (c74710368a40) \ 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 1748 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40456 -> 39576 bytes 04-build_abe-gcc/console.log.xz | Bin 214604 -> 215940 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8796 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 246188 -> 243068 bytes 08-build_abe-gdb/console.log.xz | Bin 39104 -> 38752 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2156 -> 2132 bytes 11-check_regression/console.log.xz | Bin 11936 -> 13508 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 55 +- 11-check_regression/mail-body.txt | 195 +- 11-check_regression/results.compare | 108 +- 11-check_regression/results.compare2 | 4737 +++++++++++--------- 11-check_regression/results.regressions | 108 +- 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 | 197 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 108 +- sumfiles/gdb.log.xz | Bin 1966144 -> 1862716 bytes sumfiles/gdb.sum | 7226 ++++++++++--------------------- 30 files changed, 5636 insertions(+), 7192 deletions(-)