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 c080d761f7 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 340a4c53dc 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 9302b6bec5 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards df5789f70d 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 5626579092 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 1c1a80f95d 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards bef36ec874 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards bbf7752d99 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 10474bbe1a 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 196e1c7940 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 9bddb0c7a0 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 1b1653998b 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 2c8fc44b52 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 5ff944b468 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 45a94e9650 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards a5046c0889 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards e040b4f72e 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 90bc9e1b3e 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 932b295415 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards c049589fbb 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 73de99aba6 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 13b95ad87b 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards a5bd7ffe1b 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 31c9929e9f 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 98ece758f8 212: force: #24: 1: Success after binutils: 2 commits discards a5f45cbb59 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8f0019c4c6 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 811b89577a 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 866c9edcca 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards bc8a2be263 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b2726c447c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 317fbc700a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 62b32b0202 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 2cbb211665 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards d9579300f0 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards c6e25aa6ce 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards afb6b0611a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 47a2fdfc2c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards bcacd35fe8 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b27e1506c1 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards d0baf564c9 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 636ba9f0ce 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 47b218c06e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 685f8fc2ed 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards fe17cebc27 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards eb53ba66ed 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards f573dc2b79 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 0a86654243 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 6394d3a57d 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 7cf44f2035 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 18e57d036a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards c6f923498a 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 8652142a6a 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards b9e487231e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 993cf8d74a 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 99e459642d 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 1b10154b72 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 251d91cfad 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 974ad2f935 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 94dc412c10 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards b30d2be1db 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 3070399db5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 3e1274eb2a 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards c10dd0e3df 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 5b6943146d 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards d65e0918d5 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards cda5cfb59b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 3b5c038135 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 26d9ca635d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 37e30c7b35 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards bf20a91352 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards b9bb0a14ef 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 9654234ec4 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 39ee74a07f 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 886711c380 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 632ba4f534 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards b23e3f8044 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards c23dab6e7d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards b2c469a1bb 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards df7cf33956 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 759057d2be 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 499bd50457 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards bdb6296152 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 232ae8acce 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 5d97ea730a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 486649266e 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards eac3faa33e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 0b2050186d 149: onsuccess: #684: 1: Success after linux: 10 commits discards 4ed1a0021c 148: onsuccess: #683: 1: Success after glibc: 9 commits discards deb4a257f8 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 2eef105e5f 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 70fe859fa2 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards ea64eb35db 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 0e973f11b9 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards c12d3ff642 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 6b9fe71de6 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 4c319ab127 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards f05f94eec8 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards a65327ce82 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards c06352fb3d 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards e1e1c152a3 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new b34cb0caf7 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 07563da0c1 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new be1f12251c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new fe014d3a5d 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new ca86dca35e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 24f2ee4a8a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 87270439b4 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 3c9d8ba120 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 6042daa425 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 905b6d7ac0 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 8167447ede 146: onsuccess: #680: 1: Success after binutils: 20 commits new d3b3d55c8e 147: onsuccess: #681: 1: Success after gcc: 6 commits new f24b26e492 148: onsuccess: #683: 1: Success after glibc: 9 commits new bc1d4a3224 149: onsuccess: #684: 1: Success after linux: 10 commits new 60be757728 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new f7d89a6181 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new fd73865c90 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 9b1cecda75 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 98e83ce646 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 00e9e153fb 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 400f27cc2b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 147df9c1e1 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new d692de8eb1 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 3ea0de44bb 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 265919ca78 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new e3130af25d 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 27a8786428 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 7d927e6c47 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 0dfe255d41 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new dd1a30cea1 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 1297e55ac9 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 7b3b3a3583 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 653baa1696 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 3d55ef9487 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 27de1f7264 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 6133710ec6 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new d1b225bc3c 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 43e4240afd 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 46bf4abded 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 1b791059d5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new b280853fc4 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 4c307114c8 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 59a7bbeb18 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new d007227315 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new f934b24eed 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 8e13ea9c37 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new fc26bd237a 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 4588b31493 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new e5a70c8cc1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 795e95c6e3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 75b65b402f 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 420e50a5ba 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 4c2496fc4f 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new e5edfff3c5 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new dbe46556ca 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 2dbd87e9b3 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 18437ddf22 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 293adaf642 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 69c000f9b8 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 9ddd511398 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 7fd56c999b 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new bcc2d6e981 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 6c5c7e219c 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 1ee8d9b4a5 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new a89264eebd 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 3eb9d01a68 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new ec3c3df5ac 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 51d28e781a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 96f9f116aa 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 2b10d4ab7f 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new b25cd886d4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new c5a6650567 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f0667b322f 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new bef5fc07c1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 83c9fdffab 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 8d8a1d7a28 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 4b34f7f971 212: force: #24: 1: Success after binutils: 2 commits new fc04355cf5 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new a3deecde31 214: onsuccess: #26: 1: Success after binutils: 12 commits new dc44d03275 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 07aacaa227 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 7ee7a55fb9 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new e8f2825433 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new aeb6f4fcd2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new f6ca78e8bb 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 641ad2237f 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 3ca8ddd844 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 8d06c30eca 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 6a9d9b26d0 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new c315a88445 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 529e9efb58 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new ab61398480 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 36c43a09e3 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new e36dad6d2b 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 6a9fe2d06c 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new a8ba507bc8 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 2004039a15 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new a55a38df90 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 50a86bf897 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 0301592aac 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new c04868c68c 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7b255f7e49 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (c080d761f7) \ 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 2228 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2584 bytes 03-build_abe-binutils/console.log.xz | Bin 35516 -> 35052 bytes 04-build_abe-gcc/console.log.xz | Bin 203716 -> 203304 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 241260 -> 240716 bytes 08-build_abe-gdb/console.log.xz | Bin 35168 -> 34652 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3852 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2712 -> 2180 bytes 11-check_regression/console.log.xz | Bin 1980 -> 1320 bytes 11-check_regression/results.compare | 8 ++-- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 44 ++++++++++----------- dashboard/dashboard-generate.sh | 17 -------- dashboard/dashboard-push.sh | 7 ---- .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 7 ---- jenkins/notify.sh | 2 +- {11-check_regression => mail}/results.compare | 8 ++-- manifest.sh | 36 ++++++++--------- sumfiles/binutils.log.xz | Bin 62896 -> 63144 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150736 -> 150608 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122648 -> 122620 bytes sumfiles/ld.sum | 4 +- 32 files changed, 61 insertions(+), 95 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100755 jenkins/dashboard-push.sh copy {11-check_regression => mail}/results.compare (61%)