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 2a7f489d3fe 116: onsuccess: #647: 1: Success after linux: 3 commits discards 51ce6a57f6e 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 264d921360a 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 9584436edb5 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards bfdcd83867b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 30d25ee04cb 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 71104bae473 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 05240d1deb4 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards d2da6af3744 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards f1962d7bc7f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 7e8792e9a08 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 14fe9f742d3 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 16f6449e2fe 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards c92583273c5 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 5bcd4a3b38b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards cdd4eed6d75 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 1d3315f99f8 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 36cd4b0f084 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 840bff1cd09 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 51dc16c10a6 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards d30ff9ed5fc 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 197e1322888 95: onsuccess: #619: 1: Success after binutils: 5 commits discards efe7a9391e7 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 44a379e276e 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 1c572805d7f 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards f9f4ab46395 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 3223ba057b6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 6ae9ce20312 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards e7a867a9424 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 35fd8f038b5 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 12fcc25a31d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards a22d680a058 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards c04200ab8f5 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 997843f0dbe 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 670e00e7147 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards f4178b41b04 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 52e69e77533 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards aa727093a39 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards e9ecb59dee7 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 78bce507493 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards bde70a15f11 76: onsuccess: #592: 1: Success after linux: 63 commits discards bed7054ac8e 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 924274486b8 74: onsuccess: #590: 1: Success after binutils: 16 commits discards b73097c8303 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 568b1080c37 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards f351cb51348 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards c8f788d5962 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 6e06e4b28e8 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 6f35245a9b9 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 746ea92d66b 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 72a1d9a3592 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 7356ea51a88 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 7f061c9a7ce 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 4efd3037147 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards ff6f95f857c 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 8ab371c1e1a 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 219f09203a4 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 133c8e8d13c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 45642447983 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 95c17cdbace 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 5e14bf34080 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 45628aa586a 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards e6dd8a6ff94 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards d433d7537f5 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 94eb9635333 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 8e816effba6 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 599f2c59e29 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards fd24e6f2f9c 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 0437c504e40 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 6e0398a773a 47: onsuccess: #556: 1: Success after binutils: 12 commits discards e43b4fe4b5a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards a39c0cffaed 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 4964bfe4de0 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards ea693fa6580 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 170a0b27675 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 0f45bab3a46 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 95ab006a4b2 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards ab1b8f6d3d9 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 0f5297ff0da 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 55a543066d7 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 82a7fcdd168 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards c8d964306ae 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 0cc936f0821 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 67cb632b6a6 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards a4636020e33 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards e099029be92 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 3765fce0542 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 949c7377388 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 206a9f40a26 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 5ffaf96bc9a 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 59d118c7465 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 41aad23346c 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 8044e352631 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 4904c7b31e3 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards d69c03f3250 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards fee1cfb9736 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0782d6b53de 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards eee71ebe917 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 70e12a2d59e 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c80a8f95f14 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards fb71445d08c 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3a3da7e0dea 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ac80ca1a40a 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new b3a01732fc2 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 50ddc046c7e 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a405f12ed22 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8d089a3d0e0 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 33894d87efd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 87bb0356122 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 1ce147be02d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new a46829bed9f 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 23d350b9cd9 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new ffe936898f9 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 17ce40050a2 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 76dfd7a1cfb 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 6cad727facb 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 08cc25b0b67 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new baa2fe92566 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 34cee96eb17 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new e4f5022159d 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 8dd4ea33cad 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 2e3cc5d451e 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 55bdf01ca17 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new d289e2c1771 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new cbe308f0232 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new f569c50bcca 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 78c2f7b61d2 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 74178a2a1e0 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 754fb96e1a0 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 545ba0c950e 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new fe4710fb634 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 6ce7c6f2aad 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new d47b1dd12b4 47: onsuccess: #556: 1: Success after binutils: 12 commits new 71a7133df50 48: onsuccess: #559: 1: Success after binutils: 6 commits new 35164cfbe54 49: onsuccess: #562: 1: Success after binutils: 9 commits new ce492384c68 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 61c2f139c07 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new e5559e4b2d8 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 0d3bc9ca2de 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 922c8f2c1b3 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new c8e76af0814 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new ea991861b22 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new a5e07122acc 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 6718013a9bf 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new d757dc729fd 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 4e9d40eead2 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 29440c392ac 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new a2c56bcf454 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new a80036e1b5b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new abc90e43ba0 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 2dd074d80e1 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new b640260ef57 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 07f26cceea7 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new cfa72c07fed 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 32d4c81d7e7 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new ea5b8b75846 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 70e5e1dda7a 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 253d703beeb 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 633dfad914a 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 010b0ba3fb4 74: onsuccess: #590: 1: Success after binutils: 16 commits new 3139c0ff110 75: onsuccess: #591: 1: Success after gcc: 25 commits new 2eccc29619f 76: onsuccess: #592: 1: Success after linux: 63 commits new ffa832739d0 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new cf547dbb0d4 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new a3d3b0089e6 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new efba6cb721c 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new a29739692e0 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new f642e645cc7 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 04705bd8ed9 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 14f67f1844e 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 385af151006 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new b066da6c34d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new f854a88c5b0 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 342873e9f7f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new edec0dcc8b7 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 8a14a868c10 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 4dc9e3c3874 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new b14d28b0c9b 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 63a229be6c8 93: onsuccess: #613: 1: Success after binutils: 19 commits new 35ce9177627 94: onsuccess: #616: 1: Success after binutils: 2 commits new 97967e3482c 95: onsuccess: #619: 1: Success after binutils: 5 commits new 34831ad9db0 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 474e43342cb 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new d2bd927dbc7 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 26c9996f138 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 8d21514dee5 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new aa5f4e275c9 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new c200a3ad0a1 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 28021c6ff53 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 16e72d2af5e 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 08c12b9770c 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 2741d1b9aac 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 8dd6ceb1c37 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 463982b9f89 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 37026280cd3 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9ae585592fc 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new a536973200c 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 372aabe61c3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 475b75565c3 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 3d1c6b1978c 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new b9efea2ebaf 115: onsuccess: #645: 1: Success after binutils: 27 commits new 425aa718a09 116: onsuccess: #647: 1: Success after linux: 3 commits new ebe682f1e4e 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...]
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 (2a7f489d3fe) \ 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 1664 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39232 -> 40060 bytes 04-build_abe-gcc/console.log.xz | Bin 214332 -> 215208 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 244104 -> 245244 bytes 08-build_abe-gdb/console.log.xz | Bin 39128 -> 39472 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2208 -> 2204 bytes 11-check_regression/console.log.xz | Bin 4576 -> 6268 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- 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 | 36 +-- sumfiles/binutils.log.xz | Bin 63128 -> 63104 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81772 -> 81788 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121704 -> 121748 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 408 insertions(+), 404 deletions(-)