This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts.

discards 670ca7fcac 505: onsuccess: #52: 7: [TCWG CI] Success after binutils/gcc [...] discards 71c6fb2e14 504: onsuccess: #51: 7: [TCWG CI] Success after binutils/gcc [...] discards 62fe1d77e9 503: onsuccess: #50: 7: [TCWG CI] Success after binutils/gcc [...] discards f500b6d214 502: onsuccess: #49: 7: [TCWG CI] Success after binutils/gcc [...] discards 15ea11f625 501: onsuccess: #47: 7: [TCWG CI] Success after binutils/gcc [...] discards fe9cb54856 500: onsuccess: #46: 7: [TCWG CI] Success after binutils/gcc [...] discards 97e3db68cb 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/gcc [...] discards 82e7b2e26e 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/gcc [...] discards 45fd5cd358 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/gcc [...] discards 2ae00e455d 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/gcc [...] discards 041ffcfbef 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/gcc [...] discards 3d63dc0c0b 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/gcc [...] discards 59a43f6957 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/gcc [...] discards e3dc27110a 492: onsuccess: #37: 7: Success after binutils/gcc/linux/gli [...] discards 1268a371c2 491: onsuccess: #35: 7: Success after binutils/gcc/linux/gdb [...] discards 979233a4af 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gdb [...] discards 23ca5cf1b6 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gdb [...] discards 7168d040d9 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gli [...] discards 3bf7cc8aeb 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gdb [...] discards 37a9656c85 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gdb [...] discards 21d791e14f 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gdb [...] discards 367513ce31 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gdb [...] discards 4e541ee3cb 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gdb [...] discards 45958b9fc3 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gdb [...] discards d6697c4ff1 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gli [...] discards 7a831852b8 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gli [...] discards dc9e81e368 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gdb [...] discards cdf6a847b1 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gdb [...] discards 27aa7628a9 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gli [...] discards 9abcec7ad1 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gdb [...] discards 81d1438dee 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gli [...] discards bc3580f45d 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gli [...] discards 60d1c4906f 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gli [...] discards e58233d7c4 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gdb [...] discards 449e815d04 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gdb [...] discards 567df7f6ec 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gdb [...] discards 31105e3f1a 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gli [...] discards 13224d064f 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gli [...] discards ed85880519 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gli [...] discards 61d99cb9cb 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gli [...] discards d1863f63b0 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb: [...] discards 979c303d2a 464: onsuccess: #8: 7: Success after binutils/gcc/linux/glib [...] discards d4619d4659 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits discards d049609bf6 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits discards d68cc43f98 461: onsuccess: #5: 7: Success after binutils/gcc/linux/glib [...] discards c362141725 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits discards 05bd324f9f 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] discards a324919526 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits discards 60ff67215c 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] discards 29624f5ead 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] discards 00b52b6061 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] discards c1eff0a922 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] discards 4c122b9141 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] discards a6f9f0c11c 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] discards 42bd69e173 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] discards 8eb75e5d1c 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] discards cb3629ed78 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] discards ac72c1bebe 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] discards d427d18668 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] discards e5bc02a167 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] discards 36d85ae223 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] discards d80527fb16 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] discards b4c7df4349 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards 9de2ea5cfc 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] discards a37373ed9e 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] discards 8ac6c81af2 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits discards 465a377c60 439: onsuccess: #2176: 7: Success after linux: 11 commits discards 68adcbed8c 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards d28307e4ba 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards 76d86c3f99 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] discards 656d85e92f 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] discards 715bb0c089 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards 5148f7e219 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] discards 925416293e 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] discards 98d1461b9e 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] discards b721487c9f 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] discards 2968b77006 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] discards d768ba96c3 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] discards 095916e11f 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards 9f4accfbf4 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] discards 8624b906d9 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] discards c325df45f6 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] discards 1748b2f711 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits discards d8439fbe71 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] discards a747c7f847 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] discards 1199d0f325 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] discards a9a60b582d 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits discards 5b807dade6 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] discards 396cd84716 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards 067dc23f34 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards 8e0daab3e9 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards 309babbbe3 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards 99806cdf98 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards 5a5da28044 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards 8601856d30 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 48e53e7390 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards 5d56bc8a84 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards f18405834f 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] discards 72ae015a2c 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] discards 10400081e2 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards a67f729421 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new 3a761bf464 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new 580e65541e 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new d21713913b 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new e3ac5ff205 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] new 1d911df748 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 9fdb4f24dc 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new e3d935dbf8 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new 68ce904e95 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new 09e49bfdf5 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new ef60e5bc8a 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new ef2565d83d 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new 7a72bae5ff 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 589fef9d21 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 240ddfb3f4 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] new e294dd7d64 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits new 7c17bec950 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] new 3c2a26790e 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] new eecf9f8814 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] new 4491d4a940 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits new 1f7b691354 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] new 19bc535a10 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] new a35b1653a6 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] new 0a83ace104 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new 6a3fa6e707 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] new 2a55131131 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] new 2a63b50615 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] new 7fa6b40fae 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] new 97292c02aa 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] new 52ad84d361 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] new 8144c8a7b0 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new fe57e20dca 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] new d1674e8d23 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] new dbe160a857 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new f5dbda06a9 438: onsuccess: #2175: 7: Success after gcc: 7 commits new 43a5737e18 439: onsuccess: #2176: 7: Success after linux: 11 commits new 70af81e383 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits new b1c86a6644 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] new c3644022e3 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] new 3acc566b3e 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new 4cc952ddb1 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] new 380e3d70df 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] new 9b8d1893b0 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] new 02a7dd23f7 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] new 2d0c50daf9 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] new bca98baecc 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] new d86385f990 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] new 0939c87ade 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] new a4e30ae01f 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] new d614a0b731 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] new 4c8ae53a6f 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] new 0d7aa1eabd 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] new 8256fc7172 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] new 0072481b61 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] new 8c06576871 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits new 700915c78c 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] new 9700cd4d11 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits new 90aa031883 461: onsuccess: #5: 7: Success after binutils/gcc/linux/glib [...] new 1a65dd16e4 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits new aefd4c8cab 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits new 00360a7804 464: onsuccess: #8: 7: Success after binutils/gcc/linux/glib [...] new 412a9ddbcd 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb: [...] new 502c3ae36d 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gli [...] new 6c72f2243c 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gli [...] new f44ec250f9 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gli [...] new ee267022fd 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gli [...] new 198a376895 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gdb [...] new 45e49961a4 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gdb [...] new 52bc819b69 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gdb [...] new e8cea367b0 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gli [...] new 4c56a6116b 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gli [...] new 607e4d87ef 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gli [...] new 6bfcd2d989 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gdb [...] new 586cd143fe 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gli [...] new 50004d9266 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gdb [...] new c956554d82 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gdb [...] new a1bfcbd322 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gli [...] new 022f307ef6 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gli [...] new 91b174b79b 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gdb [...] new a3ea120914 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gdb [...] new 97344b30a4 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gdb [...] new 8817d580e7 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gdb [...] new 087e2e0038 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gdb [...] new 3d8338da22 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gdb [...] new e447188a14 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gli [...] new c63d1d8293 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gdb [...] new b6ddad58fa 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gdb [...] new 7bcf4e9bb6 491: onsuccess: #35: 7: Success after binutils/gcc/linux/gdb [...] new 5f16a12e17 492: onsuccess: #37: 7: Success after binutils/gcc/linux/gli [...] new 1c1c357ae3 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/gcc [...] new 2db048f390 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/gcc [...] new db4efe6c14 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/gcc [...] new dd2f1df9cc 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/gcc [...] new 689e44185c 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/gcc [...] new 272a24b89f 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/gcc [...] new 5193201dcd 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/gcc [...] new 0f79edc294 500: onsuccess: #46: 7: [TCWG CI] Success after binutils/gcc [...] new a9a1d5536d 501: onsuccess: #47: 7: [TCWG CI] Success after binutils/gcc [...] new 0b00a6e990 502: onsuccess: #49: 7: [TCWG CI] Success after binutils/gcc [...] new 224237ef1f 503: onsuccess: #50: 7: [TCWG CI] Success after binutils/gcc [...] new c4fb2c6cce 504: onsuccess: #51: 7: [TCWG CI] Success after binutils/gcc [...] new 07b5d17b4d 505: onsuccess: #52: 7: [TCWG CI] Success after binutils/gcc [...] new 328c19351f 506: onsuccess: #53: 7: [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 (670ca7fcac) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]

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 2072 -> 2100 bytes 02-prepare_abe/console.log.xz | Bin 2544 -> 2544 bytes 04-build_abe-binutils/console.log.xz | Bin 26984 -> 26960 bytes 05-build_abe-stage1/console.log.xz | Bin 89128 -> 89216 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8888 -> 8612 bytes 08-build_abe-glibc/console.log.xz | Bin 233560 -> 232340 bytes 09-build_abe-stage2/console.log.xz | Bin 225340 -> 225320 bytes 10-build_abe-gdb/console.log.xz | Bin 34432 -> 34392 bytes 11-build_abe-qemu/console.log.xz | Bin 31904 -> 31532 bytes 12-check_regression/console.log.xz | Bin 4880 -> 1296 bytes 13-update_baseline/console.log | 44 +++++++++++++++--------------- 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 +- git/qemu_rev | 2 +- jenkins/notify.sh | 3 +++ mail/changes-list-long.txt | 32 ---------------------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 41 ---------------------------- mail/short-diag.txt | 1 - manifest.sh | 50 ++++++++++++++++++----------------- 26 files changed, 59 insertions(+), 128 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt