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 9bda320d068 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 6e50e49e767 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards ec8f1b228b6 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards ceb5d3eab59 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 1e1c2d20ce4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 1fb0f4fd419 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 3f295bcf3b4 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 20d23a664c7 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 8b39d89042a 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 6f3ea872d5c 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards d64f6822f85 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards b304eee0e72 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 1880152e978 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 6c7e791ccb8 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 00d77ef3b0d 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 1e934dbee64 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 88cd6fa6bea 95: onsuccess: #619: 1: Success after binutils: 5 commits discards e34c04d550b 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d2420ebcc06 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 27ade6b303f 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 1b427f3680b 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards e02f4dc37a6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 8bea2b753f0 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards f26276cc38e 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards ab773c50ffd 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 490b29612b8 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards c441ed542e0 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 7e9437ae4b8 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards f58655c7caa 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards e5bc8e15271 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 0d542d97d78 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 5d98573c29d 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 19a4ef14468 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 8cd22419b98 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 44c69a79b20 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 33ca4209d62 76: onsuccess: #592: 1: Success after linux: 63 commits discards 1617aa27c09 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 136d6071547 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 63ceea6a67c 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 44861170d15 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 470beabe7e6 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 18bc1bc596c 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 85240dcc824 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 638ac7bb139 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards e9f980bf174 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards f92d9163804 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 3b2da97be16 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 04cb305ca9c 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 1895f1fbfc2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards a0b20dbab29 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 0e4ed430610 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 682167cff2e 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 49dfc30fcbd 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 556f2145448 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards b7517b130ca 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards ed8485898ef 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards d8b50f816df 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 4adecfa508e 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 590052979be 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 0864933e204 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 52d62839c6a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 596b5f8ee3e 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 1a79b3a809f 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 9bca1a60abf 48: onsuccess: #559: 1: Success after binutils: 6 commits discards f7215f6f93f 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 1b4f63faf58 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 8df0a0b92c1 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 261aa5f0167 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards fe43447b353 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 14611c51a0f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards d8d2b2755dd 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards c1ef1af5f1b 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 62e677adf8f 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 878c87b920f 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 8d634a2af90 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 8ee5cb8a9fa 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards ec57862b063 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards ecacee2839c 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 545530a500b 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 3575c6f8a3a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 5c953af2a19 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards ad0a45737b9 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 800a0143bb6 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 576c19bbd3e 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards de991480684 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards e47d19341cb 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 3ae454ef417 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards a41d23dc991 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 25ce6bfabd9 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards e15d5fc2f8c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 67376c66cdc 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 434122f8f64 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards df8b01eeb2a 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f49404e82eb 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards fef311d9519 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards d5ca9440c0f 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards afd6377e48b 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f6e4a0649cc 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0c5dc994dad 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0e6943aa09f 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2ca866992f1 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 1529abe754f 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 62e8c3c343c 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new e7a38778d60 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b57e0cbf4ff 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a25c73ca26f 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 91178a9c6ca 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 68dd93df2f2 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 82f29b4e747 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 34b6e404ee9 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f59b2fb3a07 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a3731e34b3b 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 660d1b92eed 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 6d53903a50f 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 10a6b899125 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 9d18f211bf0 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 37366a5ce18 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new e06ccb1b89f 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new d7d91c6fb9e 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 7df6326604c 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 112c3e5e307 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 30030057191 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 3954d2e74c4 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 5efdf74673e 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 90a5ffbebc7 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new ca7d85a5404 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new a9cf550fb72 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new f9a21983764 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new d74973d29d4 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new d3d80b1f28d 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 5bb2415093c 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new a58b412696f 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new bf84cf17e40 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 6f2e23c043a 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 1f56eea1879 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 12c1fc74c53 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 0a7bca08ffd 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 16993a26700 47: onsuccess: #556: 1: Success after binutils: 12 commits new d3c9e51f90b 48: onsuccess: #559: 1: Success after binutils: 6 commits new 9764823e004 49: onsuccess: #562: 1: Success after binutils: 9 commits new aeb020ff688 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 0133cc9d2cb 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 773ace5667b 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 5bf0e1eb0b4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 443e201e8e3 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 1b980920895 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 26e650acde0 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 9f2c35ec7c0 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 03587442175 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 8f31dc75c92 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 72cfd198852 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new ddedd9efc92 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new e52fc8d2f24 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new c501b2aa1d4 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 3f24b9e47f6 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new b23aa2967cb 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 90a42825b52 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 215dcc05f8f 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new c8bbab7f980 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 3a6a2732d7c 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 7efd467ea93 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 5f43892ff98 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 35c0eac4bff 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 0ed2aaa86bc 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new e8a51519e9b 74: onsuccess: #590: 1: Success after binutils: 16 commits new 4d5904786ba 75: onsuccess: #591: 1: Success after gcc: 25 commits new 9c312005472 76: onsuccess: #592: 1: Success after linux: 63 commits new f3c48428680 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 3f08a7ed5f2 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new ba7a0cf4afe 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 3a726ac7830 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 92f4ac59878 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 5f3cd063c82 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 25d6c775c99 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new dce0e221f69 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 2d8ab0f1187 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new e87f0690acf 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new a9689d05dc7 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 83e7e7841f4 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 961a0324af2 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 0e8a82986ec 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 38553f78d2b 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 5089caf287f 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 62669774570 93: onsuccess: #613: 1: Success after binutils: 19 commits new 1a8481c6881 94: onsuccess: #616: 1: Success after binutils: 2 commits new e2927bd79eb 95: onsuccess: #619: 1: Success after binutils: 5 commits new c0cb44f7336 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 2e87a7552a7 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 7b4e447e875 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new d72015cfc88 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new faa6eb05448 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 640d1ac7718 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 1c4f1185259 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 32a310a2d5a 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 00a0ab659d5 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new b62eb559bbb 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new acd6fa5cde6 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new b1de3f2cc26 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 50840e8a911 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 4159c05f548 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 0565536ae52 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 697c041eba8 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 319556d762f 112: onsuccess: #641: 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 (9bda320d068) \ 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 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40180 -> 39848 bytes 04-build_abe-gcc/console.log.xz | Bin 213732 -> 216316 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 245104 -> 244552 bytes 08-build_abe-gdb/console.log.xz | Bin 39236 -> 38508 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2276 -> 2060 bytes 11-check_regression/console.log.xz | Bin 5968 -> 6152 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 62 +++--- 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 | 38 ++-- sumfiles/binutils.log.xz | Bin 63012 -> 63124 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81800 -> 81768 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121704 -> 121928 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 409 insertions(+), 417 deletions(-)