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 6a778fd4e7 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards da9ead4c72 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards 83443b8a53 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards b36a027e49 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards b5ebe9ba4d 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 2149d494c5 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 2dc9a22686 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards de78422b6a 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 5c44b18f3d 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 7365798888 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 8c5d13d584 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 0c7ce886d1 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 61901e4014 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards f6233f1c44 104: onsuccess: #558: 1: Success after binutils: 3 commits discards db35c832ab 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 68cb1c7fa2 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 65c059c4b1 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards e622e4812b 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards e8c0195748 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 9d031a8752 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 298484fba5 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards a9945164ae 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 2b6fcf8ba5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards a91f9003f5 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 80e3ae876c 93: onsuccess: #544: 1: Success after linux: 34 commits discards ef95c2db20 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 97a463a2b1 91: onsuccess: #539: 1: Success after linux: 27 commits discards ddfb2ca961 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 1a4e025960 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 6bb2614cb1 88: onsuccess: #534: 1: Success after linux: 12 commits discards 8331a91749 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 38db37623e 86: onsuccess: #532: 1: Success after gcc: 16 commits discards abfc008156 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 1dd88a3e95 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 682264d2b0 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 500a89b0cc 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 10d5a07739 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards e97f597707 80: onsuccess: #524: 1: Success after linux: 9 commits discards e728356cee 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 806028f442 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 94b8372815 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 33f92c0de4 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards e0a37a869f 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 654629e3fa 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 4d7f710d5b 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards a2642cbb74 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards cb5f8983a1 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 4f5cb2141a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 581a1095d6 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards c39e92919e 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 55eb52d9c7 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards fa1cc1cf32 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 9071634f2d 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards d34cdaa0a3 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards d75ccbce76 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 520985ae90 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 986647c2a9 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 09232c751e 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 760dced8d5 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 434e205d08 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 32ef0bcb15 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards a7c140f99b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards f21d7f17ec 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards e69f2bc403 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 20f1efa554 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards a64db62503 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards e7b3a4de8c 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 19aea0c98a 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 94c85c242c 49: onsuccess: #487: 1: Success after binutils: 11 commits discards a64d07965a 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 259cdf9ce4 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 7b3a8e9475 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 32aa6bb006 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 08c703bc29 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 40cc2119c1 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards dddbb9b12b 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 19303caedb 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 8d32dfbe94 40: onsuccess: #476: 1: Success after linux: 69 commits discards c4c93e6da7 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 0b7e9fbacf 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 07d5dcfee6 37: onsuccess: #470: 1: Success after binutils: 3 commits discards ef41879a89 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards eb5e75deaa 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 203a4c9e55 34: onsuccess: #465: 1: Success after binutils: 11 commits discards e15ae1b09c 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 203d9f61f8 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 59ce108d84 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 67599b5113 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards a770e5fe56 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 4bde877fd3 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards f302697e11 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 4292f42d70 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards cc24c7c78a 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards dd395d7bd5 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 0fe696cf7b 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards dca6a68a32 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 3b672b6455 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards ae5800206e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 504c013100 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a0a7653bec 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4245b6d2e2 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 796a26d566 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2bba199435 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d18eb26f58 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e5c3355bbc 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ed5d69170 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new bf6ea693d6 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new b8320ede00 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new d7486b1beb 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 405456ac88 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new f2c694be6d 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 91df006a4c 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 150631f7b7 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 99c8444b57 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 999bdc6d0d 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new ecb939aed6 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new b223d1ce26 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 650c0a60bf 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 2dbe3a0e57 34: onsuccess: #465: 1: Success after binutils: 11 commits new 5c12c02a97 35: onsuccess: #467: 1: Success after glibc: 2 commits new 76c5f5dfbf 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 2cb07adb3c 37: onsuccess: #470: 1: Success after binutils: 3 commits new 346ac59e1e 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new acc0073b11 39: onsuccess: #474: 1: Success after binutils: 8 commits new bd9015ab55 40: onsuccess: #476: 1: Success after linux: 69 commits new 8863a2712d 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 135cc23f1b 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 6c491a3c33 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new e5747a09e8 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 5e23ce7f62 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 7f5700e41c 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new b052bf6a3e 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 6c20d4b74e 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 050346f4b1 49: onsuccess: #487: 1: Success after binutils: 11 commits new ded0a807c6 50: onsuccess: #490: 1: Success after binutils: 6 commits new 59989c4785 51: onsuccess: #493: 1: Success after binutils: 13 commits new 4cc08950b3 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 06649526b4 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new e5f90b25dd 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 4007ae3bc7 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 293083b56e 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new bcf3747409 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 3a3c47412c 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 43f0e01f07 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new eda8868b67 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 36f530d987 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 5e05f2dba0 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new a7fa1866f5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new e64058cfca 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 20bf03af69 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 973e86eae3 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new d236f0ce83 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 8b4e0a38a4 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 557a8cda85 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 1ceec8c589 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 8a63b3e55e 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 409dfaa869 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new a302c11666 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 25333333b3 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 799a5158ab 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 9307964bfa 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 2b98f6476c 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new faf8dbfa38 78: onsuccess: #522: 1: Success after binutils: 10 commits new af648c0b23 79: onsuccess: #523: 1: Success after gcc: 25 commits new 933a249f96 80: onsuccess: #524: 1: Success after linux: 9 commits new 5bfb8602fc 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new b0d4828d80 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 08a1a33dc2 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 8224dde6a7 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new fcbf26ed2a 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 6145571234 86: onsuccess: #532: 1: Success after gcc: 16 commits new 7de0fa8034 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 2b24e91981 88: onsuccess: #534: 1: Success after linux: 12 commits new 62b6646f9c 89: onsuccess: #536: 1: Success after binutils: 27 commits new 4c4a3ad213 90: onsuccess: #538: 1: Success after glibc: 10 commits new 10c0662cbd 91: onsuccess: #539: 1: Success after linux: 27 commits new 0fcac0c9b5 92: onsuccess: #543: 1: Success after glibc: 4 commits new 25fe91a626 93: onsuccess: #544: 1: Success after linux: 34 commits new b4651beec6 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 42a77fdf60 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 8cdf239a13 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 84da073c59 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 62ece4718a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 245f04b90a 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new cb471a2ea8 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 0654d27f91 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 1838aeeb38 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 9256529e11 103: onsuccess: #555: 1: Success after binutils: 4 commits new 193487de6e 104: onsuccess: #558: 1: Success after binutils: 3 commits new 70ac232c63 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 9f3bcd6ee6 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 4520638013 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 344e61f32a 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 4097f6df8c 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 484dbd3145 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 296537c1c1 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 5df1719d96 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new b4b3c5200d 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 4273118399 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 8c3319530c 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 95cdbf2861 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new 3bd8a48938 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new ad9f012f0d 118: onsuccess: #573: 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 (6a778fd4e7) \ 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 1876 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2712 bytes 03-build_abe-binutils/console.log.xz | Bin 54524 -> 53868 bytes 04-build_abe-gcc/console.log.xz | Bin 234112 -> 232708 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 236692 -> 235132 bytes 08-build_abe-gdb/console.log.xz | Bin 52180 -> 51996 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2392 bytes 11-check_regression/console.log.xz | Bin 5896 -> 5584 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 19 +- 12-update_baseline/console.log | 62 +- 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 2882768 -> 2907768 bytes sumfiles/g++.sum | 124 +- sumfiles/gcc.log.xz | Bin 2525096 -> 2529016 bytes sumfiles/gcc.sum | 3982 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 952848 -> 950384 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 228596 -> 229616 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470472 -> 474560 bytes sumfiles/libstdc++.sum | 12 +- 37 files changed, 2159 insertions(+), 2170 deletions(-)