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 d23fc64eb8c 212: force: #24: 1: Success after binutils: 2 commits discards 641d032472e 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 70ce1e38067 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards cc5da72c581 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 46ba31c02aa 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards e8635e71b05 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards dadfb86f0d4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards b539d0bd059 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards ba03dee73b4 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1c82456e5ac 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards dcb958ed0a6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e2053fe5cf9 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 09e4d4601a1 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 88ecec7b88e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e29e16536ab 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 849a6126ceb 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2387b97c180 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ded5d13d6f3 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 353096743a4 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 0a75f26d30c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 032e8dc0616 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 4f44dd829be 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 9e3a7868daf 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards de633a93e5d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards f89b7876728 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 571100967a2 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards d0be0916d20 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 1d006334e80 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 8a15eb53173 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards c442ed3cb4a 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 1cd67853286 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 77d39ce378b 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 894e8bbeff5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 0d287d2e855 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards d9898c420f7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 6d7e17575a9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 841350e3f62 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 4e77618cda6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 49862106505 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards c822e673451 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards e80882aa849 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards d8ccc02ab41 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards ca07a678831 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 25c0051a4e0 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 36bf25527d2 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards c5a637e41a3 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 8f7de082f91 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 3e58e1c8b81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 32cbf082a56 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 258bd3b63e6 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 8eac1321f28 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 3a227ecc9b5 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards e929e7f5826 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards be2fc8ad262 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards afe7988a0c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 9c98c7c9d34 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards d25f99a292f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards e6c56bf7dbf 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 64e8c9006c8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards cc0cbf52192 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 880ffacdc76 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards f411babb411 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards e0cdc06ceae 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 4b85f6b8dd9 149: onsuccess: #684: 1: Success after linux: 10 commits discards d5fd0c98213 148: onsuccess: #683: 1: Success after glibc: 9 commits discards fd8995bd76d 147: onsuccess: #681: 1: Success after gcc: 6 commits discards ec590be6ae6 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 1defbe9eb61 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 7d5d99cc8b3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards fb9d574eb02 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards b37a6f3fa7e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards c4f9983aa57 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards d97848c944a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 8e6ceb6d505 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 738254df701 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards bd69f3d7f9a 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 4fb63b715ca 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 0cd17dafed5 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 7dd02395b17 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 4e5d027d446 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards a71f458c3fa 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 1353807f14b 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 7cb72c85f73 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 8f93da18fdb 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9193b2345f0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 80bb862f25a 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 7c735ce988f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 711180fb93d 125: onsuccess: #658: 1: Success after linux: 3224 commits discards fca17e32a2b 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 67cf3e9f5f5 123: onsuccess: #655: 1: Success after binutils: 22 commits discards ce81bcc2498 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards da9214d5b3f 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 4e7633f22af 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7a75dea3d2b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards a947f6736e5 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 4d7cf2ad040 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 3d5c6e260d5 116: onsuccess: #647: 1: Success after linux: 3 commits discards e71a85dc0eb 115: onsuccess: #645: 1: Success after binutils: 27 commits discards af6f1a6c701 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 890843da2b2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards dcbdab3a058 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new e030dcf3eda 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new d78616a09f8 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new ebe01a38def 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new d3df69e9481 115: onsuccess: #645: 1: Success after binutils: 27 commits new 6538cc53b38 116: onsuccess: #647: 1: Success after linux: 3 commits new 0e4a2c4e637 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new b8492c80ce4 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7cf8021a787 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 16e65e367c8 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 934a7196418 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 6762e0a33c7 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 014464cc383 123: onsuccess: #655: 1: Success after binutils: 22 commits new 45f44240a7a 124: onsuccess: #657: 1: Success after glibc: 2 commits new 30eb313a9a6 125: onsuccess: #658: 1: Success after linux: 3224 commits new c615e1986bf 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new a8680985cec 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 9667406af13 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new ead57ef19a3 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 52b6f289456 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f2d62813191 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new d34f9c4c6e5 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new bd59464471c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new b86ac82aad7 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new a7b538ae1b8 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 82aed5d51ab 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new a150d47c88d 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new c223f8106ae 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 653995a2765 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 3dcb4b4955a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 63b52a68c4d 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new f23760bd2dd 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 7164a729fac 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 51ea402a5c0 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 655b9d2eabf 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 9bfc3b1e386 146: onsuccess: #680: 1: Success after binutils: 20 commits new ef57c8dc050 147: onsuccess: #681: 1: Success after gcc: 6 commits new 470c49369a4 148: onsuccess: #683: 1: Success after glibc: 9 commits new bf7795ceb7e 149: onsuccess: #684: 1: Success after linux: 10 commits new 034e17dcadd 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new dc937b90672 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 12315bbe4ee 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new ec7b55e33ae 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 067c2bd8db8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new bca39e2c31f 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new d639cfc8c56 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 029451ba447 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 40cb2e4d5de 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 86a15886bbe 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new beec1efe94c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 09ce3e43c41 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 3c657b081bd 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 20740fcc725 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 30dc7df634c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 39acb3dbe1f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new de2e6708a0a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 00e4afd2463 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 891eff88efe 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 24192ffb6a5 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 412f2606478 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new ca97ab2a903 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new c3fec961a3f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new d66cbdc5a00 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new d65a4d46f6f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 95b9fb3ddf4 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new c282506435d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new f74b66445b8 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new ffd37ae4fb7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 33aba974c4a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 503fd8b5803 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 23b76df5ed6 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 1f7736b1c54 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new eac8f58e8a5 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 08c3ee7c4a5 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new c90c775f1bc 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new aa763cf2aac 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 3046a5270a9 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 9d93b8fa3e8 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new ce08332517c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 69d5db9e2fd 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 7460a826a6f 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new afbff676ac5 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 49c88743b8b 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 17729f16a1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d1f4bd5c1fb 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b298c881365 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 5d7a709f2a1 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 5835cfcce1c 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 95cf83f2a9e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 37cfa395c26 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a5f71ebef13 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new a8c9fba7964 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new adc4983f0fb 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new c5a720773da 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f49c804000e 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new fac3770cb6a 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new fc54861cbd5 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new af9cfa355a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 27c38271962 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new df2ed6d544d 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new a530a7807ea 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 7a432d64974 212: force: #24: 1: Success after binutils: 2 commits new c33ddc2dedf 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...]

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 (d23fc64eb8c) \ 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 -> 1948 bytes 02-prepare_abe/console.log.xz | Bin 3468 -> 3456 bytes 03-build_abe-binutils/console.log.xz | Bin 39052 -> 39456 bytes 04-build_abe-gcc/console.log.xz | Bin 204252 -> 204556 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 244500 -> 244016 bytes 08-build_abe-gdb/console.log.xz | Bin 39216 -> 39332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3808 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2200 -> 2608 bytes 11-check_regression/console.log.xz | Bin 3060 -> 4200 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 21 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 18 +- 11-check_regression/results.regressions | 19 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1085 ++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 21 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 19 + sumfiles/binutils.log.xz | Bin 62956 -> 62924 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83944 -> 83964 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122252 -> 122428 bytes sumfiles/ld.sum | 6 +- 39 files changed, 1239 insertions(+), 48 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh