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 1c60231cba7 213: force: #24: 1: Success after binutils: 2 commits discards ce0915780b1 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 829a1ad714a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 3c774a45276 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9d4297cbd4b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9fdb5af572e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards f89081a832b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 30f54119510 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 2bd2f54619a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards be1da56c667 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b2cf729781a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 43f43cbbd8c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 43445161685 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f2ea457fa3d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 41017edf370 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 86475f0715b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards de4c7a24815 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 103cd9f39df 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 72ef2d065e0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 668984a803d 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards b090748e5fa 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 59aef198d7c 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 556d5ff6377 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 54631dfd82b 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 7a7366b5ca0 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 4fb640db543 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards ecf970bb80c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 06db2aa8a05 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ea1e80e2085 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards eedab659d51 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 6660bfe9597 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 68cd9ae5641 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 8caf9aadb79 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 82199722aaf 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 5b9ecdfbfb4 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 7e9f1265c05 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards bc396fbf7e7 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5c37a259756 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 530d2fefee9 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 7146d1b147e 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4948a62836c 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 9c00a31a50a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 29664a9cd55 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards dd84a694a8e 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 842de85df1e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 981c3ce6f4a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards f119b31eaa6 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 82277251756 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 3f24fed0aa0 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 973582ae8c1 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 5b249d7b0f3 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards dc92098b11f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards fa1c1e13cdf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 39d0a5f354f 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 0bcde9bef5c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 75b9abb2a0e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 6293bc36ecc 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards ae879913a68 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 9864bf4ddaa 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards e561fe471fa 154: onsuccess: #583: 1: Success after linux: 10 commits discards bc4fb832b26 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 3465f4f1efc 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 824a37cdde6 151: onsuccess: #579: 1: Success after binutils: 21 commits discards cdd239c2758 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 36bf3d07048 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 4fdeb620ce6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 309d79396ce 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 0df7f27e42f 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards f5623edff3d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 90ff893db34 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 736a0c6a347 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 477469588bf 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 22cd64ba22c 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 84531b51c58 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards d8b987f265c 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 0c7622ce489 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards a1bb92b4b7e 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 006298c86ac 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 0ab9cddb219 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards b0ebc669ecc 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 0243dcaa98f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 77d1d168424 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards e95df942bc4 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards d2c057dff0b 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 55f291dfdf8 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards e0bb0abdf06 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 16a23d4c386 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 5344a87c34d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 9f5cc4edc2f 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards c0f4e2e8b56 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards fa1474f204d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 1c410ac3c33 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 101442b6358 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 7620d4a1e37 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 570ed5ac484 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 244da427af4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 9df08219cb4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 59ba16ed939 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 456e3c5858e 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 31dbe5e92a2 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards a60a59c2e4b 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 489c1f87253 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new ea342ddd214 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 4ee8720d752 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new a92792c063b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new f1eb43393cd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new c4badeaf942 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new f7ddb602295 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 904793d7a9f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new f2c342218ea 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new c321dd2c0c8 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 004388649d1 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 961b78401fb 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 2952fcdff02 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new a7cb2435edd 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 5e7d56d5537 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 128369d528a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 1234727f521 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 37cf70e584d 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new f77f68cf175 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new ae07401239c 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 51302d545e7 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 2a0d6082df1 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 6578acdebe4 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 353794cdce8 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new a443f22dce0 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 82f4222a1ad 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 98b13fb792f 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new bf4611290d0 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new fc72cb3c111 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 2740fa07580 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 47e82051645 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 30676abf8fa 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 16e0d7bcb35 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 500a97689a6 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 39e261533e0 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 94bfc2d4f23 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 395cf70564b 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 4e1afe0ec25 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new f3b66865b0c 151: onsuccess: #579: 1: Success after binutils: 21 commits new d95088bbf77 152: onsuccess: #580: 1: Success after gcc: 6 commits new 550528b0a5a 153: onsuccess: #582: 1: Success after glibc: 9 commits new 1471d58efc4 154: onsuccess: #583: 1: Success after linux: 10 commits new fd51c764f26 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 9438d301744 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 308df71f345 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new e5728e48c8f 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new b6501400aa3 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 6d58951f2e8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 4be0f164b5d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2d375995102 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 62ad635d5f4 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new e1463f3128d 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 75606f029e9 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new c7ca67689d1 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 71d8b0782ee 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new bb18e74b35d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 72bc8ded71c 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 9d0006c05cc 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 9563a61371e 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 57d2c601249 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new e69dd016b74 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 5020ffa2b49 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 004bc1d231a 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 73e224ea8ce 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 431a897acfb 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 22f3ce00f43 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5aa709b385b 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 28f418fdd05 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 4267c058191 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 5b683149c76 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 58b4c3f8a35 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 582d99699e8 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 12134530046 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new abfba539815 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 2b6d23080bd 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new fe84f13b1b3 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new adb7bc862d5 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new d890f15d433 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 70e01510e7f 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new c09621d0ba6 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 6193fca6b56 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 73dfcfd4a6b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new a732b1c06b0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 66c36ec06c9 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 0e929be06fd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ba9b1dfb9d0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new b8e82b6acbc 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2777b0f279b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2225bd9f11d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d86a83dbfa3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 63cde9b65f4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 1ba8acec937 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c596744c17f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6d0d9cecad5 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 6ae7d7de9e3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9b010554ede 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new a29fbbee12d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c3d186fa24d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 0cd82e1e28a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 002aaa7883b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new e4f7e5b92ed 213: force: #24: 1: Success after binutils: 2 commits new 778271b31d6 214: 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 (1c60231cba7) \ 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 1944 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 3440 -> 3480 bytes 03-build_abe-binutils/console.log.xz | Bin 52632 -> 54008 bytes 04-build_abe-gcc/console.log.xz | Bin 236672 -> 235796 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 235404 -> 235944 bytes 08-build_abe-gdb/console.log.xz | Bin 50456 -> 51628 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2196 -> 2604 bytes 11-check_regression/console.log.xz | Bin 3156 -> 4176 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 | 14 +- 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 62720 -> 62716 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100656 -> 100580 bytes sumfiles/gas.sum | 2 +- sumfiles/ld.log.xz | Bin 132024 -> 132412 bytes sumfiles/ld.sum | 5 +- 38 files changed, 1236 insertions(+), 44 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