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 a6d4a311b7 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 86e3349265 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 57f479c47b 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 9500a0cc39 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 9a889e0cf7 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards a326e48a95 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 786914c4f4 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 147e9ee8ef 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 664ddeb670 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards f74a2b13e7 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards c09511c414 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 8ccef3f7d7 149: onsuccess: #684: 1: Success after linux: 10 commits discards 6b08a399a7 148: onsuccess: #683: 1: Success after glibc: 9 commits discards f90b142571 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 8cd6f20aff 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 2f3f4aea02 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards a1ce955d2b 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 1c4f80326a 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 20c4fbdd1d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 94cc7a15d3 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards df6bd783a6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 9d36478023 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 75bcdd350f 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards c4212f2044 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 8daee03a64 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards b903de0cf4 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 0b066de1a4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 03fd73cdc7 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 048888cf78 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 525e085428 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards aeb6917d18 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 2d9e3f0779 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 9b95a3ee35 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards b03b8d29dd 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 44877a282c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards d0867240dc 125: onsuccess: #658: 1: Success after linux: 3224 commits discards a1a732ab1f 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 75d7982ddd 123: onsuccess: #655: 1: Success after binutils: 22 commits discards aa07dd0e55 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 810dc5378c 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 21010afc0d 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards aa66113ba0 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards e3616d86d6 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 73223e8ec0 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 083aa5a0b5 116: onsuccess: #647: 1: Success after linux: 3 commits discards 02cc832a27 115: onsuccess: #645: 1: Success after binutils: 27 commits discards e9ecc52977 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 591584a16b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards ce80258f97 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 51005a0d5b 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards b9153ef56e 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards c875f9d303 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards 2aa68b8fe9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards b31517bb60 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards b954f84070 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 784848d100 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards a05d64199a 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards d3f3c73c93 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 36d83004a8 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards a5996140bd 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 4833c90c44 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 2db5e37f69 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards f28ba3d9c1 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 71a91e8d65 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards b3db52e04a 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 281ba9b63e 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 37a4cf5503 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 95bbff03c1 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 2b10bb1e26 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 170cadf471 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 6d0a2098c0 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 93001f4f13 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards ec9079721c 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards fcc2aa641b 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 272eef7f5f 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 054a6caf7b 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 5092b2d067 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 3e2a564813 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 52af65e5c2 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 593398dbbb 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards d69552aecb 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 8bf4d6403b 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 93f9467792 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 7197216941 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 99c1a88f93 76: onsuccess: #592: 1: Success after linux: 63 commits discards e81b68c20d 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 5b275f9fc4 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 26486b0507 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 83d4dcfb35 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 31650052ca 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 8721efb858 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards cdeec9e632 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards a42104946e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 83dfd133a5 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 5bda5e0121 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 6f3e5d98cd 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 9174ae9293 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 86e23a0353 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 2b02db8749 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 367d11b151 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards a82b9487ed 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new b8fdc8433f 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new c1ca40bc00 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new fae5cde314 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 58bd71d257 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 6f1c382a6a 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new c67b9472c2 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 738752cef4 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 1566b9a306 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new d5a89f33e2 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new c7c79f74ef 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new fce10f5ac2 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 8edd9a08c2 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new ef07dddd1b 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new db69eb32b0 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 54f3ce86a7 74: onsuccess: #590: 1: Success after binutils: 16 commits new 7e8ebd515c 75: onsuccess: #591: 1: Success after gcc: 25 commits new cced27c74e 76: onsuccess: #592: 1: Success after linux: 63 commits new d9d9fa84e2 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 52e20bce5d 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 75cdcda078 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new bdb34f7350 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new ad4b99ae0d 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 6b97d0cb90 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 27d68e6d3f 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 7c1d2d0945 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new b6e6909ce7 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 80a8f7292d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 1bc9d4c0d2 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 1fe8702c1a 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 4585e0c102 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new fb0c7e8b4a 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new be64ba295c 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 5f3897ea33 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new cd8bd5930f 93: onsuccess: #613: 1: Success after binutils: 19 commits new 42864ce6dc 94: onsuccess: #616: 1: Success after binutils: 2 commits new 41435d6fa7 95: onsuccess: #619: 1: Success after binutils: 5 commits new 094aaa77b5 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new e3ca43d880 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 67054fee7e 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 9a62a399d6 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new efea6000e3 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new da38e42ddd 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 94ed675b78 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 2d6b025187 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 8a1071d1af 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new dfd19cf463 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new ea3298a112 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 8c69355d43 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 555dd654f8 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new edccd80c4d 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new 697b90c3f3 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new e7cddc2954 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 4b508c857a 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 4b2d414be4 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 1c83719a79 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 163fa501f6 115: onsuccess: #645: 1: Success after binutils: 27 commits new 1597f5dce8 116: onsuccess: #647: 1: Success after linux: 3 commits new ddc9315280 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new a41454e966 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new ec96459569 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new a6e7af4162 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new fce0c2b2d3 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new f0bbb11ca5 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new d1e98c7b8c 123: onsuccess: #655: 1: Success after binutils: 22 commits new fd98ffbd58 124: onsuccess: #657: 1: Success after glibc: 2 commits new c909947d44 125: onsuccess: #658: 1: Success after linux: 3224 commits new fd1014e1f3 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 1319ffc80b 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 80b99ff210 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new de9aafb096 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 3b20c6f880 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 0ab490f459 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 8f1c5e3566 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 18a21770e2 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 0ec703f80b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 6f2bfa4527 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 5c9384ef0c 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new f151cebf0b 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new fbf409cf7e 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new da4b825f7c 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 1008efd346 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 4ef2d840e8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 1aaaa0face 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 8e06b0597c 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new c7ea81888a 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 209083e7a6 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 6633e47a4f 146: onsuccess: #680: 1: Success after binutils: 20 commits new c6b7b5fd01 147: onsuccess: #681: 1: Success after gcc: 6 commits new d495702920 148: onsuccess: #683: 1: Success after glibc: 9 commits new c820a7dd81 149: onsuccess: #684: 1: Success after linux: 10 commits new 0bd60f1b1f 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 303ba294b6 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new be9669f0ce 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 5b18faf8fd 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 26358a518b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 051f5b286a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 81201657f6 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new bcf0580dae 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new cd0db04ec7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new c3656de362 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 1eb5c48a91 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new dbeb32cb58 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...]
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 (a6d4a311b7) \ 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 1736 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39496 -> 39580 bytes 04-build_abe-gcc/console.log.xz | Bin 213540 -> 215856 bytes 06-build_abe-linux/console.log.xz | Bin 9072 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 244772 -> 244444 bytes 08-build_abe-gdb/console.log.xz | Bin 40400 -> 39160 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2216 -> 2300 bytes 11-check_regression/console.log.xz | Bin 5920 -> 6220 bytes 11-check_regression/results.compare2 | 4 ++-- 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 +- 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 63180 -> 63024 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83836 -> 83852 bytes sumfiles/gas.sum | 4 ++-- sumfiles/ld.log.xz | Bin 122260 -> 122248 bytes sumfiles/ld.sum | 4 ++-- 28 files changed, 52 insertions(+), 52 deletions(-)