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_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards d1cc93aa0b1 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gc [...] discards 283ab35d399 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 45eff6ba742 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards b8f017a8a41 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 29313e56bfc 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 86ccc7dfc63 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards b75e37b546b 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 6a136c9d06b 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 14131ed17cc 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards db1cec72008 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 321b1cc07fe 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 153a17eb179 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 1974fcea928 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards e17e44ed193 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 41be65ac343 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards da6c97b79a5 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards ac359510777 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 9b1192b49ba 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0863b5ffcf6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards bca0dc38aec 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 5947675283c 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 78b1b158406 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4b2748380bc 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 437259df509 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f40bffcd5f0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 810ffc5750b 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 98896b558eb 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards d3502d04631 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 72316afad0c 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 64bc9c03f7e 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 8eb6e26d2c6 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 1faf9fa6a7c 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 5744de6eb0d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards c53cd082335 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 58510e71a93 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9ed6b71f6a7 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards d57954f36d8 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 95cc3d5467b 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 002499e8a73 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards bcb214c7fc6 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 0579e4cb3cb 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 2ae60a302f4 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 2320c935f0f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 2ce7e4b6a12 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 4e04ba7374f 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 09cce729a9d 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 0575139bf9a 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 994735cef55 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards d0196ddc0a3 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 51e0862fe1e 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards fb9ae3d6521 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 4932369b070 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards e611daa85d6 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 4bc27f92496 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 4f4d28a1b4b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 70778682171 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 4d66d1a8998 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 7272430cc4f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 78c5339f345 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards a28dddd5601 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 09423a865e0 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 298db8c1178 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards e93315cb775 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 2ae0f2ec205 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 2ba9d6fa81c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 0ca65c020b2 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 0cba5c84bae 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 94534de5a42 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 45a9048a3f0 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 0f06d5dd167 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards ebd2e2f4d4c 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 6a17c4ff396 162: onsuccess: #624: 1: Success after linux: 10 commits discards 46099ba55ff 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 8a7171ed535 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 94a99765540 159: onsuccess: #620: 1: Success after binutils: 12 commits discards f820cefe1c3 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d29b43be1d7 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 423d152dffb 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards d9dacf0100e 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards e052323ab50 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards cc81ed86589 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards ffb1e254d1e 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 05646a5c7d6 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 7b9a528a713 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards ad8409d436a 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards cb2bc6c39b2 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 322d4fed547 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 2f9620697ec 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards d21ab754805 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards de5b8a82ba6 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 7c6599d840e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4d1a01a4071 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards ea6cd74f4dd 141: onsuccess: #601: 1: Success after linux: 794 commits discards 6441d3e55da 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 76a16211b94 139: onsuccess: #599: 1: Success after binutils: 10 commits discards b548c66124d 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 9afc8619b27 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 85acb4c8562 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 9873c79add7 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards bdac2f919c2 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 7800566a28a 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 82bd8491dac 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 4f795db17e8 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 07827391d97 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new bba67e9a46f 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new f99826ab06a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new f87ee20bb8c 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new c1ee1381508 139: onsuccess: #599: 1: Success after binutils: 10 commits new a276bb420e5 140: onsuccess: #600: 1: Success after gcc: 23 commits new b36ff458498 141: onsuccess: #601: 1: Success after linux: 794 commits new 2765c62965b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new a8674163275 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 939be1e7c67 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 6ec0b487f40 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 6389151274e 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new b0bc90fba15 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new c4be63bdeae 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new b247b4d4475 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 55a5bff8056 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 022c177562a 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 9718840f6b0 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new a5ec309b078 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 6d2f7a86636 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new de81e378d61 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 0ba231548d9 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new cca8d074b61 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new ed418bdc6a5 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new a25070d9c5a 159: onsuccess: #620: 1: Success after binutils: 12 commits new 5703f5c69ec 160: onsuccess: #621: 1: Success after gcc: 11 commits new 83cdded6354 161: onsuccess: #623: 1: Success after glibc: 9 commits new 7e296c913fd 162: onsuccess: #624: 1: Success after linux: 10 commits new 4b6e0a7f5bd 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new d73c4645efb 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 006101b57cc 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 5411af29ba6 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 6cb9e6018db 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 3d87e3c3fab 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 3d95f78b25f 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 167dc175e0a 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new f9d987f43df 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new bfe8e3f50eb 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 2d610d86cbf 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 3f632b2f411 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new b88b1a39c02 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f9ede1b7c6c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 606542c46be 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 24eac83f54c 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 3091c27122c 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new c8c936ef27a 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 159fef47084 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 82b057864d5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 49f826562a6 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 03e5a5e60dc 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 49e21b51bfe 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 0e41f8feee3 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 3384df87a85 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new dbc417538ef 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 42b1d95304e 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 1073babf435 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 7e407c7572d 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 11418a350bd 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new b7b9b88aba4 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new cd2d61b0de4 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 3e41c1d51f1 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 3a5c5b999ef 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 1958e3eea05 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 78dc34da735 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new bc0089b4860 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new bb6d94ffac0 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 87fc6a54f97 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 397f7ad62a7 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 7493f993411 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new eb3d30040e9 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new d76a3e9da52 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 93a50f536b9 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new c6af5bf6d1d 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new ce9db6ca480 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 29d2bc3a950 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 1f1055d92b1 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new e6ff75dd73d 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 5131eb5afce 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a30c6137a97 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 314e16ddadf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 73ec540f7e6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 59d36a6d418 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e19512078da 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 34638025133 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 602c8956b23 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 432d51aac0b 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new cf7565005ae 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 8175f5916e1 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e10e93ac16a 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 7fa2c011f50 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 6fbe3e43ccd 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 1738d4a0087 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 12d0086cd6a 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new eb98b68e5c4 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new 48927ee63c4 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 7fd14320708 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new bf1a9fb8d00 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 4f3e3027f8b 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 869c40b9dbe 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gc [...] new e3677ec6153 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gc [...]

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 (d1cc93aa0b1) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

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 2024 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49268 -> 49328 bytes 04-build_abe-gcc/console.log.xz | Bin 236868 -> 235020 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 232448 -> 231624 bytes 08-build_abe-gdb/console.log.xz | Bin 46708 -> 46592 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9612 -> 11352 bytes 11-check_regression/console.log.xz | Bin 5836 -> 5364 bytes 11-check_regression/results.compare | 20 +- 11-check_regression/results.compare2 | 126 +- 12-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 56 +- mail/changes-list-short.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.sep.xz | Bin 71732 -> 97448 bytes sumfiles/g++.log.xz | Bin 2878556 -> 2886288 bytes sumfiles/g++.sum | 43 +- sumfiles/g++.sum.sep | 7271 +++++++++++---------------------- sumfiles/gcc.log.sep.xz | Bin 68272 -> 70252 bytes sumfiles/gcc.log.xz | Bin 2459744 -> 2516260 bytes sumfiles/gcc.sum | 17 +- sumfiles/gcc.sum.sep | 5567 ++++++++++++++++++++----- sumfiles/gfortran.log.sep.xz | Bin 30176 -> 14496 bytes sumfiles/gfortran.log.xz | Bin 958048 -> 960532 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2482 +++++------ sumfiles/libatomic.log.xz | Bin 2284 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233784 -> 233752 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 17112 -> 6408 bytes sumfiles/libstdc++.log.xz | Bin 468272 -> 479240 bytes sumfiles/libstdc++.sum.sep | 329 +- 42 files changed, 8324 insertions(+), 7699 deletions(-)