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 7ee9a3327ca 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 94d1cf1751c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards b2459ecf987 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 15d3b8388f7 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 9cec68b0f56 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 253ef55e994 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 0c8825270c9 213: force: #24: 1: Success after binutils: 2 commits discards bcc3ebb2840 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards b98453cb6c1 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 0dc35883ac9 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3942cbb69ea 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards e1557bc3df9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 9b845c9487c 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6734bb95020 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards b0e882f612a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8eff86aa7eb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 65d40270dc2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 10f224869f3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e66160b9f73 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards fe010a8dd99 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards cd308924241 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 00b0b2fa0ed 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ce12635b717 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 148497f309f 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ea16e9c2fa1 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 3317461770f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 81c35200949 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1d1c56f06c2 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 2a397ab6aa8 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards e4c567ed963 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards de74722c9f9 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 3dfdeeee854 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 76472cd63f6 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 46595f27a40 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 5806c4bb590 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 2f03bfd6935 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 928729b879d 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 9e8f3e8b216 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 2affe4d7277 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 20452baad4a 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards d62e26a665f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards f7b9b80a53b 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards fc816e74249 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards a382bec921f 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 0d1cc2bff6f 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards c675be56c88 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards ece146bb350 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 482b34dfc99 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards a501b01ec3e 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 727000d8d44 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards d745abe7cf5 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards b9eded0a5c5 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards d9c2f9b46a3 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards fb6a826ed0c 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards d767efc7bce 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 12a1b13f3ee 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards da2077f97fa 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards d9c3bff9ba2 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards d681812ed41 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards d906d5c98ca 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 193133d43dd 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 91f5bc9708c 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 893879d83ef 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 7aeae383333 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards c77c95cd6bf 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 2a5f4682567 154: onsuccess: #583: 1: Success after linux: 10 commits discards c5ea03e72ff 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 629af60772f 152: onsuccess: #580: 1: Success after gcc: 6 commits discards c279e8e82b3 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 71bc66a48bf 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 4a28cb3c676 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards d13b7af2aeb 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 3648e4c28cc 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 3ce7a051e19 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 574a73c06c4 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 370de1dbac3 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 80e09b26c91 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards dc72353725f 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards ca5e26726e1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards b0d83cce7e7 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards f4e0fd6588d 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 2d0e8b0dda1 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards f284e8212bf 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 7de4cff5d1a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards bb49ecffe2b 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 3a6edd5e8db 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 92df6b47e47 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards af0c58c575a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards a693542a3cb 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 49cfe0467cc 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 2b732399a69 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards c493d9f37f5 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 624c8bc5f17 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 572553a4458 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards d9426d247cd 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 8919be91ed0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 05b5646fbdf 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 7c66f9bac7d 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 4b562fae509 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards dfb71afeb40 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards fe2c886ad0a 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new c849a67d4e2 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new b7b62dd5d5e 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 4ffb2be97e6 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 85e7f697c56 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new ed8d1da03d2 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new edf59bcf651 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 2d05f78a405 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 91ffa78a1cf 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 328997a140d 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new fba5e64cc08 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 1f6a4ef5c91 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new b2538309f2c 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 956fc34c3a7 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new af3d10770df 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 772e739808e 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 1823ac0303b 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new b50074c102f 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 19f7d4fddb4 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 32b78650eb4 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new e3c4b7f7a13 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 77ae5298abe 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new cb8ae68a229 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 23fb90bdd95 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 5e98f06c981 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new a324c47be2e 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new bc52bdb4983 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 8dd443b7b1c 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new fab6f89a24c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 0a774dea3d6 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new db3a8bbeb1c 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 58acc769a51 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 22f56c0f4c0 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new b70060d22be 151: onsuccess: #579: 1: Success after binutils: 21 commits new f18c1894c73 152: onsuccess: #580: 1: Success after gcc: 6 commits new bb654d87fe5 153: onsuccess: #582: 1: Success after glibc: 9 commits new 5edc4286c14 154: onsuccess: #583: 1: Success after linux: 10 commits new 9741ab17941 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 350367260fd 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new fe3245147d1 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 32a60949e52 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 22b1b0fc74c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 51ff1e5782d 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new e2bc30e6a26 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 51535904b58 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new f621ed4116b 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 498a3d60cbc 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 46f69b44ca8 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 39258e7ddbd 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 8d9fbfc5eca 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new df33525f137 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new b318909991c 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 7832813ac60 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new ad6e1bbb36a 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 6e604ea5e8e 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 07329c91743 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 72b0119b17f 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new e1126f9be33 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new fc0d8a4f4fa 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new f75c37a389a 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 58c3ff28120 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new e31dbc14b9d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 73f493707b1 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 1b75dcd2cfb 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new a0edbd46168 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 576fa6f6ae0 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new e8fc1f7704b 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 16036efe96d 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new b29016289e1 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 6eadc3369c9 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 8e721997e46 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 326f40ba369 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new f331e3a885c 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 53290243fba 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new d956a2cc979 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 7abbe9eb2bb 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4798038042d 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 54cad39ecdc 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 254fbd0fc30 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 8daa809756d 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 826c4811bbe 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 5151cff71b3 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new d4752bfb514 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new db514ee4947 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e828a721606 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e89f3127948 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 796792e5254 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new dc62a80db41 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ac1e8f3aad4 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 4998c59bcc7 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d82841e4559 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new eba14bddf77 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3e3987c864e 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new d1c7b9b3212 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new f11c92bed5d 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 9784e6a2fb1 213: force: #24: 1: Success after binutils: 2 commits new ad1b894a194 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 1d6d1b054c0 215: onsuccess: #26: 1: Success after binutils: 10 commits new b04a7e25834 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 63949803cca 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new e9b3fd7136a 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 679065f07e3 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 847a86460e5 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...]
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 (7ee9a3327ca) \ 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 1744 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 48496 -> 49592 bytes 04-build_abe-gcc/console.log.xz | Bin 235160 -> 236912 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8404 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 233480 -> 233260 bytes 08-build_abe-gdb/console.log.xz | Bin 47432 -> 48024 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2696 bytes 11-check_regression/console.log.xz | Bin 4752 -> 5024 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++-------------- sumfiles/binutils.log.xz | Bin 62852 -> 62472 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100640 -> 100612 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132192 -> 132268 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 60 insertions(+), 60 deletions(-)