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 5df62f5376c 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards e3a0c8ccd0d 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 2db25954b79 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 5460f19a960 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 7d430dec64c 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 2085ebd7d23 214: onsuccess: #26: 1: Success after binutils: 12 commits discards ef9fea6fd27 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 132ae37654b 212: force: #24: 1: Success after binutils: 2 commits discards ac6b8530b61 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards de3dd601d22 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 13757c3e7c8 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 4947f0642a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards ce2090d6812 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 2a84697dd19 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f8271819884 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 0a8e8f7cd87 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a6154af024f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ff1f4f76d8c 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 45b24151c9c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4855c145b3f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9be88d6ffb7 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1393a1d9805 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d45dce8b138 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards abfdc046896 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards e8d02501f92 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c7e0a1e0e3e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 605c8a02d0c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ccc05c70147 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 17a8f82dd0b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 56d3e3b57e9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 853b82ee65c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards ae8c6c4b125 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards ba19437c4f0 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards c0838f576fc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards fa35fb1a835 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 5e4c2813eb0 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards d969ce189b0 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 1af260f55e7 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 185dbead15e 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 001b0e86793 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards d29755c4cf0 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 00b8ea72767 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 01189b35cdb 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 7a2ce2ac90f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards c8ab2761ff6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards e3729cd46d3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 267769e9344 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 0ea23f9ab2a 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards b13d256f684 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 4d46d14a9fb 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 06226003f49 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 297d6add00f 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 5997abe7e9d 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 10c3d4fb9e4 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 93e25be1955 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards ad74c1ecf1f 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 34b9d155f01 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 576c80edaf7 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards c8945575f94 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 1ce5b99ff95 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards cf11ec43503 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 780ec62f143 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 65f2b8635ea 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards cb3c5fd47e3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 8ce911a9a88 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards e2abc45de4b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 70142f0f05d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 7f56717f448 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 20941b1595b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 07db6ce4ff8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards ee3101d0405 149: onsuccess: #684: 1: Success after linux: 10 commits discards 6c54fadff1f 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 0464a1d18fc 147: onsuccess: #681: 1: Success after gcc: 6 commits discards fcc92967bcc 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 16cf5e59e42 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards d4737196a26 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards f9b8e006639 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards ec8be7d27ff 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 221cfbc6871 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards b3a82348a13 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 192d34d1f49 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 57c9d2d9ad9 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 2d460c1b2db 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 733f8b9369f 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 65eecf01e7a 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 9f57336ff3d 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 2aa944ac43a 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards a6012f325d6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards ecf5c986132 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 4c0756d0e3e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 2aa3307d2cd 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 85620865420 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 114a37e7f95 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards b15472cc84d 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 9320dc6bd46 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 468b1acc271 124: onsuccess: #657: 1: Success after glibc: 2 commits discards fad462aa1e0 123: onsuccess: #655: 1: Success after binutils: 22 commits discards dfc9bf693ce 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards b4e218a5b53 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 5f9bb8890b6 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7945987ade7 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 7dc6e01ac33 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new da1df870a16 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 343c8f98e4c 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e465f6390e0 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 8db7e2522ef 123: onsuccess: #655: 1: Success after binutils: 22 commits new 45781bec4b0 124: onsuccess: #657: 1: Success after glibc: 2 commits new 370d7838bce 125: onsuccess: #658: 1: Success after linux: 3224 commits new 04c9c2634ee 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 46101649cda 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 19ed5d38c60 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 0c1e7a76e93 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c1398896cab 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new dc7a23eb054 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 6dd496268ae 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 7029374993d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new c7bbcd844da 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 46dd34df8be 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 1469de0cd64 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 0652fcb9f0e 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new feb103232aa 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 0bb11c278de 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new a82992a6514 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 9f9156ae9eb 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 295c3a6b330 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 804bd43236c 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 147d9c130e5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new d992f2a78ab 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ff7fae4ce9e 146: onsuccess: #680: 1: Success after binutils: 20 commits new b59172deab3 147: onsuccess: #681: 1: Success after gcc: 6 commits new 082d5d2ad45 148: onsuccess: #683: 1: Success after glibc: 9 commits new a3da735e6a3 149: onsuccess: #684: 1: Success after linux: 10 commits new c77293462bc 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 279d1419351 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 89445c4da6a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 8f1e7db9b29 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 6885a9a9445 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 9c35c18b718 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 2df0b75e78f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 2b4aac4625e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new d531bf4e4ca 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new bec6d08f378 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new e56ede8784a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 8141b59f299 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new e5a2192eb41 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 1b3d3583d24 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 64a7a6f903a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 6fd070bd38d 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 67304e26b51 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 3650b248e9f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 33dcc9fe76c 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 65be537bc61 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 7e3f17d8e3f 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 5b3329f6158 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new b4d673c1c53 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 45175a08ac3 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new f30cf98095a 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new bb2908a6031 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 8beb508d088 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 9713a002504 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 632dffee693 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new b2b37289e13 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new ba6b23e508c 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 818bfc76862 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 8679c2dd366 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 8026dbc02e9 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 0ffc83ece3c 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 39a25b9580c 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 66f737c07b8 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new cf556430ae5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new a450bcd1b2e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 5036f2b007f 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new e500d5ca858 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 334e4c77980 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new bcf8a160f7a 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 73431d4c57e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 716d0056c3f 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 91f79335d91 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ce459d5c437 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 8ae6ff50ea5 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 713ca2796af 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e1e7a4703c1 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c6fa03d8375 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6964c43f2d6 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3cbf5bc2d23 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 8877a962fb7 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 9ee2e8ea119 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7f7463f786c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 09100b178a8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new cc41b1a9fcf 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9ce599b4142 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 296bc20efd1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new bb6fd47c0c3 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 95eebc834e9 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new d5083f20a22 212: force: #24: 1: Success after binutils: 2 commits new 385e2337872 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 631b6fd8081 214: onsuccess: #26: 1: Success after binutils: 12 commits new 5a9e674ff64 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new a0c24f1790b 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 36d45c2932e 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new f0db1ae243b 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 2ce73292955 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 136c7dd6982 220: onsuccess: #34: 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 (5df62f5376c) \ 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 2072 -> 2336 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35544 -> 35108 bytes 04-build_abe-gcc/console.log.xz | Bin 203708 -> 202960 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 240956 -> 241332 bytes 08-build_abe-gdb/console.log.xz | Bin 35308 -> 34700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2704 -> 2100 bytes 11-check_regression/console.log.xz | Bin 4800 -> 5032 bytes 11-check_regression/results.compare | 10 ++++---- 11-check_regression/results.compare2 | 22 ++++++++++++----- 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 | 34 +++++++++++++------------- sumfiles/binutils.log.xz | Bin 62576 -> 63020 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83960 -> 83932 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122476 -> 122608 bytes sumfiles/ld.sum | 9 ++++--- 29 files changed, 74 insertions(+), 61 deletions(-)