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 30574ef027 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards d90882eaaa 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 7198992f4f 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 2153130129 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 4d88e0d35e 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards e2d42876bb 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 5330d7b371 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 114eb2bf81 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 37f8bd240b 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 7ceaa6c927 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 699645e5c2 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 47e16b38f9 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 6566caf6ab 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 3dac332e52 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 933b9dfbea 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 2e328cbd19 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 7124b19808 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards cd0954bcd2 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 7f688257f8 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 24f95eebe8 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 5de259c171 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 8b1f658f14 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 484afaced7 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards f4eac2e328 93: onsuccess: #544: 1: Success after linux: 34 commits discards be5bb4e00f 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 80fe657fca 91: onsuccess: #539: 1: Success after linux: 27 commits discards ae2e1d9dd9 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 77e19589f7 89: onsuccess: #536: 1: Success after binutils: 27 commits discards b7b69ed80e 88: onsuccess: #534: 1: Success after linux: 12 commits discards 0bc515bfa8 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards a8f69388d5 86: onsuccess: #532: 1: Success after gcc: 16 commits discards ed9bfc94b8 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards da34225943 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 8a8aa65031 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 1333d28202 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards b130c6a456 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards b194b06543 80: onsuccess: #524: 1: Success after linux: 9 commits discards 19a285b109 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 029d3e6826 78: onsuccess: #522: 1: Success after binutils: 10 commits discards ce78998621 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 119a6cef88 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 4603f1e72e 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards e806d9a4e9 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 3477a39b74 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 391d46d74f 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 7fb465f056 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 746c6ca7f8 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 30ac7396ec 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 938439ddf2 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 85a6b21ae9 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards b54cd5a3a5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 153167afd5 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards cfebcf6649 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 7a797a371a 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 617c321d72 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 1152916744 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 552ffbc5f8 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards bafd18d523 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 7011379a51 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 49e09993e3 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards a5bfa6ea73 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 49d81f4ac1 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 43fab19680 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards de1eee47e3 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards bfffd2e24a 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards df790ee186 51: onsuccess: #493: 1: Success after binutils: 13 commits discards e4def7174d 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 318a0075d5 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 15ca51c184 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 1bc4e4c2fe 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 55e3c514f5 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 8b8f0d4d4b 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 38bfbfa8c9 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 1a566a3ad6 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 644b09fd68 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 5a8cba9075 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 5d22e2782f 40: onsuccess: #476: 1: Success after linux: 69 commits discards 42fbbe1e72 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 7d8a075325 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 2f34bd1676 37: onsuccess: #470: 1: Success after binutils: 3 commits discards aa7e4f76b0 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards ffc354ac6e 35: onsuccess: #467: 1: Success after glibc: 2 commits discards b9d2ec262b 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 5398e20e1c 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards a9c08de39d 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 61c55c4905 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 01ee7edfe3 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 5ccbfe8a0d 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards bbdd8b13f5 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards c2325b61c7 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 0bc0172e7c 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards eb2e6da578 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 4a8385840e 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 03b11f8626 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards e14f1b8a7e 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards b9ecb1e33a 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 970e2e9593 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 33d07bdf9b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a74166447f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 884dc88b4a 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4531025efa 16: onsuccess: 1: Successful build after binutils: 5 commits new 2bf01fa406 16: onsuccess: 1: Successful build after binutils: 5 commits new 4245b6d2e2 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a0a7653bec 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 504c013100 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae5800206e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b672b6455 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new dca6a68a32 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 0fe696cf7b 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new dd395d7bd5 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new cc24c7c78a 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 4292f42d70 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new f302697e11 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 4bde877fd3 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new a770e5fe56 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 67599b5113 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 59ce108d84 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 203d9f61f8 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new e15ae1b09c 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 203a4c9e55 34: onsuccess: #465: 1: Success after binutils: 11 commits new eb5e75deaa 35: onsuccess: #467: 1: Success after glibc: 2 commits new ef41879a89 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 07d5dcfee6 37: onsuccess: #470: 1: Success after binutils: 3 commits new 0b7e9fbacf 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new c4c93e6da7 39: onsuccess: #474: 1: Success after binutils: 8 commits new 8d32dfbe94 40: onsuccess: #476: 1: Success after linux: 69 commits new 19303caedb 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new dddbb9b12b 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 40cc2119c1 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 08c703bc29 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 32aa6bb006 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 7b3a8e9475 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 259cdf9ce4 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new a64d07965a 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 94c85c242c 49: onsuccess: #487: 1: Success after binutils: 11 commits new 19aea0c98a 50: onsuccess: #490: 1: Success after binutils: 6 commits new e7b3a4de8c 51: onsuccess: #493: 1: Success after binutils: 13 commits new a64db62503 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 20f1efa554 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new e69f2bc403 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new f21d7f17ec 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new a7c140f99b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 32ef0bcb15 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 434e205d08 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 760dced8d5 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 09232c751e 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 986647c2a9 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 520985ae90 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new d75ccbce76 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new d34cdaa0a3 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 9071634f2d 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new fa1cc1cf32 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 55eb52d9c7 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new c39e92919e 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 581a1095d6 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 4f5cb2141a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new cb5f8983a1 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new a2642cbb74 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 4d7f710d5b 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 654629e3fa 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new e0a37a869f 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 33f92c0de4 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 94b8372815 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 806028f442 78: onsuccess: #522: 1: Success after binutils: 10 commits new e728356cee 79: onsuccess: #523: 1: Success after gcc: 25 commits new e97f597707 80: onsuccess: #524: 1: Success after linux: 9 commits new 10d5a07739 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 500a89b0cc 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 682264d2b0 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 1dd88a3e95 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new abfc008156 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 38db37623e 86: onsuccess: #532: 1: Success after gcc: 16 commits new 8331a91749 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 6bb2614cb1 88: onsuccess: #534: 1: Success after linux: 12 commits new 1a4e025960 89: onsuccess: #536: 1: Success after binutils: 27 commits new ddfb2ca961 90: onsuccess: #538: 1: Success after glibc: 10 commits new 97a463a2b1 91: onsuccess: #539: 1: Success after linux: 27 commits new ef95c2db20 92: onsuccess: #543: 1: Success after glibc: 4 commits new 80e3ae876c 93: onsuccess: #544: 1: Success after linux: 34 commits new a91f9003f5 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 2b6fcf8ba5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new a9945164ae 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 298484fba5 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 9d031a8752 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new e8c0195748 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new e622e4812b 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 65c059c4b1 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 68cb1c7fa2 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new db35c832ab 103: onsuccess: #555: 1: Success after binutils: 4 commits new f6233f1c44 104: onsuccess: #558: 1: Success after binutils: 3 commits new 61901e4014 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 0c7ce886d1 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 8c5d13d584 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 7365798888 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 5c44b18f3d 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new de78422b6a 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 2dc9a22686 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 2149d494c5 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new b5ebe9ba4d 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new b36a027e49 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 83443b8a53 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new da9ead4c72 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new 6a778fd4e7 117: onsuccess: #572: 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 (30574ef027) \ 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 1688 -> 1876 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 52420 -> 54524 bytes 04-build_abe-gcc/console.log.xz | Bin 236144 -> 234112 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8856 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 235772 -> 236692 bytes 08-build_abe-gdb/console.log.xz | Bin 50848 -> 52180 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3200 -> 2612 bytes 11-check_regression/console.log.xz | Bin 6184 -> 5896 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 55 +- 12-update_baseline/console.log | 56 +- 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 2920828 -> 2882768 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2527360 -> 2525096 bytes sumfiles/gcc.sum | 4936 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 952996 -> 952848 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229456 -> 228596 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 474112 -> 470472 bytes sumfiles/libstdc++.sum | 12 +- 37 files changed, 2643 insertions(+), 2672 deletions(-)