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 d81bd926b1f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 69871a3e682 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards cde5d949892 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f3e38f02678 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 497f1a09453 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 8ed7deb42b2 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0ee2383a233 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2721361086a 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 98ce86cc754 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 8151361b6df 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards e84feed7f1a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f7615a7e50e 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards d21d46e1e0d 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3c0b23a12ae 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 26145d045b1 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards f181c202816 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards f780dca0e19 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 191de828a04 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards e31278a30e9 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 1bf8e549754 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards f0729336169 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 7cd0b437f0b 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards d6841d86e75 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards a743616e2c2 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards ee0e10928b7 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 74924603be9 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 76c107c9417 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards daefafc3a0b 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards cf77694f3fb 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards a7e17aac640 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards a8aee803cb1 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards ce8dac4c3a2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards c55045af2ae 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards a4f46a0d5ca 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards d8671ff19f6 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 33bb24b5839 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 8cc9fb19438 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 17430c7759c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards df97009b742 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 4b17914cab7 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards b70878bae9d 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 97f23db2044 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 456a5f84b24 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 55455201d93 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards de9e1721781 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards b2f7b776b0a 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 338b53cc96f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 0733a44a1ba 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards c0d55db20f3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 15ffbac0c0c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 0fdb22d3686 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 532d0f7131f 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards dee4cdf8298 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards e8933332d88 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards f94f9267803 149: onsuccess: #684: 1: Success after linux: 10 commits discards c983e91cb2a 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 88c8d3403da 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 1272b1bbdc0 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 9315999ec31 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 35e07d35a6a 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 654a4f74286 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 53f9cf886d1 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 36dc98fa382 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards e9f64a5de8e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards cb69d7b90d7 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards a039ae3734a 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards d4331330762 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 36033114a7a 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 8282830ab91 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 7dd31b55846 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards cd447d55090 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 656653ccc56 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards d39d98c623e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 156825b5025 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 40772a94fe9 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4b911917d64 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 52f6274877d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 5d81fb03e1c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5d886f64dc9 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 75c4080270e 124: onsuccess: #657: 1: Success after glibc: 2 commits discards d60cdf21645 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 5c3f49cc8c1 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards fa95d1f31e3 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 9684448bed7 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 809f0424e86 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 8cc08696960 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 5576c90ae67 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards db058025cd8 116: onsuccess: #647: 1: Success after linux: 3 commits discards 220a57ad29b 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 133eec74bc8 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 940a9500552 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 2354cd4ec01 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 3782abf0577 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards fef6836a9ce 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 67f6ae9db26 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 9ddbb6894be 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 4b15b8c2ee7 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 9f3eee06d77 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 5a48ad1111a 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 166a5ff4441 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards deb8f652b6b 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 71a03dc57cd 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 29203bc4c90 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new a0f66d8cdcd 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 931226ae88b 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 25684c03f0c 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 8131e55b794 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new e33974301c3 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 97a6f3fc002 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 53efac6de24 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new f34b4edf06c 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new c60c111b112 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 99925446cba 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4bac3e86630 115: onsuccess: #645: 1: Success after binutils: 27 commits new 1c86f13d94c 116: onsuccess: #647: 1: Success after linux: 3 commits new ee66f25d453 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new d759a126691 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 9c9135bce95 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new bc2e7ff5ef3 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ae50add537b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 0d75dad3c1e 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 252f297011a 123: onsuccess: #655: 1: Success after binutils: 22 commits new 66b3d573de5 124: onsuccess: #657: 1: Success after glibc: 2 commits new b8a0fdde606 125: onsuccess: #658: 1: Success after linux: 3224 commits new c3f6f9caac2 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 4c083754cdd 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new ac87eac5624 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 5d0bd7a5f01 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new d6bbced1a9b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 1512b42fd42 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 710f8262706 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 407cfd47b11 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 49f38d21f8b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 06890226e22 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 14b8fba74e9 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 7acca9b5209 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new e57675b8615 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 4bd6a7b6845 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 6751bc02ea6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 4a53e0580b8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 2b510ab92b0 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 6137df244cb 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new cc6d7abdcc3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9a4928d8e0d 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 5c16fdad601 146: onsuccess: #680: 1: Success after binutils: 20 commits new 2aa0f2988e8 147: onsuccess: #681: 1: Success after gcc: 6 commits new 5adbd5f7f4d 148: onsuccess: #683: 1: Success after glibc: 9 commits new 50513f54436 149: onsuccess: #684: 1: Success after linux: 10 commits new a03d59b0a42 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new c42e76ebff5 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new d952e8ca9cc 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new dd00cfca9c3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new a664c60465a 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new e7d1642c580 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 178aaa94d0c 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new fb0440baf10 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 0dd4cd363c7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 36b95c8961e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new c7e53d80de1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new c0165151958 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new ef526c86dbf 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new dbf4a1be1b6 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 1cf54dadca5 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 81c5dc5d4f0 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 2bf4699ff6c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 7978d3d93e8 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 4a6d5abafd3 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 5803bf513a7 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 2c2f3b9d6f4 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 7bd5e585a13 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 662568d55d2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new d8c5dce4795 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new a06f6e25174 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 1c99dddec63 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 5a83640438a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new e7c14f9b49c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 7e44e49aee5 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 3b7017b2c86 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new a238d839b50 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 93fe62dd914 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 01d747247ea 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 8e0644a077d 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new f0e1e10b0b4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 0dfdb4d2316 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 97c81f6b05a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new ac55b21fccf 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new e7dfc4de2d5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new f94bca527cc 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new e2d17f370c5 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 7bf8b9cff59 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 504cb77176e 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 2eb7d3041f5 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d1e68ffc15a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new a7defef1940 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ed31b49cbfc 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 60309cf0a8e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a27cc4b206e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 33d2591dfad 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 87022a1fc48 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 17298b18f40 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 892dccfadcf 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3c61e67be94 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new abf948c894f 204: onsuccess: #14: 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 (d81bd926b1f) \ 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 1920 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 38688 -> 38940 bytes 04-build_abe-gcc/console.log.xz | Bin 204024 -> 203116 bytes 06-build_abe-linux/console.log.xz | Bin 10076 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 245572 -> 243972 bytes 08-build_abe-gdb/console.log.xz | Bin 38456 -> 38704 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3760 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2144 -> 2284 bytes 11-check_regression/console.log.xz | Bin 6060 -> 6076 bytes 11-check_regression/results.compare2 | 33 ++++--------------------- 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 | 38 ++++++++++++++--------------- sumfiles/binutils.log.xz | Bin 63124 -> 62984 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83972 -> 83972 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 123632 -> 123620 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 57 insertions(+), 78 deletions(-)