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 df57771967 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards a8b36e9814 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 7305931ef5 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 9e605882f1 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards e1b746ce6a 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 97ce56beb6 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 60f9fe45ca 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 9b46f00631 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d645b91540 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 1053ad72b7 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards e2b3e17e1f 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 20df257d7e 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 99f6305616 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 65500b959c 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 6c711400ef 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 98bcd0c3c6 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 06b665f956 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 458246c486 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards ce7cb08b60 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 9576a4f406 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards cd6184fde7 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 7e558a28c9 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards f9ea9da409 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards f3e49094c8 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 83a8b322a6 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards f4fe86de56 76: onsuccess: #592: 1: Success after linux: 63 commits discards b7373e6b3d 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 26d63e6ee0 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 0750f3bd34 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 7d6d724951 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 967fa966a9 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards fe11e168ce 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards e8da90c28e 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 65c519cb6e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 13176a1569 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 2e876e0f32 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 58f479ba07 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 8f6f9dc083 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 6ec9e5a1c6 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards e23bc62a0a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards dea6843660 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards d83599329c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 3541873df7 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 6e9b2571ce 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 6bc12022b4 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 8dcee6bb15 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards aa308c8913 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 07bb4843b2 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards b4f1a59787 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 08809b16a6 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 58e5f683c1 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 3beb4feae7 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 6d812b2c0f 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 25c9aadfd0 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 36074cac73 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 0b6631de7a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards b7381749a3 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 0ba068fb31 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 745b0af47d 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards a1d3ccb458 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 5a55ac10de 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 659d45b2b3 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 5df39a455f 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 2cae0b4b1a 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards d2e94d020a 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 4b52554b64 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards afa892fbbd 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 915346ab55 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 91d0f1b9dc 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 738e2597e9 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards d7b08a20f5 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 29d13a69a5 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 276dd7616d 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 4ddfe0f28f 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards f22cd56c91 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 490aaa50e3 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards f8e48104c0 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards 0fa8c762e6 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards 63096f706d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards 3fa3f3351f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 60f18181fa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8af5356766 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bfa8f36b64 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4dc3d33888 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 95d6e916eb 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6ffeeb82e0 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 08d4f4a8f0 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards af2372a858 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 98121e56e0 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0fd425922a 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ac796165bc 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f41c8abb0 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 961ce662ac 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8bd6a81d86 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c2b69595a4 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 10424af18a 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 068fcee0e6 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 0e8cf091da 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c083b558ed 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d07800b998 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 63754f1afe 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e49bebbffc 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 7f638d3a77 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d0e413dfc5 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9a8de9c48a 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 335e7c3ec3 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9253f724bc 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 50655bd5f0 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6a71efe271 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cb9010220f 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fec9845c23 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2c17778b74 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8345814ffe 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f7ddfd4c49 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0b2b2cac8c 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c0deeb5d4b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 436566e296 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d90b474c79 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new daefe1a934 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4f4920666a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b5646e8d4 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9957545f44 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc58820df5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new a9b13f9f44 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new c6422a530a 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new b215837773 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 0f835639d6 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new b34691675b 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 6d1eff5359 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new efbe49d483 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new 1fc418fea6 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 8a75dd94c3 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new b0061d35c8 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 96b9d3be82 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 227231a39e 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 2369d46922 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new e29d0b2e50 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 926ac9368a 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 205116c43d 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 2197bcf65c 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 05b3fbe122 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new f87f776625 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 41efbe001e 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 064576b7b8 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new c43fb44504 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 14075c3507 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 886b8ee54c 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 57c182917a 47: onsuccess: #556: 1: Success after binutils: 12 commits new d19a5c9f7c 48: onsuccess: #559: 1: Success after binutils: 6 commits new 99991d1547 49: onsuccess: #562: 1: Success after binutils: 9 commits new f391c7989a 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new d832b2e104 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 306b0c874a 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 850b02b59d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new cd268b8ad0 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new bd2c5e62cb 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 9af322dd39 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 1a313a6d40 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new c0899d32dc 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 16194bb3e8 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 6d62cb2800 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new e880a7e5c7 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new b6c9a605a4 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 3f53b72e10 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 3f5556157d 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new e9544a1c22 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 7b540efc6f 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 7c198f5204 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 7141d617e6 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 2d25ede6de 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new b65bab8622 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new d0d53fb814 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 60c34c102a 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 49a9f2f4ee 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new c8f01d5d79 74: onsuccess: #590: 1: Success after binutils: 16 commits new 5ea6169622 75: onsuccess: #591: 1: Success after gcc: 25 commits new 0ad89df881 76: onsuccess: #592: 1: Success after linux: 63 commits new 03edd8b955 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new be530134b5 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new f44ec25634 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 457ac9e0bb 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 20ba89b613 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 543bceafaa 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 3a256b7094 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new a4365af0ed 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 81badb58bd 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new d5d0bc95d7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new e2e14b7e61 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new d3c572f145 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new ca33632651 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new baf9eb5fab 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new beec4d7d9a 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 8cfb8c78b5 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 40b1d86ff4 93: onsuccess: #613: 1: Success after binutils: 19 commits new dadbd01bc9 94: onsuccess: #616: 1: Success after binutils: 2 commits new a218e2f1b7 95: onsuccess: #619: 1: Success after binutils: 5 commits new 23c3ada1ac 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 301c9129e3 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 32295d4344 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 441a25a631 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 57101497f9 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new bd8f491d1d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 7bb8453b5c 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/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 (df57771967) \ 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 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39888 -> 39436 bytes 04-build_abe-gcc/console.log.xz | Bin 215648 -> 213644 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8292 -> 8408 bytes 07-build_abe-glibc/console.log.xz | Bin 244148 -> 244480 bytes 08-build_abe-gdb/console.log.xz | Bin 39180 -> 39184 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3844 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2196 -> 2184 bytes 11-check_regression/console.log.xz | Bin 5760 -> 5648 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 36 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_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 63084 -> 63192 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81776 -> 81712 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 121684 -> 121692 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 389 insertions(+), 389 deletions(-)