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 18a709f2d0 147: onsuccess: #681: 1: Success after gcc: 6 commits discards aad8710867 146: onsuccess: #680: 1: Success after binutils: 20 commits discards aa0be89123 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards f766b36254 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 42193bf965 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 24cbee938f 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards e7693cd140 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 606b95512d 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 6487db7e4b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards d183ce1969 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 689e2a56ef 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards fb8d2bed67 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards f9acb75826 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 10af84c926 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 812cb5a7db 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 064fbe1d7f 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards a3e29a8b6e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 09db655321 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 42c4486ef1 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 4ba7473c1f 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 2f379aea8b 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 655a48c582 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 0834b8bc17 125: onsuccess: #658: 1: Success after linux: 3224 commits discards c2edc36c5f 124: onsuccess: #657: 1: Success after glibc: 2 commits discards a7e259723f 123: onsuccess: #655: 1: Success after binutils: 22 commits discards c53ebd08a9 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 5b5df3e6ae 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards bacec76722 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 6615806ecf 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards a093d08966 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 7feff0d903 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards bfe3d125e3 116: onsuccess: #647: 1: Success after linux: 3 commits discards 47f0a16643 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 036ba8d9de 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards dc70348ad9 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards d02ad50a81 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 26a87686c2 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 0e95f749e0 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 05aab08eb5 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards 65b6839e50 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards bfb1c85a7d 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 3114bf3deb 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 51aeb8f6f4 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards f13a125818 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards ef099971cb 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 2c414bf964 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 851ef620d2 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 65678afdba 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 9659383b2c 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards f6e088ded4 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 580c8b4c62 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards d512ef80c1 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 36472efe20 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 0ef936ab5c 94: onsuccess: #616: 1: Success after binutils: 2 commits discards fd79567e88 93: onsuccess: #613: 1: Success after binutils: 19 commits discards fffff68001 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 9ccb34a38c 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 28582690a0 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 732f77cac9 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards ebbeeff726 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 125d8bc03a 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 1367b4cd36 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 98cc22b7ef 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 63478f7239 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 02a38c7f3d 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards a05966f8ee 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards b6070bbd65 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 03efc4cb14 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 818a7cbfaa 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 579e65e55d 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards b96ce86723 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards df1f45d273 76: onsuccess: #592: 1: Success after linux: 63 commits discards 939932ee26 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 4204720b7c 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 53c96cd336 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 8a48110330 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards f153beb287 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 3fd9b09edc 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 4b748715d9 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 8ff9721896 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards e65d2a16da 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 0a945cc33a 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards a201ca3ed4 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards a55455dcdf 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 17a48b2a20 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 8123faa841 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards cc630e367c 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 92bb0f9403 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards d5246d636e 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards eccb025b41 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 4b06031da8 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 1784645a4b 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards d15320f39d 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards e30a685a23 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 3223bc2b4a 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards ea59048046 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 21e138ece8 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 6959097cb6 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards c26ce52bea 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 728798791b 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 68a5911c7b 47: onsuccess: #556: 1: Success after binutils: 12 commits new 68b4220525 47: onsuccess: #556: 1: Success after binutils: 12 commits new f218414ecf 48: onsuccess: #559: 1: Success after binutils: 6 commits new 1113d5c2a5 49: onsuccess: #562: 1: Success after binutils: 9 commits new e6e2a56301 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 7dceb31606 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new a27baf4498 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 3845bff3a4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 0950c77a7d 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 17f3847a39 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 16fab75f6d 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new e70c3da73b 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new dbde31beb8 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 4112ca3b30 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 1bf8390ef0 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 7f021669fd 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new f64d84a9a0 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 27a6a86cd2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 359cc8f564 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new c4ca303352 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 970909764e 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new cdc8e3dcd0 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 76a7e3dbb3 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new afb46ec876 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 488ffbd38f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 4d810b0975 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 2190d02429 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new e40b8070a3 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 5942062597 74: onsuccess: #590: 1: Success after binutils: 16 commits new 1da32a27bf 75: onsuccess: #591: 1: Success after gcc: 25 commits new aefee677b8 76: onsuccess: #592: 1: Success after linux: 63 commits new adace39a47 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 6872fc40e2 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new ff1e49cb2e 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 68ffb98291 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new b14ee641fa 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 5b017755b2 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 14b6c3c3ed 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 6c4377a6be 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 150ea84d21 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 8cba9b60cf 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 68dae38554 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 0af16a71ef 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new aaed99857d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 9c505bb132 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new d136de67a7 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 6ff92c0199 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new ddb68d4dbd 93: onsuccess: #613: 1: Success after binutils: 19 commits new c6e12e76dc 94: onsuccess: #616: 1: Success after binutils: 2 commits new 11a057c99b 95: onsuccess: #619: 1: Success after binutils: 5 commits new e82cd56b62 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 7a22b63ad2 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 23608160be 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 7f2b306ccf 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new e73b2c20dc 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 318f7604f1 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 5bed7d88ca 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 2996fea12a 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new aa49d1a5ac 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 720d79cea9 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new cc711c6cec 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 5aa7a01543 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 31eccf61bc 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new e8388a622b 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new c5f2178f82 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new ce55053d15 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new f2559f12b9 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 6eb45fe7ef 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 1736656da1 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 08eca66200 115: onsuccess: #645: 1: Success after binutils: 27 commits new d79b46df70 116: onsuccess: #647: 1: Success after linux: 3 commits new 8c1f7152a0 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new af2d71e1f8 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 5e3c95a932 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 985f5afbca 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 11863243fc 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 84ed399237 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new dc3a4ba053 123: onsuccess: #655: 1: Success after binutils: 22 commits new 9bc81d371e 124: onsuccess: #657: 1: Success after glibc: 2 commits new b74a46fe2e 125: onsuccess: #658: 1: Success after linux: 3224 commits new 5ebbcce9d4 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 969b4a52c8 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 9bc717445a 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 8818e5f450 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 19421c3e33 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new a468984311 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new cdd2ef8b2a 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 2bcb633774 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 370d6cc05a 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 7dc708d799 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 4c885c611d 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new d84f60da3e 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 11335d6cf7 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 3f14b0556a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 64c3f16f7e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new b5cd28c2a4 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new b121c22bd0 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 59ae46fa50 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 2fefbfdd02 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 7b5a798f21 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 8ca0eed5ba 146: onsuccess: #680: 1: Success after binutils: 20 commits new 2cb949ac40 147: onsuccess: #681: 1: Success after gcc: 6 commits new 7511fcafcb 148: onsuccess: #683: 1: Success after glibc: 9 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 (18a709f2d0) \ 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 1724 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39720 -> 39824 bytes 04-build_abe-gcc/console.log.xz | Bin 214444 -> 214236 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8464 bytes 07-build_abe-glibc/console.log.xz | Bin 245220 -> 245132 bytes 08-build_abe-gdb/console.log.xz | Bin 39536 -> 40092 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3860 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2220 -> 2264 bytes 11-check_regression/console.log.xz | Bin 4796 -> 4700 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/binutils.log.xz | Bin 63144 -> 63052 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83968 -> 83852 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122400 -> 122188 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 26 files changed, 379 insertions(+), 379 deletions(-)