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-arm in repository toolchain/ci/base-artifacts.

discards 1a995ecd88 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 5ed762a9c5 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 25a7b3e0d3 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 65cac425c4 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 3045e5604a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards e68318406f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 8b9362a10c 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 183bd1aabb 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 71f8bf9dbe 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 6ec21a3b9a 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards a3c634c5b6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 216dfa6f42 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 7df8c06881 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 8b5ae4e64f 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 01e9cab8da 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 374808e99a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards eb9fa6a0bc 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 00b0cd2863 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards f2a65232d2 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards d081cb3f2f 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards c6bffaa386 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards bc90ae7c56 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 3e36946c42 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards bbf9224097 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards cd74e6669f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 071fc2cde4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards d51be4c530 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 35a24b6f9f 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards ff1aa6ed87 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards a693eb882e 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 9c6a8f4d2e 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 11c8b3b585 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 098e6b2378 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards f36254ca69 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 78a6bf8092 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 2f2e41a1bb 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 65e5edbf0c 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards df553f016e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 138838ff41 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards d350d28116 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 2eedac8611 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards ff3a19a30c 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 4651d672ad 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards e32668f060 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 98941a69ad 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards c20ef5792b 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards d20b14e2b4 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 22b3a814de 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 0943094e10 125: onsuccess: #614: 1: Success after linux: 12 commits discards d753b2e1b1 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 8ef14c268b 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards f9c019da93 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 1072dbfdca 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 6c75d0246b 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 155ed1ec4d 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 2062bdc80d 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 97eb2ee26d 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards dc580a8549 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 51dbb65aff 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 803820eee1 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 87f823f19f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 4f9a5f1d70 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards b1a9fade2f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 852f97d460 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 23738efbc8 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 8aeb244318 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards c797b3c5e7 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 71d12b5cef 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards b2a4b2178d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 9739e29718 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 4bf9b1572d 103: onsuccess: #589: 1: Success after binutils: 3 commits discards cc3b37ba8b 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 8ad173eb0b 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards a8e3215f84 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards ab75a01bb9 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 421ff009f7 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 0cefa0e247 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards c897cc850c 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 907a0903d6 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 61ab1de546 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards c06159b7b0 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 347f0ce0a3 92: onsuccess: #575: 1: Success after linux: 34 commits discards 3415c25972 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 88cdaed829 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 6e2280e7ce 89: onsuccess: #570: 1: Success after linux: 11 commits discards 952e07d183 88: onsuccess: #569: 1: Success after glibc: 10 commits discards f889f6e10b 87: onsuccess: #567: 1: Success after binutils: 8 commits discards f7ad32e970 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 58d8242fad 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards ca1988e02f 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 431629226b 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards b71d67b249 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 44ffdaa0db 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 284c06454e 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards dd2a061adf 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 8220321d1f 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards a13ed4074b 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 4c87d4125e 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards a13c43e895 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards a60e03a715 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 6884a5bc1d 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 4e83eb0fdb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 56e9430cc2 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 6a2bd6f40c 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 75a0d8c49f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 07b8fb3b5b 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new b9d14dee34 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new ac148c57a2 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new fd010b6c17 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new cee97a8762 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new a238c47fe6 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 81fa19de53 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 526210cc56 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 76a11c9544 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new b4493ea908 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 08420d3d82 87: onsuccess: #567: 1: Success after binutils: 8 commits new f352bb4bfb 88: onsuccess: #569: 1: Success after glibc: 10 commits new a79baa0e6b 89: onsuccess: #570: 1: Success after linux: 11 commits new 477b585138 90: onsuccess: #572: 1: Success after binutils: 15 commits new a976ae422a 91: onsuccess: #574: 1: Success after glibc: 3 commits new 4c4f384c01 92: onsuccess: #575: 1: Success after linux: 34 commits new 26990b5a3b 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new dba64756c0 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 9d77201290 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new ea8d1baec6 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 1b3a01bc94 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new bd0dac2ad5 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 168bf701eb 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new d65033e271 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new d45d2e6eb9 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 40c1ce67df 102: onsuccess: #586: 1: Success after binutils: 5 commits new 67251a3155 103: onsuccess: #589: 1: Success after binutils: 3 commits new 2dc3f53f43 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 4f99c756be 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 7b3705132b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 1f9f03d44e 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new b981c67e2a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 6a6fce5ef5 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 1bfdd97b41 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 6e6f01f1ea 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 336c097a22 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 30145362a9 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new cb14b6c24f 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new f4651dd6f7 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 0a7090ac73 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new b6ac7bdb11 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 4db2ea8bb9 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new e1f6283349 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new ece97bf3fa 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new cb0272dc12 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 09145156c5 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 21b7a44f53 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new b82612bc0d 124: onsuccess: #612: 1: Success after binutils: 18 commits new 3a6e9249b6 125: onsuccess: #614: 1: Success after linux: 12 commits new 797b9dc1eb 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new b6e22d0eb9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 1f8172091c 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new c649e7eb12 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new fbba95ab14 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 5106fd78e2 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new d3dc6a7d2d 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 88dd632ae6 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 5bb6e492e4 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new d9f11ca240 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 8fba2a4491 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new c0879eb151 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new e81b8339e7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 7286de2ae3 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new c19d5b6824 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 1081da703a 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new ab4652a11a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 0015c5210b 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 6d6229aaff 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 9be011f85f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 0cffd3522a 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f457f4bfea 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 43ddca9a08 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 2e5e6e022a 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 7b929b4d9e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 13755abeaf 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 17f4ac24a1 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new e6f1b30b38 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new bb5dead26e 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 51f0dadf33 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 471e1837f4 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 9531a7307c 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new e4aca708cb 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new f039296570 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 810edff397 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 4bf98203cb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new fe82b94390 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 849467ae98 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 7a0c781b68 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new a0fa091c04 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 348f3d45cf 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 6066c78cf0 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new c2fa0eed67 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new b1a0dbb4e3 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 0e22655b15 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 04c71e3766 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 063fdbd56a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 56253213dd 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 52d376e266 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...]

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 (1a995ecd88) \ 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 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 51704 -> 51416 bytes 04-build_abe-gcc/console.log.xz | Bin 236728 -> 236548 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 236812 -> 236464 bytes 08-build_abe-gdb/console.log.xz | Bin 50036 -> 50604 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2124 -> 2132 bytes 11-check_regression/console.log.xz | Bin 9928 -> 16988 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 35 +- 11-check_regression/mail-body.txt | 166 +- 11-check_regression/results.compare | 80 +- 11-check_regression/results.compare2 | 3923 +++++++++++-- 11-check_regression/results.regressions | 80 +- 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 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 168 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 80 +- sumfiles/gdb.log.xz | Bin 1891124 -> 1807792 bytes sumfiles/gdb.sum | 9664 ++++++++----------------------- 31 files changed, 6306 insertions(+), 8006 deletions(-)