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_gdb/master-arm in repository toolchain/ci/base-artifacts.
discards 36bdd7eb49 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 4b79ce8a09 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards a3529a00b1 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 954658d918 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 25ca9dc340 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 7429bbe90e 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 495deb9955 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 7e8350ed19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards ce6afb7a90 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards f59d32eeea 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 8f5bcb2cdb 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 780d841699 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 51a1c3bce5 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards d97330c9d6 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards c142a08264 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 8df4275e9e 92: onsuccess: #575: 1: Success after linux: 34 commits discards 56404bda13 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 46edf05259 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 3e1d86bf28 89: onsuccess: #570: 1: Success after linux: 11 commits discards d9a8d91029 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 74e94904c2 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 99dcf97145 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 5f87a3c9bc 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards ea0fcb6f63 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 31a72aca3a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards b327b4b92e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 06bd4c0250 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards e1c2f4ea3f 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 04e5573a3a 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 3875d8918b 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards d0156a255c 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 4af6444f9e 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 733726095b 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 1190b00d1c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 600950e063 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 97dd94fd41 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 6adc9073f9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 22ef809bfb 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards bcd630e1b2 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 513758380b 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 4404a9a057 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards c63e232f4c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 3f3b2a9da6 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 4d2419c12b 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards d6c98c7274 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards f3c0c223cb 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards bf669c3527 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards de857ee181 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 9a87ddc45b 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 97473bb138 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 3da1fb3cbc 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards be2d1d8787 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards ea40d9ed7b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 3299e19375 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 169d0130e4 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 2819bb557d 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 84238ea724 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 2f581cbfce 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 1ad35f0736 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 00a05ed7bc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards d93182586f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 7f22e8f203 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 247cfe95f2 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 8b1b807366 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 8dae927960 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 6dc24c3733 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards e846ccb5e3 41: onsuccess: #514: 1: Success after linux: 64 commits discards f306ee8053 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 760ad34f29 39: onsuccess: #511: 1: Success after binutils: 8 commits discards cf52af0506 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 1563b9c851 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards db418681ed 36: onsuccess: #505: 1: Success after glibc: 3 commits discards cb9a98c86a 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 308ddd570a 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards f101e78d5d 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 234d81bf5b 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 51f63a324a 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 1e33c13ee9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards fa00a7e1df 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 09aaabba77 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 96035bc2e4 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 9e712a6c6d 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards a44a178fd9 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards f66e4f08a0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards ec53d3d88d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e2188a4b54 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards a259b3e853 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 41a230dc9d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0a6f04bee1 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1cec99ab96 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 61e0ce5440 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ebe95edac8 16: onsuccess: 1: Successful build after binutils: 4 commits discards c2da457e6c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 28b1e7cfec 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ec804e0b0d 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5134493b6 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5edfc42f2b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40b5deb2df 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e863e8c536 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fa4a640749 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9c68dfa7de 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cc4f39a23c 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 36b95f2a69 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 69ed808efa 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9dd5d35ea3 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 713c59108f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e3940b400 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fbeb692901 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9296b48aa9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5439856d79 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5fa12a764 16: onsuccess: 1: Successful build after binutils: 4 commits new c166289066 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7bf6175d66 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5a58cd66cc 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45058311d9 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f81e4f9caa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50eb77d410 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new b5ed8468c6 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5b490c5a82 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 8be5b1effa 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 52de82f9db 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 0a30f713d8 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 33c9a812fa 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new df8a006f6c 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a0a79c33c5 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 1f7a28ac47 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 751d16c613 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 9e23ef111b 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new ae53fc446d 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new cc65699a93 35: onsuccess: #503: 1: Success after binutils: 11 commits new e5fd55e5eb 36: onsuccess: #505: 1: Success after glibc: 3 commits new 48bce7cd1d 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new fa4de52c0a 38: onsuccess: #508: 1: Success after binutils: 3 commits new 71ba9f66bc 39: onsuccess: #511: 1: Success after binutils: 8 commits new 8e0b9ba28d 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 2066cba80d 41: onsuccess: #514: 1: Success after linux: 64 commits new 0d0f247b1c 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 76dc2b55db 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new be011e853a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 5da6d10f34 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 79d8eac418 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new b121a93594 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 2f294dbc58 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new b5e8a7f26f 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 13cc3ea22e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 480b2a41f2 51: onsuccess: #525: 1: Success after binutils: 8 commits new ceaec79148 52: onsuccess: #528: 1: Success after binutils: 8 commits new ac7367f427 53: onsuccess: #531: 1: Success after binutils: 12 commits new 422e84d29a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new b96dee6e3a 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new b350f5abe6 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 9e94cad1cf 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new eb962c875f 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 1459ee8e2f 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 9bd0b32d6d 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new f2da2285a4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 6fe6103c1a 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new c592ae3551 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 5d93d24849 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 57762032cd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new f37f0006c0 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e5b09a01b1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 4aa6da2055 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new b9f5146236 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 6811b2353b 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 7959fab7d9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new d2bc750403 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 4476589738 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 4f9075ccbf 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 6a9277b000 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 7c0db87b2a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 0ee12b00b8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new d5b1c68dc0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 23a2e44bf0 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 489f47bc01 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new f7263bc448 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new da52189e18 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 56c2be42c9 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new eba248d942 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 71b477fb8b 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new b09efb9075 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 2c56672076 87: onsuccess: #567: 1: Success after binutils: 8 commits new 4c0d27f88e 88: onsuccess: #569: 1: Success after glibc: 10 commits new d0374efbc6 89: onsuccess: #570: 1: Success after linux: 11 commits new 9b6cbe95f6 90: onsuccess: #572: 1: Success after binutils: 15 commits new 55b05114cd 91: onsuccess: #574: 1: Success after glibc: 3 commits new e912af799b 92: onsuccess: #575: 1: Success after linux: 34 commits new b498f589c8 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 9e37d22a2a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 929f839c27 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 8b9bb52389 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 09d7fc3674 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 89f1d325f9 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new cb26254986 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 1d95a0b1f7 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 70e0aaa658 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new fb001163cc 102: onsuccess: #586: 1: Success after binutils: 5 commits new a813ee454d 103: onsuccess: #589: 1: Success after binutils: 3 commits new 8e5cabc6d0 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 1a8da83d40 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new dc8c26ee60 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 48972e4794 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 668ba4031a 108: onsuccess: #595: 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 (36bdd7eb49) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 53296 -> 53412 bytes 04-build_abe-gcc/console.log.xz | Bin 236832 -> 236148 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9200 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 236028 -> 235844 bytes 08-build_abe-gdb/console.log.xz | Bin 50916 -> 51736 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2624 -> 2276 bytes 11-check_regression/console.log.xz | Bin 11888 -> 15036 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 132 +- 11-check_regression/mail-body.txt | 213 +- 11-check_regression/results.compare | 162 +- 11-check_regression/results.compare2 | 5066 ++++++++++--------- 11-check_regression/results.regressions | 168 +- 12-update_baseline/console.log | 64 +- 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 | 215 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 168 +- sumfiles/gdb.log.xz | Bin 1728584 -> 1790664 bytes sumfiles/gdb.sum | 8212 ++++++++++++++----------------- 30 files changed, 7197 insertions(+), 7251 deletions(-)