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 4b38d077b6 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards a1283d2014 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 2a1947f62b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards c6c9b17e3f 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards c5e14eac5f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 10c7579a58 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards d02370b37f 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards ca2a2cd98e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards dc148f0b1b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 3cd8e41ad1 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards ba77f0af90 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 1ce153b331 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 01fad9c3f7 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards b203ec2e16 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards afccf6acdd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 1a913165b7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards a6dd16cc85 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards b881f5be78 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 3c60a61690 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 7708ae4625 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 474e10dcf4 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 10d2caa01b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 7243b2bde4 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 3478d168a5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 0f931dc59e 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 0ec3c88484 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 1e7aa225dd 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards c51ca3c679 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 0cfe5d8299 125: onsuccess: #614: 1: Success after linux: 12 commits discards c09801c04e 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 071e036679 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 64b68629ba 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards fff6d4c141 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 12258c2ff2 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 6129fdce89 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 990d4f319e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards cad6d4d529 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 4586aa2a0e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards ac6293367b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 0cca833d80 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 431bcf1dda 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 44e10472e6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 66f7ed138c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards cb05491759 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 6885730d6d 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 0223e96185 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards d2b3319bbe 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards c1dad961d2 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 0a710190fd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 0e2470953b 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 3a475ef208 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 53d328f7fc 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 2bf38e0baf 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards c57d5c9008 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 2c5fa233bd 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards c49a21cef7 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 72bea92ced 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 84922f0a85 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards d7def8229c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards eb0a96ad75 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 337e2f148d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards fadabddf40 92: onsuccess: #575: 1: Success after linux: 34 commits discards fb1de5d122 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 4c46dce73f 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 13a8f2db30 89: onsuccess: #570: 1: Success after linux: 11 commits discards 24ce7756e1 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 3ab1745a0f 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 5b0a642889 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f4e44b29f7 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards bda3c5f2bc 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 193914c395 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards b8bb549ead 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 6311f60cc7 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 51fd3d6872 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 3de687a345 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 920fe272ed 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards b0837cda37 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 72170c58a5 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 26625cf5ea 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 6aa729d4a5 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards f94a53d6eb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 7ccc30d564 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 29fdcb24f9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 85669aa79d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 81b0e4cc80 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards e9709a942a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards a58621c35a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 4f75c3269e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 7d70374e17 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards c336daeff1 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 2495ee7014 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 4f5e340b0d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards b112338fd1 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 641214b9ec 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards a73db00852 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 3ee2b7650c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards da0d07466b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards f4cc0b6de5 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 3786c33ff3 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 9bbb363c41 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards e69723b0cb 53: onsuccess: #531: 1: Success after binutils: 12 commits new 59e8d710ff 53: onsuccess: #531: 1: Success after binutils: 12 commits new 498d219552 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new ffe1e621e9 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 886bc195ab 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 48d8781b3a 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 771a7d5973 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new ae8f0da706 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 3a745f94f5 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new ae628412a5 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 22bf333200 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new b058e4ad47 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4981b55623 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 24ada70878 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new c210b4dc31 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 43cfe799fb 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7bb8fedf1e 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new dcc1d35a89 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new ec7db68d86 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 57bc2799ab 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 74a13ed02c 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 805468d5f7 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new ce82e93213 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new ee0e7ba2c4 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new ee4ecbb319 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 89c4a3e8eb 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 378a30a49a 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 8ac3153eee 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 31160b6c26 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 471288c2e8 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 15cbdde84b 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 5493a40a1f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 0f0a91b800 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 14537aeace 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 60a40896be 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 1907c020a5 87: onsuccess: #567: 1: Success after binutils: 8 commits new beedc34dcc 88: onsuccess: #569: 1: Success after glibc: 10 commits new f529d5544c 89: onsuccess: #570: 1: Success after linux: 11 commits new 731a858fa2 90: onsuccess: #572: 1: Success after binutils: 15 commits new fb097dac96 91: onsuccess: #574: 1: Success after glibc: 3 commits new ca06fb3835 92: onsuccess: #575: 1: Success after linux: 34 commits new ad842dba91 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 707db10b5a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 1a56da9788 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new a488068809 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 48ec703e66 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new f4fe821951 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new fdf2938d97 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new a995ece949 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new bddb186229 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 7ff051b5b7 102: onsuccess: #586: 1: Success after binutils: 5 commits new b8a7bf0377 103: onsuccess: #589: 1: Success after binutils: 3 commits new 0ef6223e94 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 8c4c7373e7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 324b7f616c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 1bdaad0de9 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 4dcc6fad6a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 3043ef1458 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new e172642df6 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new caf885490a 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 1f02fb3dcf 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 436a490b06 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 3588dae320 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 41e0d84d0c 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 6739be0d82 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 4bc4352ba8 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 6f3f3073c7 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 56fa15e372 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new b121e603f4 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new ab230e10cf 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 9b0d89c081 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new bb64b1ced0 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 716fa3c47a 124: onsuccess: #612: 1: Success after binutils: 18 commits new cc55955407 125: onsuccess: #614: 1: Success after linux: 12 commits new 80d941ad6c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 1a5da410b0 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 675e0de874 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new b666b44956 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 096e1c2516 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 1dac1e972b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new b99a0f47df 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 58fe9c4907 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 8423cf423a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 500bf62188 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new f6b3ca5eff 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new d34d9d4093 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new c0eed13e99 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 09b529f500 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 898ca7560a 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 392cfad971 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new ae03c9e6c0 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 80fcd42f32 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new f707ee2b3a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new f13f6cb623 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 16b9821168 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f1d64c1764 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 5a0b864061 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 4101a035d9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 3e1623e592 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new c4463e7464 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 39ba4c3378 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new c67c81d928 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new e9f116a428 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/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 (4b38d077b6) \ 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 1736 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 53160 -> 53412 bytes 04-build_abe-gcc/console.log.xz | Bin 239588 -> 240576 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8996 -> 8992 bytes 07-build_abe-glibc/console.log.xz | Bin 238424 -> 237316 bytes 08-build_abe-gdb/console.log.xz | Bin 52464 -> 52300 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2244 -> 2212 bytes 11-check_regression/console.log.xz | Bin 16476 -> 17104 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 138 +- 11-check_regression/mail-body.txt | 225 +- 11-check_regression/results.compare | 187 +- 11-check_regression/results.compare2 | 3336 ++++++----- 11-check_regression/results.regressions | 135 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 227 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 135 +- sumfiles/gdb.log.xz | Bin 1714436 -> 1803940 bytes sumfiles/gdb.sum | 9212 +++++++++++++++++++++---------- 30 files changed, 8706 insertions(+), 5001 deletions(-)