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 c33ddc2dedf 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 7a432d64974 212: force: #24: 1: Success after binutils: 2 commits discards a530a7807ea 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards df2ed6d544d 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 27c38271962 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards af9cfa355a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards fc54861cbd5 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards fac3770cb6a 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f49c804000e 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c5a720773da 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards adc4983f0fb 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a8c9fba7964 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a5f71ebef13 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 37cfa395c26 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 95cf83f2a9e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 5835cfcce1c 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 5d7a709f2a1 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards b298c881365 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d1f4bd5c1fb 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 17729f16a1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 49c88743b8b 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards afbff676ac5 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 7460a826a6f 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 69d5db9e2fd 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards ce08332517c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 9d93b8fa3e8 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 3046a5270a9 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards aa763cf2aac 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards c90c775f1bc 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 08c3ee7c4a5 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards eac8f58e8a5 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 1f7736b1c54 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 23b76df5ed6 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 503fd8b5803 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 33aba974c4a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards ffd37ae4fb7 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards f74b66445b8 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards c282506435d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 95b9fb3ddf4 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards d65a4d46f6f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards d66cbdc5a00 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards c3fec961a3f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards ca97ab2a903 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 412f2606478 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 24192ffb6a5 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 891eff88efe 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 00e4afd2463 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards de2e6708a0a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 39acb3dbe1f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 30dc7df634c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 20740fcc725 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 3c657b081bd 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 09ce3e43c41 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards beec1efe94c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 86a15886bbe 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 40cb2e4d5de 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 029451ba447 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards d639cfc8c56 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards bca39e2c31f 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 067c2bd8db8 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards ec7b55e33ae 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 12315bbe4ee 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards dc937b90672 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 034e17dcadd 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards bf7795ceb7e 149: onsuccess: #684: 1: Success after linux: 10 commits discards 470c49369a4 148: onsuccess: #683: 1: Success after glibc: 9 commits discards ef57c8dc050 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 9bfc3b1e386 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 655b9d2eabf 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 51ea402a5c0 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 7164a729fac 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards f23760bd2dd 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 63b52a68c4d 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 3dcb4b4955a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 653995a2765 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards c223f8106ae 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards a150d47c88d 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 82aed5d51ab 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards a7b538ae1b8 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards b86ac82aad7 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards bd59464471c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards d34f9c4c6e5 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards f2d62813191 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 52b6f289456 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards ead57ef19a3 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9667406af13 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards a8680985cec 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards c615e1986bf 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 30eb313a9a6 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 45f44240a7a 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 014464cc383 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 6762e0a33c7 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 934a7196418 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 16e65e367c8 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7cf8021a787 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b8492c80ce4 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 0e4a2c4e637 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 6538cc53b38 116: onsuccess: #647: 1: Success after linux: 3 commits discards d3df69e9481 115: onsuccess: #645: 1: Success after binutils: 27 commits discards ebe01a38def 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards d78616a09f8 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9a82961b270 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 90e3e1bca60 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new f36c41967a8 115: onsuccess: #645: 1: Success after binutils: 27 commits new 9a76600bffe 116: onsuccess: #647: 1: Success after linux: 3 commits new a0c178f20cc 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new a6dda4a5edf 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 4aed62677a9 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new dc7c60a85d0 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new bbb78ad2b9b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new db82c4e0beb 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 2c17786d4a5 123: onsuccess: #655: 1: Success after binutils: 22 commits new 5e0d4912681 124: onsuccess: #657: 1: Success after glibc: 2 commits new 2514ca68eba 125: onsuccess: #658: 1: Success after linux: 3224 commits new f887834bf07 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new e5bcf0caa2d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4f4045c3234 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 70314b7896f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a4fdf8810db 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 02a3d0c6347 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 1709654920d 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new c95d71d0cea 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 09883fd08ca 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new c126d951bf1 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new b502bb4a675 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 5a4c0426760 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 2a220907f78 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 73c586ab2b9 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 8917d998c9c 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 3d6808ef56f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new efde725deef 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new f942ee68ffb 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new c8624b7c189 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 0939ce19f13 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 37362cddc4e 146: onsuccess: #680: 1: Success after binutils: 20 commits new 24ff4229145 147: onsuccess: #681: 1: Success after gcc: 6 commits new d13c53793ca 148: onsuccess: #683: 1: Success after glibc: 9 commits new 6de25999706 149: onsuccess: #684: 1: Success after linux: 10 commits new 025066de901 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new c4eecca5a25 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 9df74fae9e3 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 241db191392 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 98a5fdb37ca 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 840875f9ed1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new aa28f4e6df3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 2d29cfd88e8 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 80e5a0e3519 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 92a4d3d72d5 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new ebb4cb9ecb1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 6472f74f6a4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 68818eb0709 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 0c828908b6e 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new e0c417c45fc 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new b1f45623c67 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new c7cb3d6ba68 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 8d574b66c43 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 61adeb07a58 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 2fbb1a5dbb1 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 50533a902bf 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new df09fd47fb7 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 999a2b828cf 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 5f1ae993473 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 4123f8b6d89 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 7054587238f 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 96609513715 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 51586a0e3fd 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new edcfba747d2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 92e35330638 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 3446a2c0d56 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new db641d84680 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new b8db38d209e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 711b42693eb 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new be9483c5644 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 1c901da95e3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 6f4557cc609 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 87cd0daf3d5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 08b7881805e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new cbf164bb953 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 2ad0b45ad72 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 78dc008778b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5011984f696 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new c10ad2513d4 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 0e1bc8cdb21 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ebc2e4101e1 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 84338d1f2f9 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 98116901bd4 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 01c82984de5 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2a66b34169c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new fc0a01f06c7 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0545660e7c3 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 62af3970cc6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4990dba3071 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 1dfc5763c8a 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 25ceb198cb0 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 98480832c40 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 02e6c41e4e9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b59bf7e7fb2 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 4655373d4ea 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 595626e4046 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 422a8110028 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 029e4c50123 212: force: #24: 1: Success after binutils: 2 commits new 51397ec318e 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 10af7021706 214: onsuccess: #26: 1: Success after binutils: 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 (c33ddc2dedf) \ 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 1948 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 3456 -> 3448 bytes 03-build_abe-binutils/console.log.xz | Bin 39456 -> 39312 bytes 04-build_abe-gcc/console.log.xz | Bin 204556 -> 203992 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 244016 -> 243896 bytes 08-build_abe-gdb/console.log.xz | Bin 39332 -> 38992 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3784 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2608 -> 2652 bytes 11-check_regression/console.log.xz | Bin 4200 -> 3592 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 | 36 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 45 +- 11-check_regression/results.regressions | 19 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 42 +- 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 | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 19 - sumfiles/binutils.log.xz | Bin 62924 -> 62888 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83964 -> 83976 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122428 -> 122464 bytes sumfiles/ld.sum | 4 +- 40 files changed, 124 insertions(+), 1232 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh