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 7e3675ff9cf0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] discards e71f3dfc582e 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] discards d1358c593429 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] discards 5598f104a8f1 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] discards 5b1469a1e00b 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] discards 7f5ecdcc21af 122: onsuccess: #909: 1: Success after linux: 2753 commits discards a6d66f095d28 121: onsuccess: #908: 1: Success after glibc: 2 commits discards b2052976a1b4 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 44d77d71fe49 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] discards 10ce5462085d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] discards 38cee90cc2d6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] discards e1c2b4c6670b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] discards 9513d4f7f9ef 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] discards 55f4c33b4a71 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] discards b41e8f592399 113: onsuccess: #898: 1: Success after linux: 3 commits discards 52c5a732fd95 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 4a50dfa7ed74 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards d8753379fba3 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] discards c490b8d44b9e 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] discards 893b683266fb 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] discards 84dcd99e792f 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] discards f48ac23a31e1 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] discards 0f51abad29b9 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] discards bf7d39ecfe83 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] discards 1ebb243213cf 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] discards e5fcce6bd4f2 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] discards eb749b2cb9cb 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards 407239378e56 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 68cb1b836390 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] discards cefaef16a1ea 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] discards f2612be6e418 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] discards 7d01f7b3315f 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] discards 95e7ee2d39f7 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] discards 11de2c05fb07 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] discards ae17ce143205 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] discards 83bdccb7b557 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] discards 2de21e310897 91: onsuccess: #870: 1: Success after binutils: 5 commits discards de30c97c603e 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 718ac224506f 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 572ef3a24221 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] discards 8b755c8a11dd 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] discards a663039caf57 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] discards ee1dc6e98ff4 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 7b48d2c838c8 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards e70fabd32e98 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 0f29cbd5e8d6 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 887a3006852f 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 4cb0f55645d3 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards a2f526294fbb 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 234c91e12538 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards c245f2a0b962 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] discards dee1dbed1f9f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] discards 0fcf863e5e2a 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] discards c3cbc079c47e 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] discards f68e06ba00f2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 4979e5dc9307 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 33d9eee480f5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] discards 503fcfc6ae80 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] discards 8d8ab106576e 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards ec032992165e 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 9b0eaa426cdd 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards f36281b49cf7 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] discards c09b8200d235 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards e0504c474e70 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards d8ba300b1806 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards db315629b771 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] discards ec4672a63db9 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] discards b22b01f036ed 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] discards f099320263e4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] discards 1263208b467c 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] discards 61c05884fad2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] discards 6c47c71edcc4 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 9506dec20c16 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards 6d86d392bc8b 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 33bd54070ae0 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards 7d44c7090b33 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards f4a1aa1fba43 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 55935ec5b616 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards 182bc337ab09 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards d27127c95a5d 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 6c802f6864b4 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards e37382eb0ee4 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 6c7c6993613f 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 275c63abecef 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards d7a96896f2d3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards 985b7e81ab8b 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards d6d352ef8e9f 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 933de5900b31 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] discards 630f54764fa5 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards c7694f185214 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] discards e17cafd4e80c 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards 536bcd132a23 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] discards 2c92597171d7 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards 4438f28e7583 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] discards cb5f796c74e4 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards 84ccb2127e12 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 3ee6ff0ede54 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards 8966db545434 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards d3996d3d0b45 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] discards e7c77219de40 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards 9ffaec291f05 27: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new f1dbc8ad108c 27: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new e0fa5ab21d73 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new 613f1d5dcd2d 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] new da3680a2f608 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new b192a34f191e 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 60edc5cd5ba1 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new 1e8cf78eaefe 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new 6e879140a60c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] new d3085e58bf87 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new ac4e1756f9e0 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] new 6832ea58e788 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new 87c829c0260e 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] new 0572b30c0cbc 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 2523551ff86e 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] new 23815e664f92 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new a499a55e7cfe 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new 75082f4ae3ef 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new 5af7d0f30cd2 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 6214a1a098cb 45: onsuccess: #815: 1: Success after binutils: 6 commits new 960ecbc5bb89 46: onsuccess: #818: 1: Success after binutils: 10 commits new 9862a377a461 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new 167f95674acf 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new 63ef2593144e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new 8dd85d0014c2 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new 7a2304be0d4e 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new 8e89f0fc13be 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new 9d540975b609 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new 36ccbe186cc9 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 1a433a97b796 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new 8fff65a5b632 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new 551492da3e5a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] new 19d304d827d7 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] new acfbaeec0939 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] new 2d436e78fc3f 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] new c435d42e2461 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] new 901f14430e2d 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] new 798c12ec0bf5 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new 7c3ff005505c 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new a52aff5592f5 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new 7002aaae7891 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] new a9ad39e19a3d 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 8b3f804dac07 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 23bffd83f7e1 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new e582627606e6 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] new 9151b62df152 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] new 9bd303d5a6c1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new eb8d3b477f90 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 52a168b34ada 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] new 728f66de1a53 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] new a3885649dd01 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] new e13f5aeb53c2 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] new d8ef177fae25 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new d451bb3dc21a 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 2fe0b788826e 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 47c784fb5bfe 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 9cfe49aaa37b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 26d6a8cab70d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new e1107dc73025 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 0caa35b598fa 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 9e74b11aa0b0 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] new 4a8b781fb287 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] new 918af72c62dd 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] new acf5332f3833 89: onsuccess: #864: 1: Success after binutils: 25 commits new 2929e690e3d4 90: onsuccess: #867: 1: Success after binutils: 4 commits new e372312146b2 91: onsuccess: #870: 1: Success after binutils: 5 commits new bc8e8d9100b9 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] new 207154bf22aa 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] new 72b1c305e85e 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] new 540a2cedeebb 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] new 54f63ffd1732 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] new 9fa90d8721d5 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] new 413b782c2cac 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] new 2a50ab571057 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] new 4adecabe89fa 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new 4e4ecf0f8a7f 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new 0122c1231d2f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] new aeae2ac8e3fb 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] new a13b9d6c0b22 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] new 98175aab5172 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] new 8a86523cf23c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] new d77cf82e1077 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] new 9c6eb28ab3f6 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] new 77ffa9f549ce 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] new c2394433c907 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] new 619724f5b1ac 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 35d7c499b26a 112: onsuccess: #896: 1: Success after binutils: 24 commits new 91accc23b93c 113: onsuccess: #898: 1: Success after linux: 3 commits new 53add98d280e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] new 1cddcaa8e38a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] new 49ae028edd72 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] new 265caa292893 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] new 2434d4d1301d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] new a173af47b19f 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] new 1c08def51019 120: onsuccess: #906: 1: Success after binutils: 29 commits new d49939fcad50 121: onsuccess: #908: 1: Success after glibc: 2 commits new bd9ad6648c24 122: onsuccess: #909: 1: Success after linux: 2753 commits new 3554aa8eef38 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] new 718b7944d902 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] new bf5760ab3b77 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] new 5f96d013d3eb 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] new ca822c8b04f8 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] new 290fbba36533 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...]

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 (7e3675ff9cf0) \ 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 1740 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39752 -> 40564 bytes 04-build_abe-gcc/console.log.xz | Bin 215596 -> 215276 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 244924 -> 243300 bytes 08-build_abe-gdb/console.log.xz | Bin 39124 -> 39212 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2024 -> 2020 bytes 11-check_regression/console.log.xz | Bin 17740 -> 14744 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 58 +- 11-check_regression/mail-body.txt | 184 +- 11-check_regression/results.compare | 125 +- 11-check_regression/results.compare2 | 1863 +------ 11-check_regression/results.regressions | 125 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 186 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 125 +- sumfiles/gdb.log.xz | Bin 1948852 -> 1924584 bytes sumfiles/gdb.sum | 8054 +++++++++---------------------- 30 files changed, 2959 insertions(+), 7871 deletions(-)