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 480016b787 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 13bbc495ef 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 82becc540f 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 182fecce90 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards f14d7a33d2 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 90ccbe1eb2 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 0eddb3bfac 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 4813385fd8 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards f2a49f87d3 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 8f6ef44e84 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 73585c912b 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 0d2016b98f 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards f63a6f1a91 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 7a299a6bc6 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 6e0af4c673 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards acd6198628 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 84803e7e3d 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 4e9ec31548 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 61e4535ccb 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 1313fc1caa 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 214cbdd0ac 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards b2e646185c 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 4d06f65d20 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 5038e7f177 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 747c8665bd 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards a0e9c1da0d 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards acefc35129 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 3be4fb5bef 125: onsuccess: #614: 1: Success after linux: 12 commits discards cda5411064 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 43e5596ea2 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 0d04cd8be0 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 7748a21e76 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards b06d4ecfe7 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 44c92d91fd 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 9f58a7c791 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards d498e564e1 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 30877290f1 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 3a5efd33a8 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 5a75dd415b 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 5eb7136cc8 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 3a07066e08 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards f6a70b6d27 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 730db84a96 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 227d0d0a10 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 5edbce8d8d 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards cfc7c1a0e4 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 9a0c56cce6 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards fc235b1e75 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards e57bed47e0 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards aa9f18a636 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 2bca33730f 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 9e47e3ce21 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 6dd713626e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 94f4fe9ebe 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 25c5b5e276 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 3501d2bf9c 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 500121151e 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 63dac54772 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 7824db6a86 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards fcc37e5bfa 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 113e66f075 92: onsuccess: #575: 1: Success after linux: 34 commits discards c608fa157a 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 98124ebc80 90: onsuccess: #572: 1: Success after binutils: 15 commits discards d289ec1b1d 89: onsuccess: #570: 1: Success after linux: 11 commits discards 43efe0159a 88: onsuccess: #569: 1: Success after glibc: 10 commits discards c7b226943d 87: onsuccess: #567: 1: Success after binutils: 8 commits discards fd6a9242ce 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards eb83e474a4 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 00b50b63f2 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 8aabd6c3d6 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 510185aa0a 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards a853b6cfb3 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 4cd900c6d1 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards b6685405dc 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 306b8ffcf0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 83d1035acf 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 759c4f73f0 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 77f1f1ed76 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards a53d2b2523 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards b4b3c04b4e 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 1e9b49a92c 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 804374d76a 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards c4954641b9 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards fe084a7e81 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards e66af7d451 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 0358417992 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards d7bc287acb 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 986a44facb 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 248973556c 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 0e2bf1fd40 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 4a4de70c38 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 9c96249817 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 9cc7366282 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 788af026da 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 9365b429df 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards bb11e33363 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 09b97c246c 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 237bde52ad 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards ab7da74fa3 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 40fff3fb4c 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 3601dc19bf 52: onsuccess: #528: 1: Success after binutils: 8 commits new d790ab1deb 52: onsuccess: #528: 1: Success after binutils: 8 commits new e69723b0cb 53: onsuccess: #531: 1: Success after binutils: 12 commits new 9bbb363c41 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 3786c33ff3 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new f4cc0b6de5 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new da0d07466b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 3ee2b7650c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new a73db00852 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 641214b9ec 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new b112338fd1 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 4f5e340b0d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 2495ee7014 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new c336daeff1 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 7d70374e17 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 4f75c3269e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new a58621c35a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e9709a942a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 81b0e4cc80 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 85669aa79d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 29fdcb24f9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 7ccc30d564 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new f94a53d6eb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 6aa729d4a5 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 26625cf5ea 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 72170c58a5 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new b0837cda37 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 920fe272ed 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 3de687a345 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 51fd3d6872 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 6311f60cc7 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new b8bb549ead 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 193914c395 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new bda3c5f2bc 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new f4e44b29f7 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 5b0a642889 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 3ab1745a0f 87: onsuccess: #567: 1: Success after binutils: 8 commits new 24ce7756e1 88: onsuccess: #569: 1: Success after glibc: 10 commits new 13a8f2db30 89: onsuccess: #570: 1: Success after linux: 11 commits new 4c46dce73f 90: onsuccess: #572: 1: Success after binutils: 15 commits new fb1de5d122 91: onsuccess: #574: 1: Success after glibc: 3 commits new fadabddf40 92: onsuccess: #575: 1: Success after linux: 34 commits new 337e2f148d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new eb0a96ad75 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new d7def8229c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 84922f0a85 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 72bea92ced 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new c49a21cef7 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 2c5fa233bd 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new c57d5c9008 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 2bf38e0baf 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 53d328f7fc 102: onsuccess: #586: 1: Success after binutils: 5 commits new 3a475ef208 103: onsuccess: #589: 1: Success after binutils: 3 commits new 0e2470953b 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 0a710190fd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new c1dad961d2 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new d2b3319bbe 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 0223e96185 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 6885730d6d 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new cb05491759 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 66f7ed138c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 44e10472e6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 431bcf1dda 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 0cca833d80 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new ac6293367b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 4586aa2a0e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new cad6d4d529 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 990d4f319e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 6129fdce89 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 12258c2ff2 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new fff6d4c141 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 64b68629ba 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 071e036679 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new c09801c04e 124: onsuccess: #612: 1: Success after binutils: 18 commits new 0cfe5d8299 125: onsuccess: #614: 1: Success after linux: 12 commits new c51ca3c679 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 1e7aa225dd 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 0ec3c88484 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 0f931dc59e 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 3478d168a5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 7243b2bde4 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 10d2caa01b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 474e10dcf4 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 7708ae4625 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 3c60a61690 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new b881f5be78 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new a6dd16cc85 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 1a913165b7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new afccf6acdd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new b203ec2e16 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 01fad9c3f7 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 1ce153b331 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new ba77f0af90 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 3cd8e41ad1 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new dc148f0b1b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new ca2a2cd98e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new d02370b37f 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 10c7579a58 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new c5e14eac5f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new c6c9b17e3f 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 2a1947f62b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new a1283d2014 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 4b38d077b6 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...]

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 (480016b787) \ 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 1688 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 53496 -> 53160 bytes 04-build_abe-gcc/console.log.xz | Bin 238124 -> 239588 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8368 -> 8996 bytes 07-build_abe-glibc/console.log.xz | Bin 236528 -> 238424 bytes 08-build_abe-gdb/console.log.xz | Bin 52268 -> 52464 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2328 -> 2244 bytes 11-check_regression/console.log.xz | Bin 11260 -> 16476 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 48 +- 11-check_regression/mail-body.txt | 186 +- 11-check_regression/results.compare | 98 +- 11-check_regression/results.compare2 | 2834 +++++++++- 11-check_regression/results.regressions | 98 +- 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 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 188 +- mail/mail-subject.txt | 2 +- manifest.sh | 37 +- results | 98 +- sumfiles/gdb.log.xz | Bin 1778960 -> 1714436 bytes sumfiles/gdb.sum | 9066 ++++++++++++++----------------- 31 files changed, 7154 insertions(+), 5581 deletions(-)