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 1a010c8199c1 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] discards b69dddf87289 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] discards 6248e4eceb41 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] discards 2d9bc2dc86cd 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] discards ea9310dcd637 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 7354860dccaa 121: onsuccess: #908: 1: Success after glibc: 2 commits discards ee9419efb46b 120: onsuccess: #906: 1: Success after binutils: 29 commits discards aab9b357c1b5 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] discards d72f3852b099 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] discards d485b864eafe 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] discards 3da7b16c4bda 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] discards 3d6216579997 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] discards 35d535ea83a9 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] discards 5755852cb93b 113: onsuccess: #898: 1: Success after linux: 3 commits discards b5a14eedac9e 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 94a5300d34c8 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 3791e5b0142d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] discards 03dafac3c984 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] discards 8e874de2792f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] discards 29c3be77657e 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] discards c0b6c98a00d8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] discards 439e802c426d 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] discards 83a1384cc977 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] discards e1066c5c5530 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] discards dfc9ca9898fb 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] discards f5cbf2c978cb 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards 4b422503bf3d 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 01e621d74442 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] discards a0ce84c0c119 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] discards a6468fc1ee14 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] discards e20bf0a38d22 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] discards d0c18ab2f110 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] discards 140582297719 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] discards a284503b832e 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] discards 4c15fcfc823e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] discards e68c28b69729 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 0d84d4e93792 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 5e9acb34d7fc 89: onsuccess: #864: 1: Success after binutils: 25 commits discards bf0d077ce402 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] discards e6f6ccd94d0b 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] discards 6593f825ced8 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] discards 3ab348576810 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards f4222086b379 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards ad4703ae1364 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards bc5b0249597a 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards e5edb58eb206 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 94c2c8d450eb 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards c7e8faa9a414 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 6d9a469e24e7 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 39e8e037a7a0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] discards b4673e2094b5 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] discards d778303db0dc 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] discards 61835cd9eb25 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] discards f0674c05338c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards d223a0903470 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 7c3f2c59cb82 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] discards 51d6ec4f18e5 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] discards 3abf142d525e 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 1dc1bc153309 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 48f15457bd31 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 7922048a2f2b 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] discards d6f2fba93e24 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards 53838658f0bc 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 033e98ef2d07 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 8b064209e1b3 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] discards 62d4756705af 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] discards b74df565d598 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] discards 6f64c2722856 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] discards 0b27ac5d7429 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] discards 3cae9df2b72c 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] discards f201e2c6126b 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 5a4cd4862f83 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards cc3fc04c8b26 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 31b3a05afc49 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards 8e35730c2909 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards b0cce3c70df0 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 07cfa39d72d5 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards 3f53f0e696bb 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards 50eee8e35f91 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 1a3428979398 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 6806473b34f4 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 76a7188d0900 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 63d21d1964f8 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards a599feef2f51 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards 5a8cba946ed0 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards 3dc51bf61630 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 53612fd6360f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] discards 5ec7abf5a944 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards 7582b6e3c007 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] discards c6d7c4d992f7 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards 03ad31833b5a 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] discards 601d191fdd29 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards af9898a58810 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] discards 5a2f712b9e89 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards 581f326197e0 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 23ccc7b837fa 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards b752bfcbc82b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards 1053761aa93e 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] discards 4d29bf895f16 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards d1fa9df0392a 27: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] discards a97b5e194d57 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/g [...] new f9c583093ae5 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/g [...] new 9ffaec291f05 27: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new e7c77219de40 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new d3996d3d0b45 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] new 8966db545434 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 3ee6ff0ede54 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 84ccb2127e12 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new cb5f796c74e4 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new 4438f28e7583 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] new 2c92597171d7 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 536bcd132a23 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] new e17cafd4e80c 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new c7694f185214 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] new 630f54764fa5 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 933de5900b31 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] new d6d352ef8e9f 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new 985b7e81ab8b 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new d7a96896f2d3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new 275c63abecef 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 6c7c6993613f 45: onsuccess: #815: 1: Success after binutils: 6 commits new e37382eb0ee4 46: onsuccess: #818: 1: Success after binutils: 10 commits new 6c802f6864b4 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new d27127c95a5d 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new 182bc337ab09 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new 55935ec5b616 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new f4a1aa1fba43 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new 7d44c7090b33 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new 33bd54070ae0 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new 6d86d392bc8b 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 9506dec20c16 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new 6c47c71edcc4 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new 61c05884fad2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] new 1263208b467c 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] new f099320263e4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] new b22b01f036ed 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] new ec4672a63db9 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] new db315629b771 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] new d8ba300b1806 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new e0504c474e70 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new c09b8200d235 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new f36281b49cf7 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] new 9b0eaa426cdd 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new ec032992165e 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 8d8ab106576e 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 503fcfc6ae80 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] new 33d9eee480f5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] new 4979e5dc9307 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new f68e06ba00f2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new c3cbc079c47e 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] new 0fcf863e5e2a 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] new dee1dbed1f9f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] new c245f2a0b962 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] new 234c91e12538 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new a2f526294fbb 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 4cb0f55645d3 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 887a3006852f 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 0f29cbd5e8d6 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new e70fabd32e98 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 7b48d2c838c8 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new ee1dc6e98ff4 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new a663039caf57 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] new 8b755c8a11dd 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] new 572ef3a24221 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] new 718ac224506f 89: onsuccess: #864: 1: Success after binutils: 25 commits new de30c97c603e 90: onsuccess: #867: 1: Success after binutils: 4 commits new 2de21e310897 91: onsuccess: #870: 1: Success after binutils: 5 commits new 83bdccb7b557 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] new ae17ce143205 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] new 11de2c05fb07 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] new 95e7ee2d39f7 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] new 7d01f7b3315f 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] new f2612be6e418 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] new cefaef16a1ea 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] new 68cb1b836390 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] new 407239378e56 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new eb749b2cb9cb 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new e5fcce6bd4f2 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] new 1ebb243213cf 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] new bf7d39ecfe83 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] new 0f51abad29b9 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] new f48ac23a31e1 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] new 84dcd99e792f 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] new 893b683266fb 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] new c490b8d44b9e 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] new d8753379fba3 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] new 4a50dfa7ed74 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 52c5a732fd95 112: onsuccess: #896: 1: Success after binutils: 24 commits new b41e8f592399 113: onsuccess: #898: 1: Success after linux: 3 commits new 55f4c33b4a71 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] new 9513d4f7f9ef 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] new e1c2b4c6670b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] new 38cee90cc2d6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] new 10ce5462085d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] new 44d77d71fe49 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] new b2052976a1b4 120: onsuccess: #906: 1: Success after binutils: 29 commits new a6d66f095d28 121: onsuccess: #908: 1: Success after glibc: 2 commits new 7f5ecdcc21af 122: onsuccess: #909: 1: Success after linux: 2753 commits new 5b1469a1e00b 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] new 5598f104a8f1 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] new d1358c593429 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] new e71f3dfc582e 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] new 7e3675ff9cf0 127: onsuccess: #914: 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 (1a010c8199c1) \ 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 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39576 -> 39752 bytes 04-build_abe-gcc/console.log.xz | Bin 215940 -> 215596 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 243068 -> 244924 bytes 08-build_abe-gdb/console.log.xz | Bin 38752 -> 39124 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2132 -> 2024 bytes 11-check_regression/console.log.xz | Bin 13508 -> 17740 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 57 +- 11-check_regression/mail-body.txt | 167 +- 11-check_regression/results.compare | 59 +- 11-check_regression/results.compare2 | 2791 +++++++-- 11-check_regression/results.regressions | 59 +- 12-update_baseline/console.log | 36 +- 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 | 169 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 59 +- sumfiles/gdb.log.xz | Bin 1862716 -> 1948852 bytes sumfiles/gdb.sum | 9373 +++++++++++++++++++++++-------- 30 files changed, 9963 insertions(+), 2855 deletions(-)