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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts.
discards a9cf4b5ae0 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 3ccd13a29c 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards f4375d1465 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards d52d9e5b50 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 29494d45d4 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards efac735e7e 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 1c4135dd52 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards da4d31d3d1 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards e8a683d860 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 8bc64fd6ac 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 63b7fda17e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 290d9a16ac 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards dd3412a2d4 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 11d76ff601 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 839c15a0ab 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards b600f4b35b 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 019532f5fb 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 0620f1c128 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 273cd849f2 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 53e2697592 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 16e743d9ab 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards da71a41e64 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 00e6e24599 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 67dc8ac8ed 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 3f7253dc3b 116: onsuccess: #647: 1: Success after linux: 3 commits discards 80b147c1b2 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 2c771f7cf6 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 5d446f7db6 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards eaa04176e3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards fb70fe6633 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 91253d2dfa 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards f190ab4599 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards fad3aca6e9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards e7615a4131 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards a754284bfb 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards f30bea3840 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 05ef9cd0ef 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards a377df4b02 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards e025711eb3 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards af390ccef1 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 3c0d826d91 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards c9c8b1c99c 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards c9e6a73732 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 410876bf4c 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 341bfa00e6 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 6b793e521f 95: onsuccess: #619: 1: Success after binutils: 5 commits discards deca6d7968 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 1417990153 93: onsuccess: #613: 1: Success after binutils: 19 commits discards ed101a548b 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards c762a20df8 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 14f6128818 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 3db9da3cce 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 64f9ba80d7 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 4e76f2ca69 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 64603e2c9a 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards c9efc48a5f 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards c1b2583383 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 3f7f483c69 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards f69ddcea5e 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards f3dbc9d2ab 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 79acd242c6 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards c083b6eabf 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 71fd5a7f6e 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 475156675d 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 48af96b0f5 76: onsuccess: #592: 1: Success after linux: 63 commits discards cc5483a5bd 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 68c183d1ef 74: onsuccess: #590: 1: Success after binutils: 16 commits discards b9d5ff195a 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards a6b3f2b912 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 327552ceb3 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 34fe0e283f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards a02dfefc25 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 82a89f81e9 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 480114186e 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 6b863a3cbe 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards d9f85468ee 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 1b30f57a9e 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 9b9ab86091 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 6850a6edec 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards a37581defb 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 1be0c80776 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 7bb18dff99 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards e48393adcc 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 8459a4b858 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 6bbb518ad4 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 5a483f9e2b 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 76585c860a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 0a9d630b0d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 2b79c162ae 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 5828e43ade 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 53b7175feb 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 4e63b8f289 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 1ad21432e2 48: onsuccess: #559: 1: Success after binutils: 6 commits discards fcae0a2f1f 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 8b01b385f3 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 2405ea4819 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 640661943d 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards f60b36db44 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards e34b74ca7a 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 4158822cb9 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 61164da866 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 7156894a6b 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new e221c344a6 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 189944ff9a 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 92e7105179 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new a5905cb3d1 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new e0cf98a823 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 7898510da8 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new be79ac8e07 47: onsuccess: #556: 1: Success after binutils: 12 commits new a1851e898b 48: onsuccess: #559: 1: Success after binutils: 6 commits new 14663ea2e2 49: onsuccess: #562: 1: Success after binutils: 9 commits new 6eba53bc95 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new e3e2738981 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new c20e10bf6c 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new e116134703 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 9512a58650 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 462a8354b2 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new ab47be0b09 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new fd42e2f208 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 13e227f00a 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 31a10effc6 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 7c044456e0 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 46ef4e5e72 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 7e3a0ba3b4 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 473333ba37 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 75876036af 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 6ae3c26185 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 0b4c4d75f0 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new ed2d290d76 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 0d16b4749b 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 07d852495d 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 0775007dcc 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new bc0848cb43 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 3fb0e76402 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 3781da46d9 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 9e6262de48 74: onsuccess: #590: 1: Success after binutils: 16 commits new 5e2144ef76 75: onsuccess: #591: 1: Success after gcc: 25 commits new 841dba5d70 76: onsuccess: #592: 1: Success after linux: 63 commits new 55fb0bca1f 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 980ae4e711 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new db7e15a753 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 01bc445483 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new fe6eb100d0 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new a2219ca752 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 376488bdeb 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new b4bada0b22 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new a10c1a7719 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 600baeed91 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new a1e6b9d1a3 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 70963ba340 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new a128ca7f0c 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new eb977dee66 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new efd97215d7 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new e59a5f09c1 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 52af062154 93: onsuccess: #613: 1: Success after binutils: 19 commits new 695b0131b4 94: onsuccess: #616: 1: Success after binutils: 2 commits new f4a972006c 95: onsuccess: #619: 1: Success after binutils: 5 commits new 68ae8152c8 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 6517b7459c 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 2d66870c68 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new aaa0beef6f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 0fc8905e50 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new d05208b7ea 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 362aac517d 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 03fabf267f 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 26fd47d6ba 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new c52c5e59e7 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new f489ffe4a1 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 2dfd432065 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new e67a8f18cd 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 0a902aca05 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new 6cd977d711 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 780ec4542e 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 271dda9343 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 920d53d8cb 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 5ff5efd10f 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new af9d7332e5 115: onsuccess: #645: 1: Success after binutils: 27 commits new 299fe87784 116: onsuccess: #647: 1: Success after linux: 3 commits new 71d899872d 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new c45570d3a2 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new ff9437646b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 762a20cb25 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 42303d85ec 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 1f4192cd61 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 2de6d5d856 123: onsuccess: #655: 1: Success after binutils: 22 commits new 4b42fd68fe 124: onsuccess: #657: 1: Success after glibc: 2 commits new 5d762aa6c9 125: onsuccess: #658: 1: Success after linux: 3224 commits new 63995c4cdd 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 1839979f8d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 5bac627ddc 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 589ae13971 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new aca603eadb 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 35be945769 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 7501557b4e 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new fd9751a1f5 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 72ee659951 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new af6a4dc181 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new aa1868a21a 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new f154a2ead5 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 008cfbb831 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new a4c1888ee5 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 984464a395 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new dfced462ba 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits
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 (a9cf4b5ae0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]
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 1716 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39984 -> 40044 bytes 04-build_abe-gcc/console.log.xz | Bin 214832 -> 214492 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8428 -> 8324 bytes 07-build_abe-glibc/console.log.xz | Bin 246236 -> 245056 bytes 08-build_abe-gdb/console.log.xz | Bin 39552 -> 39420 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3860 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2064 -> 2248 bytes 11-check_regression/console.log.xz | Bin 5460 -> 5196 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +-- sumfiles/binutils.log.xz | Bin 63104 -> 63104 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83876 -> 83876 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122208 -> 122212 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 28 files changed, 389 insertions(+), 397 deletions(-)