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 57cebb4579 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards a1f806b33d 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards e9a2c777a1 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 8235ac3378 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards b007693540 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 61ec35df5e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 74458d5a1d 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 0f871b39ea 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards da6e35ead0 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards e651df759a 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 800cc70fec 94: onsuccess: #616: 1: Success after binutils: 2 commits discards ca512e03fa 93: onsuccess: #613: 1: Success after binutils: 19 commits discards a8c7922434 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 0b68a63262 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 1354fd1892 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 23a0291107 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards adf93d7817 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 73678dd649 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards a203957341 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards c5a4230a1c 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 8de09a1b16 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 8dda5b236f 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 892f42faa4 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 0701456153 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 75296f57a1 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards cad44fb08e 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards b17cf1af10 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 4ff151d39f 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 8b5c54241e 76: onsuccess: #592: 1: Success after linux: 63 commits discards 03b4fec9b2 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 3d891d1ba3 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 65bbefd3aa 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards a00e1a2793 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards ab92e9a4d2 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 18ed24b7da 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 1eb879a983 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards e986cc2991 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 5744943f59 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 6d9da6ffc1 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 9b734a9420 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 7f64f64d37 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 27ea9d77ce 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 012f2b2daa 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards e24e5be5b1 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards e5773f5e11 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 5985e8acdc 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards d414f76ba6 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 6a1c5eeb6e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 4e15d7e15b 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 55fd7ccb49 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards f0c31a575e 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards bce3dc48f7 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards cf735cf083 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 06b2b28bcc 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f8d4805a36 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 884a969d26 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 691cbe53db 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 1b31d8b188 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 042fe8e729 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 94871b57cf 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 56537364ad 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 5aabc5008a 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards e9f8f54f83 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards b32002ff19 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 113201b22c 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards a20fd37da4 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 88ceb6f45e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards e1b7eb8b54 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 327573ad60 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 9842d9d100 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 7dd7fe9681 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 0c079eacd6 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 4870319830 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards d51bbd1c6f 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards ed8dff5ced 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 72eb5f4760 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 5f5c68d87d 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 817b9eb462 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 73a1393b0c 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards b6d91fb851 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards 97d995c9b9 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards eaf10da73c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards df7ab6c1ee 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 1b2ce4b5f3 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0ac323fc75 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cb6cf57efc 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e136d7a7f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fa8746542f 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards acad074084 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ac9689552e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0fc9af2de 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2d2e46caf9 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aae27df3d6 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb61122244 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1692642e9a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 272ee9333b 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 245b4cb41f 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 096f3cd379 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 54fe62a24d 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6c5b27df65 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 83473d4eec 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new eb27ba2a1e 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new ba3b770cc3 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 05f23676cf 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a516678184 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 53d6614002 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f1db2eaabe 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e657710ebe 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d41448d887 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dfa742932e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a305d9e72c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5d542b38dd 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3026e3a6ea 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4dc70872da 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba4c1d36ba 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 713729ddee 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 701541441c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 42ecd80e15 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 462fc2c293 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dfe93fee3a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 681cec22b8 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new 35915a259b 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new a35ff0ec15 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 56efc80a8d 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new 70a5f91fdb 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 3a07679761 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new e4c5194063 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new 6d933123fa 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 657463ca96 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 6b16ef25ef 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new de4544ef59 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new f82d829990 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 0b0f1fde69 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 6579c26ce4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new ad6c7478db 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new f419f32e1e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 71bdf04d79 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new bb496652af 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 84cf1328e1 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new c20244a7e7 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 4235a020a4 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new cbc9a47c39 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new e201151150 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new a9c10f882b 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 3c00412a6b 47: onsuccess: #556: 1: Success after binutils: 12 commits new d31c626577 48: onsuccess: #559: 1: Success after binutils: 6 commits new 430b68cc7a 49: onsuccess: #562: 1: Success after binutils: 9 commits new 4c0d6a1a08 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new d02dca45d7 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 6c2d2cc8e0 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 9b6f16f12c 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 3e9a71b4ff 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 7f0aec5241 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 4149491b9f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new eb9379e2d8 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new eae0c4acb4 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 7e1001c3aa 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 44ad92b61c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new bcf42e9e95 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 0d780ac951 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 683db576e2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new e78e0f05a0 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 305e8f86b0 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 314b980b4b 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 6a1dd54ddc 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 85659fa1d2 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 0a890b43af 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 83b43ebf52 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 6f6f367959 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new aeb7fe86ed 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 5a8b033ef4 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 6e440540d0 74: onsuccess: #590: 1: Success after binutils: 16 commits new c5f58ddb30 75: onsuccess: #591: 1: Success after gcc: 25 commits new 4932f15bd9 76: onsuccess: #592: 1: Success after linux: 63 commits new 2dc869a773 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new aa9618a92d 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 6bf5fa0b56 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 085e42b1f2 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 27bdfc28ee 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new b541591641 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new c2e297d835 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 5367040edd 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new b661d10747 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 09fe88329d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new b281444793 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 4aa16f3cfa 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new a9934b0f27 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 9cbf28e1fd 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 831e8d4d31 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 91a0a716c8 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 9d5ef66892 93: onsuccess: #613: 1: Success after binutils: 19 commits new e6466b7f8c 94: onsuccess: #616: 1: Success after binutils: 2 commits new d285db7fb0 95: onsuccess: #619: 1: Success after binutils: 5 commits new b4d138268f 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new ba87223c81 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new b98db157b2 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 28f814fb1e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 9be99d420e 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new c5b37a0e4d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 6690efd542 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new d8c69f7259 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new e45fb08bae 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 4ff0572fd2 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...]

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 (57cebb4579) \ 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 1676 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 40192 -> 40156 bytes 04-build_abe-gcc/console.log.xz | Bin 214340 -> 214640 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 9512 bytes 07-build_abe-glibc/console.log.xz | Bin 243696 -> 243644 bytes 08-build_abe-gdb/console.log.xz | Bin 39516 -> 39608 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3856 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2584 -> 2612 bytes 11-check_regression/console.log.xz | Bin 5696 -> 5876 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 62884 -> 62952 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81776 -> 81728 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121752 -> 121712 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 391 insertions(+), 391 deletions(-)