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 d96e4e930089 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 7de13d88bffb 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] discards c7a9861db893 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] discards 91eaa0827902 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] discards 244f6a4c30f3 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] discards 51c4919be664 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] discards 6c9f80f83292 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards 1b511ded5234 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards f708c8fc7c65 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 1ae2173e4d8e 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 553daf2e0b74 125: onsuccess: #614: 1: Success after linux: 12 commits discards 2a2c49cae7de 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 99e335092f7e 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 53d6f8b751d9 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 53562d5859c7 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards 7bcb32b4aa58 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards 84b6d57a7bd4 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 7e7ca08172c4 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards db27b8c3e792 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] discards b59ede511840 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 8e339972c2ea 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 8e5540e91492 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards d5eea3068d4f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards 7a14bb6ad21b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] discards c6591c6404df 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] discards c3a367d6f71d 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards 0c35877f5f81 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 786cae989a20 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards e7d827514da3 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards 672e2675c779 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards d9cfebf580a8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards 86f3b763e287 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards 34cd18e2bbd0 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 49594710a3de 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 0856c9e184e0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] discards cdad1092d62e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] discards 9ead7b68e2bf 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards 19ff8b9611fe 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards 92a693f716b0 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards 20dbff9c074f 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 67c9e64f20fb 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 653089565aae 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 87c2bed3cc31 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards ecd17cae8f6a 92: onsuccess: #575: 1: Success after linux: 34 commits discards a329035bbba2 91: onsuccess: #574: 1: Success after glibc: 3 commits discards add6f74297d9 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 05c102d35d8d 89: onsuccess: #570: 1: Success after linux: 11 commits discards 1873ad06f249 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 0c1252efd1f4 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 10994b80fd3d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 92d6c94cf5a6 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards fa5bbd884918 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 0e81c0c96be5 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards be75c4a0c439 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards bba975f6ed13 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 583fa0d47248 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards ef38f646fa2f 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards a390ffe79fc7 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 19221bab8853 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards a7cbc3a33b81 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 572b801c58ed 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] discards 58ed8ca16415 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards d0c4dd318cc6 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 0e0f6c769bb9 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards e02597c6f1d5 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 489e768327e9 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 556840fb8132 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 65d68d515887 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 5c3efcd717c1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards c888d10f92e9 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards ee9c3f4a2891 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards e89583188f8f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards c03c9e3864b1 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 824ea91eb062 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards dde76c6025fd 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards 80dc3c3ea738 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards b51ca7632b43 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 67690530074d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] discards 6d6511dab2b4 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] discards c5d4c37456ea 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards 9a42b4c4b1e7 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 071f929028ab 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards 71cc52ea2486 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 8d181fd8b35a 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 9512b8cc611f 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 5f6c7268f29d 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] discards b1af73b03f1e 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] discards 46ad005ca1f3 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] discards 1b602ab1d82b 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] discards c4404065262c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 4b1e8da25d01 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] discards 404219d7ee00 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 19f3746a766a 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards a8aadc755ed7 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards a3c1f6c45576 41: onsuccess: #514: 1: Success after linux: 64 commits discards 46314d258948 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] discards 183064892734 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 53627dfaa1a5 38: onsuccess: #508: 1: Success after binutils: 3 commits discards d3415be2dc34 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb6 [...] discards c9e6db9a53ca 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 40e3028a4fd9 35: onsuccess: #503: 1: Success after binutils: 11 commits new d161a5596912 35: onsuccess: #503: 1: Success after binutils: 11 commits new 2fc8337749bd 36: onsuccess: #505: 1: Success after glibc: 3 commits new bf1734e781dc 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb6 [...] new 44b2b5604120 38: onsuccess: #508: 1: Success after binutils: 3 commits new 563bac594d7c 39: onsuccess: #511: 1: Success after binutils: 8 commits new c824af99d162 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] new 8c35383a45ce 41: onsuccess: #514: 1: Success after linux: 64 commits new ae31c907fb95 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new f7d949c947ef 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new a30676c5ccb7 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new ceef3ad94a9f 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] new 984734f1465c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new a4d2d66c1528 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] new 540d891072d4 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] new 8519bf9803c4 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] new 1a971bb4cc12 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] new 392353d46f6d 51: onsuccess: #525: 1: Success after binutils: 8 commits new ffda9b5348cb 52: onsuccess: #528: 1: Success after binutils: 8 commits new d9b542f010ec 53: onsuccess: #531: 1: Success after binutils: 12 commits new 7ba6bc8b9b11 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 4cdf73f3a6ab 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new d9e628466be0 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 397cc64cf345 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] new 10db658e1444 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new a7e91963aa34 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new aed7af02a037 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 7277531631d1 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new c9a3bd2e91b9 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 62fa684fa02f 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new fab0ce2efcdd 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 34fe4ccf6a41 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 0aebc60734aa 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 36bc17e0608c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 30de51523ea7 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new d54f440e3ad0 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 204d87546ef6 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 7731dee4f4c4 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new aedab17ee50f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new a4f60299b6a9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 84d05351f060 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 9b9c8b1c7c73 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] new 3c9815e7b73e 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new c015185c1b13 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new c0debca8eeaa 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new d6c33bc0edae 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 9ccc36f13d45 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 23dc3a8633a1 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 7861ba2ac9f8 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 7d1fd98b6620 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 699946e3553c 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 154a51773817 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 385811eb0648 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 0db1ab241500 87: onsuccess: #567: 1: Success after binutils: 8 commits new f0624cb245a0 88: onsuccess: #569: 1: Success after glibc: 10 commits new f3e79a104148 89: onsuccess: #570: 1: Success after linux: 11 commits new faf5c7854dc1 90: onsuccess: #572: 1: Success after binutils: 15 commits new 9d4638671f6a 91: onsuccess: #574: 1: Success after glibc: 3 commits new b7cf17fdb2ea 92: onsuccess: #575: 1: Success after linux: 34 commits new e25944fa9901 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 1433d41f6b2a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 2c4a16083f69 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 6844351407f5 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 76772c7489bc 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new 7102b59de623 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new b937f2018907 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new 7c7894cce3d5 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] new eeb36e1d6e00 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] new c599f763a171 102: onsuccess: #586: 1: Success after binutils: 5 commits new fb6e7c0d637f 103: onsuccess: #589: 1: Success after binutils: 3 commits new ff0696761325 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new d89a3e7e413c 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new 3638ed342953 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new 8680788cc41c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 12bf965ac8c5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new e044c3584ec0 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new 1bd72757639b 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new f3c92060cd6b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] new 5f8cd20c99af 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] new a966505bdf8f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new 624af24346be 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new 0f8d2141dda2 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new f00344563c7a 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 77681ec86e5d 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] new 699f03773739 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new e258cb744f6e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new ee0931668b22 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 4d90aeb070b8 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 6dbd90036732 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new e034254441c7 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 274724f40bc0 124: onsuccess: #612: 1: Success after binutils: 18 commits new 8ae99bc6710f 125: onsuccess: #614: 1: Success after linux: 12 commits new 23ccda65691c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 8059d90f4fa7 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new c871033ebd89 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 257e3fc88fab 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new 74b63e201b98 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] new 15e1f92c5445 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] new 99799456f576 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] new a27bebb0162c 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] new 1b2bed4710e1 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] new 9f24fa81e2b2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 8d1bad0d12da 136: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...]
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 (d96e4e930089) \ 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 1764 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 53668 -> 55168 bytes 04-build_abe-gcc/console.log.xz | Bin 235324 -> 237972 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9852 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 236396 -> 236912 bytes 08-build_abe-gdb/console.log.xz | Bin 52324 -> 53064 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2656 -> 2696 bytes 11-check_regression/console.log.xz | Bin 11792 -> 13500 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 58 +- 11-check_regression/mail-body.txt | 209 +- 11-check_regression/results.compare | 110 +- 11-check_regression/results.compare2 | 4173 +++++++++++------ 11-check_regression/results.regressions | 110 +- 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 | 211 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 110 +- sumfiles/gdb.log.xz | Bin 1850740 -> 1830168 bytes sumfiles/gdb.sum | 7784 +++++++++++++++++++++---------- 30 files changed, 8481 insertions(+), 4370 deletions(-)