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-arm in repository toolchain/ci/base-artifacts.
discards 778271b31d6 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards e4f7e5b92ed 213: force: #24: 1: Success after binutils: 2 commits discards 002aaa7883b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 0cd82e1e28a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c3d186fa24d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a29fbbee12d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9b010554ede 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 6ae7d7de9e3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6d0d9cecad5 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c596744c17f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1ba8acec937 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 63cde9b65f4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d86a83dbfa3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2225bd9f11d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 2777b0f279b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b8e82b6acbc 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ba9b1dfb9d0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0e929be06fd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 66c36ec06c9 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards a732b1c06b0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 73dfcfd4a6b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 6193fca6b56 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c09621d0ba6 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 70e01510e7f 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d890f15d433 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards adb7bc862d5 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards fe84f13b1b3 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 2b6d23080bd 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards abfba539815 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 12134530046 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 582d99699e8 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 58b4c3f8a35 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 5b683149c76 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 4267c058191 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 28f418fdd05 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 5aa709b385b 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 22f3ce00f43 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 431a897acfb 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 73e224ea8ce 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 004bc1d231a 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 5020ffa2b49 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards e69dd016b74 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 57d2c601249 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 9563a61371e 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 9d0006c05cc 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 72bc8ded71c 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards bb18e74b35d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 71d8b0782ee 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards c7ca67689d1 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 75606f029e9 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards e1463f3128d 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 62ad635d5f4 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 2d375995102 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 4be0f164b5d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 6d58951f2e8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards b6501400aa3 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards e5728e48c8f 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 308df71f345 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 9438d301744 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards fd51c764f26 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 1471d58efc4 154: onsuccess: #583: 1: Success after linux: 10 commits discards 550528b0a5a 153: onsuccess: #582: 1: Success after glibc: 9 commits discards d95088bbf77 152: onsuccess: #580: 1: Success after gcc: 6 commits discards f3b66865b0c 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 4e1afe0ec25 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 395cf70564b 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 94bfc2d4f23 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 39e261533e0 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 500a97689a6 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 16e0d7bcb35 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 30676abf8fa 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 47e82051645 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 2740fa07580 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards fc72cb3c111 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards bf4611290d0 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 98b13fb792f 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 82f4222a1ad 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards a443f22dce0 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 353794cdce8 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 6578acdebe4 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 2a0d6082df1 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 51302d545e7 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards ae07401239c 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards f77f68cf175 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 37cf70e584d 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 1234727f521 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 128369d528a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 5e7d56d5537 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards a7cb2435edd 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 2952fcdff02 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 961b78401fb 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 004388649d1 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards c321dd2c0c8 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards f2c342218ea 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 904793d7a9f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards f7ddb602295 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards c4badeaf942 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards f1eb43393cd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards a92792c063b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 4ee8720d752 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards ea342ddd214 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 9ef2967744e 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new f0b27a61235 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new b69d337474b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 22ec2f9f77a 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 83c9f9bc2dd 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 7abc67d593b 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 03d76f3dfd9 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new f8146583d82 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 04cde5c1ec2 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new f74b520db6d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new aca9b78895e 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 4f2fe64acd2 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 0fc52fc9255 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 5e09d813d6b 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 91b6d23e16e 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 7bfa42f7bcf 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new d8d5ca9fc57 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 74fb4c7653a 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 0972d8f5e3a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new e6b9ccf34e6 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new a02dc39def2 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 7fc51ec040c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 58274a2596a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new b915d0c2c41 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 491663f67ce 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 0ba57ba8788 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 0b91e7c02d4 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 2191bdf144e 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 56471ee1688 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new e8e879272a6 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new d84407029d2 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new df6d931941d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 8714612ccd6 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new aca15795230 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new f02845ca41d 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 7e038ecd2db 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 851c838b42d 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 5f75e912d1d 151: onsuccess: #579: 1: Success after binutils: 21 commits new 5a96e00948b 152: onsuccess: #580: 1: Success after gcc: 6 commits new 3df84144984 153: onsuccess: #582: 1: Success after glibc: 9 commits new 5b72e15bb6c 154: onsuccess: #583: 1: Success after linux: 10 commits new 137cfc14ca7 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new a5915d53343 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 1d3f145305c 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 3c421570302 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new cc709a6ec16 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 46a35d241ef 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 247dcd804ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2da0fc1bc95 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new afd793b198d 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new ccb14ec937b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 6903e8637b0 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 6aa31190835 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new b96775bda8b 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 1de5b175f8f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 917ac0027e0 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new e1ced45e800 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 68b31d131db 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new b3e4f747dea 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 3d5b48a2be1 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 351a0808805 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 634e12ea426 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 4e9e2279e2c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 25f000d1296 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new d0d615866a4 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new b416c9d6485 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 8fd78f1ce20 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d0c3c842179 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 6d05f31d4f7 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 6cd1e316041 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 20876accdcb 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 83f40fd5d56 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 31476480638 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e64a6612659 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 0079c36e9de 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 4a700141c83 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new f65075f8223 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 7426109c658 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 0f23256a651 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 78d6f11131d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 294629f7ed0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 73e5cd1f597 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a3615c56f5d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c4f785dec81 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c6a5d4ad501 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a183514316d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 6bb2022d469 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ed1ebe6a7fa 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 9c9b7800dcd 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 528fc877fd7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e66c4826668 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b283c83f75d 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 545578df10e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 37cc33591e8 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 7ae74c59eee 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new e1e0b01587a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new d61ab31e85f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b8462ed2579 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 69c01450d84 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 102cd60dc5c 213: force: #24: 1: Success after binutils: 2 commits new 107675619f7 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new ada0739fa87 215: onsuccess: #26: 1: Success after binutils: 10 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 (778271b31d6) \ 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 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 3480 -> 3432 bytes 03-build_abe-binutils/console.log.xz | Bin 54008 -> 53440 bytes 04-build_abe-gcc/console.log.xz | Bin 235796 -> 237816 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 235944 -> 235916 bytes 08-build_abe-gdb/console.log.xz | Bin 51628 -> 50624 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3764 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2604 -> 2520 bytes 11-check_regression/console.log.xz | Bin 4176 -> 3584 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 | 20 +- 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 | 66 +- 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 | 16 +- results | 19 - sumfiles/binutils.log.xz | Bin 62716 -> 62612 bytes sumfiles/binutils.sum | 62 +- sumfiles/gas.log.xz | Bin 100580 -> 100572 bytes sumfiles/gas.sum | 274 +++---- sumfiles/ld.log.xz | Bin 132412 -> 132192 bytes sumfiles/ld.sum | 344 ++++----- 40 files changed, 473 insertions(+), 1581 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