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 554ec156cb7 125: onsuccess: #658: 1: Success after linux: 3224 commits discards de77aab2c08 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 4cad33be542 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 7ee364588b8 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a2d783abf15 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 9366af7873a 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 91842ee1c28 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards e1c96c9bbab 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 7c08bf515a3 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards c7f1c448fb3 116: onsuccess: #647: 1: Success after linux: 3 commits discards cc3650e5a12 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 57e399bdecd 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards ccddf5c86aa 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 3d494b762ec 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 08be70b7c5d 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 6b29378e645 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 2e6614fba28 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards a3f88217f58 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 36790970607 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 7e9fd42201b 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards ccb69615330 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards bca20bd7393 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards d0ed20d098d 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 92774dfeaed 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards e3817757f58 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards e9c04418b2c 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 3de1968ee75 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 54bdc4b88e3 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 8cbd84bccac 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 7b4f130fdaa 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 6a1cba209ce 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 6bec0747e18 94: onsuccess: #616: 1: Success after binutils: 2 commits discards fdf2a7a8620 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 8a2cf48479c 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards a1c2ad0d1fa 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards e5941797e68 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 1fd5d964272 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards fa44fb642f7 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 217be3731f5 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 2035ffb7949 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 66cd8f7151c 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 9b71215cb89 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards e8d350c5d96 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards bbfd801c615 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 7e1f1ad1f51 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 38f9102adf3 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards ad3c47a8599 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards ca18590c700 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 449a730daed 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards bb27342bc6e 76: onsuccess: #592: 1: Success after linux: 63 commits discards 4faf3c9f961 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 8a17f368247 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 136426956cb 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 3bf0081820a 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 4797cdeb0e0 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 0984da84fcb 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 4fa7e7c0137 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards c7e4bc67aa1 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards b5eb73297a6 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 29a44f46f64 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 7c3757b4891 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 3bbafb1464c 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 2eecdc098a8 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 13fe0921bdb 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 1901146c005 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards b67b8db2794 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 599ef2b2219 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 8c1b86ff475 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 8e7732277e3 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 1616891cba0 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 6afad888527 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards ead0016915b 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards e76e55507ac 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 5b54a0fd07c 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards d70dbb27184 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards d7eff494fd7 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards e33a5f056a7 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 18d8a04ede9 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 35b2f55fae0 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 944536f1d97 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards dbb70219150 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 86bbd89f963 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards ff0f494389b 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards eb47ba53c2e 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards d4d22bf39a5 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards b053c31ff62 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 01b1ba52d2c 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 3641009ef08 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 2fefbb42143 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 3b5e8726814 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards d4b33c490e5 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 59f850c1e9f 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards e5b407cf04c 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 9411d2052c7 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 4cf9c4afd95 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards f259529a74c 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards c30d3b78981 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 40c44469d88 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 0825e92541e 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 16114fdedb8 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards f0d660431ba 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 6b149304bb7 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 8eb6865d86e 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new a99aa883e9a 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 90a4441b903 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new fd2d9537614 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 87e3e1938ce 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new ca6fc62b474 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new dd2eb3340af 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 90e7ed207c6 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 9f0f7e283ac 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new f103e7d0c34 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 059baea8588 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new bc86c5a3f11 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 8a5bed339ec 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 51887d26b58 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 549741036fc 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 661239f538e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new c5b01f68727 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 1033f993dae 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 2469111dc9c 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 39260953515 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new c4ef22e08ce 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 7fdeef5e251 47: onsuccess: #556: 1: Success after binutils: 12 commits new 433c8c6c999 48: onsuccess: #559: 1: Success after binutils: 6 commits new d0d58c4eda5 49: onsuccess: #562: 1: Success after binutils: 9 commits new 7e99ab23a75 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new a4299177c7f 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new f5254b09664 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 0d79c8e1ebe 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 6cbf03b6045 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 6d60c3bc9c9 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 4142a1185a6 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 8fc7bdfb784 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new a6b05c7db18 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new dfd92970a05 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 4f6b1083c40 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 136a52fb96f 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 7737a4d889e 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 2e23db9eecf 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 2fc96d156a8 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 7b49a670a58 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 69b494da2d6 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new ce988999be1 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new af43e8e3deb 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 6a719b8ebab 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 1fdac068e0a 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 1f4f59fadd7 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new ecc6a319140 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new cec57abf271 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 27f01e229b9 74: onsuccess: #590: 1: Success after binutils: 16 commits new 18b6d783ebd 75: onsuccess: #591: 1: Success after gcc: 25 commits new 02d9127ae13 76: onsuccess: #592: 1: Success after linux: 63 commits new 4ac5d14589b 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 728653f2954 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new eb881ca3ffe 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 8aa44c901f5 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 69d1a0b361b 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 073d63a425f 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 92f2967e3f8 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new f68777c480e 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 480ed92d635 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new afe3d5d4877 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new ec97abb0e9e 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 5b52df5674b 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new f3322dd9b7e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new d6e0f292889 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 95a0df956fe 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 862b5d49f95 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 3783bd55276 93: onsuccess: #613: 1: Success after binutils: 19 commits new ac787467223 94: onsuccess: #616: 1: Success after binutils: 2 commits new 8bb35fe9c95 95: onsuccess: #619: 1: Success after binutils: 5 commits new 5fd9d58c3a7 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new ce05c855763 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 5204d265cc3 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 6dcba475635 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 59ae0ca86ee 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 643aa3df589 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 7703bd23c31 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new efc21ebabf5 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 01197d3af0e 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 41f7a677283 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 55c15755ed0 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 7b182079b9f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new c172b701051 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 68aa1d06d4f 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9f921bea1d7 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new fec5989829a 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new d7ee7c084cb 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new dc170e29309 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new f17f4c7a566 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 8aa7018a7c4 115: onsuccess: #645: 1: Success after binutils: 27 commits new 4f50b0df44f 116: onsuccess: #647: 1: Success after linux: 3 commits new 8a160e4093c 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new f504aaa89e7 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 005bc219f7e 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 9bcd28c15f9 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a8a1e642c93 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 5d8218bebaa 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 735c49480d9 123: onsuccess: #655: 1: Success after binutils: 22 commits new e654167d121 124: onsuccess: #657: 1: Success after glibc: 2 commits new c9ba6d98e77 125: onsuccess: #658: 1: Success after linux: 3224 commits new a86c0ce707c 126: onsuccess: #659: 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 (554ec156cb7) \ 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 1728 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39728 -> 40192 bytes 04-build_abe-gcc/console.log.xz | Bin 212860 -> 215988 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9412 -> 10248 bytes 07-build_abe-glibc/console.log.xz | Bin 243340 -> 243612 bytes 08-build_abe-gdb/console.log.xz | Bin 39012 -> 39360 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2552 -> 2596 bytes 11-check_regression/console.log.xz | Bin 4736 -> 6192 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 | 34 +-- sumfiles/binutils.log.xz | Bin 63040 -> 63240 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83748 -> 83724 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121700 -> 121764 bytes sumfiles/ld.sum | 345 ++++++++++++++--------------- 30 files changed, 406 insertions(+), 403 deletions(-)