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 5ce926e903 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 9bfab912d5 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 69ba976e33 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 3673c251da 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards eb92ddd7b7 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards f72f2fb7c9 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 5eafb7025a 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 65c22a2a31 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 0d525c774f 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 61b7cec124 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 1475d7edeb 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards b041e22aaf 104: onsuccess: #558: 1: Success after binutils: 3 commits discards cc18e90f9a 103: onsuccess: #555: 1: Success after binutils: 4 commits discards d8237d03c2 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards bd06319d82 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards e1c7b0b87d 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 42a69e7aae 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 8ddb7ce100 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 70bd1fb54f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards e4078ae753 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards adea842578 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards ec01095130 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 4d1b0d5030 93: onsuccess: #544: 1: Success after linux: 34 commits discards 271f9db73b 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 33b1d88dc3 91: onsuccess: #539: 1: Success after linux: 27 commits discards 046f3688cd 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 0a9e40a98d 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 4723ff44eb 88: onsuccess: #534: 1: Success after linux: 12 commits discards d1aabd5e34 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 5a43115128 86: onsuccess: #532: 1: Success after gcc: 16 commits discards e695881e8d 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 0e765b4db6 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 755bc377d6 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 8098a0ec1e 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 117d21213b 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 0f4186d35b 80: onsuccess: #524: 1: Success after linux: 9 commits discards 564447b225 79: onsuccess: #523: 1: Success after gcc: 25 commits discards e9f1d47443 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 16c5b7e2df 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards d4dfaf8934 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards dc2b10fbee 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 81940dd581 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 2eb42edae8 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 28b44f05bb 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards dd337f3b5b 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards b0456c3223 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards fa4c840607 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards bf1f59c4aa 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards ef9b4c2555 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards bcfbf18dad 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 787670bbc7 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards c5bc788a9f 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 27c49453ff 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 5f09e0c630 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 9474a63a0c 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards a709fb85e4 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards cac83532a9 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards a4b5395181 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards b6d176293b 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards c771d5086b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards f9237a2cfb 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 7893f4c39b 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 4f15e58cdb 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 64cd0e2608 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards e1f783d2e1 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 50eb9944b7 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 9cef91ee87 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 997df99aba 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards fe34ab8c17 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards eeb4135580 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards ba2094f48e 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 02a9ea4d9a 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards fb1f81500c 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 39b07ab2b5 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 31669fd566 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards df0e55be1b 40: onsuccess: #476: 1: Success after linux: 69 commits discards 8f6d778d32 39: onsuccess: #474: 1: Success after binutils: 8 commits discards d81a98f22e 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 103bd354e3 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 2739bbd438 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards a42810391c 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 2520d69bb2 34: onsuccess: #465: 1: Success after binutils: 11 commits discards e458c02f8b 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 00e8fa68cc 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards c7dabb0d76 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards a44c218c90 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 31ee56bcbd 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards b6463d0c6e 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 4d9c01242a 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 72075f88b2 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards b59cb44edf 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards c47e3aebf1 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards e4226c878c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards eb47ed0ad2 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards fe155277ac 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7e02ca83b2 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7715bc95b8 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d084e88388 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2018118ec5 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f44c8774da 16: onsuccess: 1: Successful build after binutils: 5 commits discards 4d9fa2a962 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bbaff0c7d3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4531025efa 16: onsuccess: 1: Successful build after binutils: 5 commits new 884dc88b4a 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a74166447f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 33d07bdf9b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 970e2e9593 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b9ecb1e33a 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e14f1b8a7e 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 03b11f8626 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 4a8385840e 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new eb2e6da578 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 0bc0172e7c 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new c2325b61c7 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new bbdd8b13f5 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 5ccbfe8a0d 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 01ee7edfe3 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 61c55c4905 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new a9c08de39d 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 5398e20e1c 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new b9d2ec262b 34: onsuccess: #465: 1: Success after binutils: 11 commits new ffc354ac6e 35: onsuccess: #467: 1: Success after glibc: 2 commits new aa7e4f76b0 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 2f34bd1676 37: onsuccess: #470: 1: Success after binutils: 3 commits new 7d8a075325 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 42fbbe1e72 39: onsuccess: #474: 1: Success after binutils: 8 commits new 5d22e2782f 40: onsuccess: #476: 1: Success after linux: 69 commits new 5a8cba9075 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 644b09fd68 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 1a566a3ad6 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 38bfbfa8c9 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 8b8f0d4d4b 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 55e3c514f5 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 1bc4e4c2fe 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 15ca51c184 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 318a0075d5 49: onsuccess: #487: 1: Success after binutils: 11 commits new e4def7174d 50: onsuccess: #490: 1: Success after binutils: 6 commits new df790ee186 51: onsuccess: #493: 1: Success after binutils: 13 commits new bfffd2e24a 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new de1eee47e3 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 43fab19680 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 49d81f4ac1 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new a5bfa6ea73 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 49e09993e3 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 7011379a51 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new bafd18d523 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 552ffbc5f8 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 1152916744 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 617c321d72 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 7a797a371a 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new cfebcf6649 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 153167afd5 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new b54cd5a3a5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 85a6b21ae9 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 938439ddf2 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 30ac7396ec 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 746c6ca7f8 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 7fb465f056 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 391d46d74f 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 3477a39b74 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new e806d9a4e9 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 4603f1e72e 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 119a6cef88 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new ce78998621 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 029d3e6826 78: onsuccess: #522: 1: Success after binutils: 10 commits new 19a285b109 79: onsuccess: #523: 1: Success after gcc: 25 commits new b194b06543 80: onsuccess: #524: 1: Success after linux: 9 commits new b130c6a456 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 1333d28202 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 8a8aa65031 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new da34225943 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new ed9bfc94b8 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new a8f69388d5 86: onsuccess: #532: 1: Success after gcc: 16 commits new 0bc515bfa8 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new b7b69ed80e 88: onsuccess: #534: 1: Success after linux: 12 commits new 77e19589f7 89: onsuccess: #536: 1: Success after binutils: 27 commits new ae2e1d9dd9 90: onsuccess: #538: 1: Success after glibc: 10 commits new 80fe657fca 91: onsuccess: #539: 1: Success after linux: 27 commits new be5bb4e00f 92: onsuccess: #543: 1: Success after glibc: 4 commits new f4eac2e328 93: onsuccess: #544: 1: Success after linux: 34 commits new 484afaced7 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 8b1f658f14 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 5de259c171 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 24f95eebe8 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 7f688257f8 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new cd0954bcd2 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 7124b19808 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 2e328cbd19 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 933b9dfbea 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 3dac332e52 103: onsuccess: #555: 1: Success after binutils: 4 commits new 6566caf6ab 104: onsuccess: #558: 1: Success after binutils: 3 commits new 47e16b38f9 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 699645e5c2 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 7ceaa6c927 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 37f8bd240b 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 114eb2bf81 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 5330d7b371 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new e2d42876bb 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 4d88e0d35e 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 2153130129 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 7198992f4f 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new d90882eaaa 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 30574ef027 116: onsuccess: #571: 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 (5ce926e903) \ 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 1676 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2712 bytes 03-build_abe-binutils/console.log.xz | Bin 52352 -> 52420 bytes 04-build_abe-gcc/console.log.xz | Bin 235428 -> 236144 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9512 -> 8856 bytes 07-build_abe-glibc/console.log.xz | Bin 234836 -> 235772 bytes 08-build_abe-gdb/console.log.xz | Bin 51828 -> 50848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2668 -> 3200 bytes 11-check_regression/console.log.xz | Bin 7376 -> 6184 bytes 11-check_regression/mail-body.txt | 43 - 11-check_regression/results.compare | 36 +- 11-check_regression/results.compare2 | 229 +- 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 | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2893832 -> 2920828 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2507164 -> 2527360 bytes sumfiles/gcc.sum | 4390 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 957780 -> 952996 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229160 -> 229456 bytes sumfiles/libgomp.sum | 27 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471232 -> 474112 bytes sumfiles/libstdc++.sum | 14 +- 38 files changed, 2415 insertions(+), 2633 deletions(-)