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 f001be8d98 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 84c337780a 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 8a969651d2 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 2238944064 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards e86dac748b 162: onsuccess: #624: 1: Success after linux: 10 commits discards 8ddd1eeec5 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 72a4825b8f 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 5a0760f031 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 8ae2e3e6c8 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards 2362a2abb4 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards 231ed5957e 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards f689815fd1 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards c795c16ea1 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits discards e9168e395d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits discards d20bb59390 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits discards d6c651a248 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] discards 88154a8101 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 9aec6a929d 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] discards 77484fec85 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 16e2d0ec95 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards cf1f9c82ef 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 17fb5ac508 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 17da9a12b4 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits discards 5bf88c4fc5 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 5f33e69b42 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 8cb8047ed2 141: onsuccess: #601: 1: Success after linux: 794 commits discards 3cd70410d5 140: onsuccess: #600: 1: Success after gcc: 23 commits discards bfe37b77c1 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 6695c2fa93 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards c5f65a4410 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards b77a602ca4 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 17dd63107a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] discards f0cd57a053 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 6ef45f0f76 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards a4d3677bc7 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 3770cb8ba2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 6fcc2eaa2f 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] discards 2e9ac1d36f 129: onsuccess: #588: 1: Success after linux: 4 commits discards f1c35759c0 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 6d247c8789 127: onsuccess: #584: 1: Success after linux: 21 commits discards 4de34d0e38 126: onsuccess: #582: 1: Success after gcc: 9 commits discards d22f1e6a0c 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 5c1392dbc6 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 7f34f27554 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 7100f587f9 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards e7b0157908 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards a41c3d7971 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 0dfb514da8 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards 50ae375857 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards bc1ce1e625 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards 67c02ea6b2 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards 8c99e4b122 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 8b0d5b3f89 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 1221d3dce1 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 104e0f2385 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 2de5303224 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 14f8c03bba 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 830a60d941 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 7e13713d7c 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 2b3f13c961 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 850bde2ee1 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 3403581846 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 60d7114f40 104: onsuccess: #558: 1: Success after binutils: 3 commits discards b04cb14795 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 4583da3eec 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 51579e15ce 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards fc2e1d4d0d 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 39d550665c 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards e3050c8b05 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards c2a72e68f3 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards ef445d785c 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 1195026d8c 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards f94c12deb4 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards db960e9ac3 93: onsuccess: #544: 1: Success after linux: 34 commits discards 237eccb149 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 68dbdf3158 91: onsuccess: #539: 1: Success after linux: 27 commits discards aeba021080 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 454af8fa06 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 23ce1e07ff 88: onsuccess: #534: 1: Success after linux: 12 commits discards d5d424f004 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 8d933bef98 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 4ca7583998 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards cd3c3cde05 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 71dcde1913 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 0b1a21c05b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 2d47222e26 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 4346120e72 80: onsuccess: #524: 1: Success after linux: 9 commits discards f6c2e4db9d 79: onsuccess: #523: 1: Success after gcc: 25 commits discards a89033d331 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 09cacb6644 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 4df6dc655e 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 131a91c776 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 5ed3361abd 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 825813f750 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards f446a10fbb 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 771a19b988 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 10fbdbf7cf 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 2c4a96a5f6 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards d36d33d64e 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 0a161175a6 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards b164d0561e 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 1ee428609a 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 088ccbf302 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 708d728c05 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 98fd4ac0b1 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 21ecf9f3fd 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 1082284eea 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 043c5ba8df 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new b98e9ae363 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 1280c7a89a 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 007b970413 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new c33ff04e7a 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new c2e5a824d8 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 0e4151c8fc 78: onsuccess: #522: 1: Success after binutils: 10 commits new d4e52ff763 79: onsuccess: #523: 1: Success after gcc: 25 commits new 9aaba4f7f5 80: onsuccess: #524: 1: Success after linux: 9 commits new cea6590f20 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 314f1fcd03 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new e1f77aa3fe 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 209f0334ae 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new ca8dfb4857 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new c12953a8ee 86: onsuccess: #532: 1: Success after gcc: 16 commits new ca6470344b 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 47d12cc2d3 88: onsuccess: #534: 1: Success after linux: 12 commits new a53f0f56dc 89: onsuccess: #536: 1: Success after binutils: 27 commits new 51d6063e1b 90: onsuccess: #538: 1: Success after glibc: 10 commits new a540fd2353 91: onsuccess: #539: 1: Success after linux: 27 commits new a10ddbba3d 92: onsuccess: #543: 1: Success after glibc: 4 commits new dc7a694f9f 93: onsuccess: #544: 1: Success after linux: 34 commits new 34b2d2c6ca 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new ebb40e89f0 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new fe74c9082e 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 2cba73788b 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new d259da72f7 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 1bb8cbb6bc 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new c4633a49ad 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 531be9c341 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 2bc4a94985 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new ff8f323194 103: onsuccess: #555: 1: Success after binutils: 4 commits new 832361ddca 104: onsuccess: #558: 1: Success after binutils: 3 commits new b250e03b9b 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 8aa55cc3f3 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 0aff9c64c0 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 4ac545b6bb 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 1486d89613 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new f8df52f905 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 4f95ae0afb 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new e0ec20a4d7 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 2db56f33c8 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 70f1c34bd1 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new d768b8edad 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 30008ea1da 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new 709413f3e6 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new 4243deef06 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new c4ecf2db09 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new 707068ff15 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new ef43f06a15 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 966e1a9fde 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 0a29906b22 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 9e7cf53a87 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 3af55f9776 125: onsuccess: #581: 1: Success after binutils: 4 commits new e912a3448a 126: onsuccess: #582: 1: Success after gcc: 9 commits new dffbca32c8 127: onsuccess: #584: 1: Success after linux: 21 commits new 613f8baa6c 128: onsuccess: #586: 1: Success after binutils: 22 commits new 9a3c85ea59 129: onsuccess: #588: 1: Success after linux: 4 commits new a39aa4c851 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] new 7c0951c015 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 306e8f8925 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 101ec66564 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new b05db698d9 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 34bcfb0581 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] new cbb58794e6 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 6e7e1ed7ec 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new e5b5861691 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 5c32264db5 139: onsuccess: #599: 1: Success after binutils: 10 commits new f4d105bb3e 140: onsuccess: #600: 1: Success after gcc: 23 commits new 32dab57cf3 141: onsuccess: #601: 1: Success after linux: 794 commits new ba2c21b355 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new d19e44a102 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 354b66789c 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new f3b1c48582 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 1ccc3f04f8 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new e7ac0aa830 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 9016140f96 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new d43e19331b 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new 52cdb0b316 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 4fbbae9812 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new 16521faba2 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits new 690432ae1c 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits new fd22c9e598 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new 92a1b283a9 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 7f6c00fe48 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 4ee853d9ee 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 83137a2377 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new 66c953e731 159: onsuccess: #620: 1: Success after binutils: 12 commits new 66c87ee78a 160: onsuccess: #621: 1: Success after gcc: 11 commits new a01181e568 161: onsuccess: #623: 1: Success after glibc: 9 commits new 03838ce622 162: onsuccess: #624: 1: Success after linux: 10 commits new 01cc2d60f8 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 3d01df0e15 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new b2730b1e29 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 0bbe3a985d 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 29b1b7b837 167: onsuccess: #629: 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 (f001be8d98) \ 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 1740 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 53512 -> 53388 bytes 04-build_abe-gcc/console.log.xz | Bin 237668 -> 238944 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8944 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 236396 -> 237680 bytes 08-build_abe-gdb/console.log.xz | Bin 52712 -> 52468 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3940 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2580 -> 2872 bytes 11-check_regression/console.log.xz | Bin 6736 -> 5660 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 40 +- 12-update_baseline/console.log | 40 +- 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/g++.log.xz | Bin 2920612 -> 2943368 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2563684 -> 2558640 bytes sumfiles/gcc.sum | 4504 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 958120 -> 942480 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230700 -> 230896 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473568 -> 472568 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 2422 insertions(+), 2450 deletions(-)