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 e6a7f98d7b 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 50d7c05c39 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 429d97ccd0 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 8d4b47960a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards dd9b22d91a 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards a0af04a693 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 1b16863595 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 72fd77358c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 04f64a8aeb 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 5a4fde736f 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 605d420c55 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 70c66bbc4f 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards e7f6bf77f1 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 7c8c1b4aaa 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 9671d40375 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 88acd98991 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards ece593b0fb 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards f76f1bf3a2 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards c1d46e1bb4 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 0d8a5d26a0 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 625a902f27 124: onsuccess: #657: 1: Success after glibc: 2 commits discards ba39395c05 123: onsuccess: #655: 1: Success after binutils: 22 commits discards ee9f77d0a6 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 24da19690c 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards e9a2c098a7 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 7082e6e6be 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards cb74d1eb67 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 25e443a20a 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards c978a02aca 116: onsuccess: #647: 1: Success after linux: 3 commits discards f81c59367e 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 4230166a3e 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards c2a55ebfe2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 861918eb51 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 3c186624bd 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 9219e051d9 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 21f6fc7abd 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards fc1d560d85 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards c9b8377229 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 7bfded8b8d 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 7f2b3cf596 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards d024229a64 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 538719b12f 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards eb55e90cbe 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 76009c9581 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 8344e581b1 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 5d2ead73c9 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 29207b4723 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 6c1a369d18 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards f40433d5ef 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 154cdc1d6d 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 8c088b4e3e 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 31400bbdda 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 34efce90a7 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards cf0e555518 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 5ab6ebdaed 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 2a52134a22 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards d275a2f987 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards bcacc66814 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards e198fa920e 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 86047b102d 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 8e4d1ece12 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 442800a0b2 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 169e23ed35 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards a8ae536450 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 18dc3ca106 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards f9eb27e40b 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 7d53b79517 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards eee7892b89 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards c2d12696a4 76: onsuccess: #592: 1: Success after linux: 63 commits discards d1fd4c81a1 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 78ee7f6a1c 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 193cc7b39d 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards b2c56738d9 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 60e3ccbb13 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 1906e9a299 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 57b279a8d4 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 28de847268 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards b9cb3395e9 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards e643d05fbc 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards cb3ac59a32 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards aaa43a23b9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards e36ed2dcc3 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards f29bb4240e 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards bb3af9baac 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 0c2787df9f 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 9dd55e0ec2 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 364b28f710 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 7dd1cfa595 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 929300f006 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards eb4f62f90c 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 168da92819 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards c3eb49432c 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 1070b652ff 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 3310492f7f 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 934d37cd3f 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 58b41b2889 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 82934ac544 48: onsuccess: #559: 1: Success after binutils: 6 commits discards ae5b487f31 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 8c0a6d5d1c 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards c14a133bee 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards a32dc49648 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 21e9920391 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new e61ebf1dd6 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 0329a36667 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new ea6310561b 47: onsuccess: #556: 1: Success after binutils: 12 commits new d386314428 48: onsuccess: #559: 1: Success after binutils: 6 commits new f244cc8acc 49: onsuccess: #562: 1: Success after binutils: 9 commits new 80870c8786 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 830e6d7e45 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new c3500482ef 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new c1e1eda560 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 932fdda0d4 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 3df29b6321 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 2915cd3149 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new b9edd77649 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new b69556e1d8 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new b37d71e5d3 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 2b289b6911 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 9d12450d60 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 3bc849ef3a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 73daa98bd1 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new cbf8be61b9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new a8f4486160 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new a1aee36c16 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 7b5b21a8a4 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 4b69d0bbd5 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 9702b0f076 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new b36236364f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 4b5759649f 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 63653523e7 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 73e0560fa0 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 33d80d5f97 74: onsuccess: #590: 1: Success after binutils: 16 commits new ed7cd78efd 75: onsuccess: #591: 1: Success after gcc: 25 commits new 7c624af18f 76: onsuccess: #592: 1: Success after linux: 63 commits new d6525f2a47 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 6a53f40395 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 49ff0391cc 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 688810ddd6 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new d788dc3bc7 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new e77be7132a 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new b6d835b4ca 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 949e09d80c 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new f29fcaa496 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 4a66352a88 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 06ca2afb87 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 2a1bf84807 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 117edc9b3e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 7999b115e6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 058151573a 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 5028f82d5d 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 16be040e23 93: onsuccess: #613: 1: Success after binutils: 19 commits new 019a27e5ea 94: onsuccess: #616: 1: Success after binutils: 2 commits new 8f2b0139dd 95: onsuccess: #619: 1: Success after binutils: 5 commits new 100f242b1f 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 04281d6743 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new f954100c6c 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 84734e4b4f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 2f2738f3a4 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 89219f13de 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new aed9a15de3 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 4f16087134 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 3b9811006b 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 1310d3a8cd 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 9b16a2fbec 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 0d7f673869 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 0a77cf6b8b 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 1072b0fffe 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new 938d6f91d7 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new fd5773cfca 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 778667ae60 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new ae37f9d3e2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new a7681de2ab 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new fc2329c483 115: onsuccess: #645: 1: Success after binutils: 27 commits new df21068f4f 116: onsuccess: #647: 1: Success after linux: 3 commits new 03d2032d07 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 2de0fe41f3 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 22d0c9e642 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 8b761f08cd 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new d3bba2b4be 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new fe56b04382 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 8918313cf7 123: onsuccess: #655: 1: Success after binutils: 22 commits new fb0af920a7 124: onsuccess: #657: 1: Success after glibc: 2 commits new 5fe039e08c 125: onsuccess: #658: 1: Success after linux: 3224 commits new a2d4f18751 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 17a9bb6aa9 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 735398df09 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new af11031253 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new cd1168d4e4 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new c98a2a63c6 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 63b0500b84 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new aaa313a164 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 4c5efbf4f7 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 5635483c3d 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 2718cda0c8 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new fd177ce42c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 6bae02b5e3 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 68ada2c2e5 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new adfe3749da 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 62d614f3a3 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 3694218832 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new bc7a615966 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new cb15b048ed 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new f2cd1f52a1 145: onsuccess: #678: 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 (e6a7f98d7b) \ 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 1744 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40144 -> 40332 bytes 04-build_abe-gcc/console.log.xz | Bin 214056 -> 214120 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8708 -> 8284 bytes 07-build_abe-glibc/console.log.xz | Bin 244536 -> 244572 bytes 08-build_abe-gdb/console.log.xz | Bin 39396 -> 39632 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2080 -> 2176 bytes 11-check_regression/console.log.xz | Bin 5808 -> 5664 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 | 32 +-- sumfiles/binutils.log.xz | Bin 63216 -> 63052 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83856 -> 83892 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122204 -> 122236 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 389 insertions(+), 389 deletions(-)