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 e2737c86e00 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards e865eabb3f1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 7f4d0b05c64 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 7d823a8ec07 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards cf87caa7014 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 99245dff125 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 1a1662d9dda 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e11f241ce2b 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards e28a3fdbdaf 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6b7b26f843f 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a547c6cc6fc 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9d59170997f 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e88d3ed36b2 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards bee8a9e5e68 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards bba6c46b029 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4702ec374bf 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e0a3b4c3d5b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 11284671d6a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a7703ab4c31 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3e6cabb0d67 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 52472aa85b5 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 53ec4fa791d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 20d4222e67a 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 4582f372808 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 1469c1f412a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 97a71ab2946 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards b85afd672d3 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards eab93e84c7e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 232254e1b9c 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards cadc874bb99 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards da0ca84fc27 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 02156e9981a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 626fa7bf7ac 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards d144662afd9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 0da2b72b906 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards ae8e486fe4a 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 4e3746814fe 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards a8f86fde468 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 00808566063 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 70a08c8d5e9 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 27fb33a82cc 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 4d7f81d3e6a 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards c4577bb0204 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 9f6bd1ce358 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards d43c33615b7 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards ccbdd103720 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 2e5d91568d8 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards a74bd6b17b5 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 864664ffb45 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 93f0dacfe72 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 0373ffd1daf 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards db61cb18254 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 7c145db268f 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards fe05424b9e7 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards a1cfcc51881 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards ba40d515d7c 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 3ef649ee4a7 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 6fceff57ea5 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards ef9e68e567e 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 2c3ed3f8a9e 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 33a2977dce5 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards f38447e0e4c 149: onsuccess: #684: 1: Success after linux: 10 commits discards 9e18ba165a5 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 3477c9f65c7 147: onsuccess: #681: 1: Success after gcc: 6 commits discards f77c0813449 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 299eaa18f80 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 24158225a29 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 04427811d50 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 8cbf20f132a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 0a521bd0f71 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards de128f19213 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 7f580ccf03b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards a4e5001ec88 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards b6b52c8b488 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards ceeec435886 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 7f902e856ad 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 8c7c1847bfc 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 1cd610e6957 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 77881cf5ac3 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 1ded2462d01 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards b96e99c3a4e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards ad0f1ff799c 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 5113e3357a1 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards bcfb5391492 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 60e88c51bf4 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 0ec595fb9b6 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 05c5ef0de9e 124: onsuccess: #657: 1: Success after glibc: 2 commits discards c77f5e03e82 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 8956f088a5f 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards ce8cb6e8741 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 788d3933257 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8884af864d7 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 8c78f8bb9d6 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 344f4444481 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 89920b8c1a9 116: onsuccess: #647: 1: Success after linux: 3 commits discards f4c96081a7b 115: onsuccess: #645: 1: Success after binutils: 27 commits discards f499fe318d7 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5d01ff8d53a 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 918149d312f 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 0c0e4a4e423 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 072a25255d5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new a0ca8db7eb1 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new df97b734f88 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 91a724754b1 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new d00a674cb21 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 3968e2a12be 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new c720e550082 115: onsuccess: #645: 1: Success after binutils: 27 commits new 2debe2f1360 116: onsuccess: #647: 1: Success after linux: 3 commits new 96c83646e18 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new d15dab9ac58 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 6c31814f27f 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 0cd6b4485b4 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 771c964a31d 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 2c53acf8866 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 43dca4c83ec 123: onsuccess: #655: 1: Success after binutils: 22 commits new fa455300ce1 124: onsuccess: #657: 1: Success after glibc: 2 commits new dd8e83f5343 125: onsuccess: #658: 1: Success after linux: 3224 commits new 5028611a72c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new a663192d15f 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 6efd84e0d13 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 1058829ca9d 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new bd8d0a8507e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new cabaf79a1cf 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 62bf32abc62 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 99c60f3e158 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 63deda6d649 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 2bf408ec596 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 552b89547a3 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 1d60c1c86f4 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 73f97305c78 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new aa25579c0d5 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 52f68b2aa83 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new d5836656c91 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 19f60ebcdc9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 95d6b98eac0 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 4a6b0422a7e 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 077fc89a5ce 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 78957721937 146: onsuccess: #680: 1: Success after binutils: 20 commits new 5a8e1f6afb1 147: onsuccess: #681: 1: Success after gcc: 6 commits new cea081b7c76 148: onsuccess: #683: 1: Success after glibc: 9 commits new eecdfe721c8 149: onsuccess: #684: 1: Success after linux: 10 commits new 68e7599faa1 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new cf8a827e66b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 488dd1f84c7 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 0ad01e52d32 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 839d55420dc 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new de788c83b09 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new e1dba2bdd66 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 0ddc4d6b50c 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 2f3786b8451 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new a9729f54ba8 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new dbe9e257065 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 3b259478351 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new ef181f5049e 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new ef21c1e1124 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 3401a7e39a7 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new e0dfc9dc128 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 56f6a48e588 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new cd65dac47da 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 46f3eba0a1a 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 1b62a037602 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new b81e68889e1 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new e228d83656a 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 0c681492c18 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 0e53beff629 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new ad5b8befc9d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 9850111eb3e 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 1fdf69f746c 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new bac75dba64b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new e4399ef1f27 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new c4cc654f216 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 73e550d7bb3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new e150e6a60d9 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 06823571ed6 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 91eeabdc936 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new ec787a19098 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 336345dbee6 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 914107ba15e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 535d872abf5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new d5a4c481d36 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 26d7de5eee1 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new cedffcb76ef 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 483a126dcf2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 2c08910eb84 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new d36ea1ea08f 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 11463fbca1f 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new f226ba89553 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new da8a8f64d1a 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 69ec791e373 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 7fc2377602e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new bbd90fe1da4 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 20db68e578a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 71ef8715419 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 816da92c5ad 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e43cfd5a8f1 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 4e16e917e1b 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new af4a79973c9 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 4844673247c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 389dd206062 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new fe877fde434 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c4671904831 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 6e29ca0aacb 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 8fc752f4a7f 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 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 (e2737c86e00) \ 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 1748 -> 1932 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 3536 bytes 03-build_abe-binutils/console.log.xz | Bin 38764 -> 40156 bytes 04-build_abe-gcc/console.log.xz | Bin 203564 -> 204944 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9028 -> 8504 bytes 07-build_abe-glibc/console.log.xz | Bin 246092 -> 244268 bytes 08-build_abe-gdb/console.log.xz | Bin 38308 -> 38952 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3776 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2020 -> 2080 bytes 11-check_regression/console.log.xz | Bin 6036 -> 4416 bytes 11-check_regression/results.compare | 10 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 42 ++-- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++- sumfiles/binutils.log.xz | Bin 63068 -> 62928 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83968 -> 83992 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 122240 -> 122228 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 28 files changed, 391 insertions(+), 393 deletions(-)