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-aarch64 in repository toolchain/ci/base-artifacts.
discards fd9d421ae6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards c54e836966 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards e050d37966 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 91e9d0df2e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 4a615b9397 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards f6cea5a500 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 8a00005727 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 080525b284 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards e7f8efcee5 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 1f1f9c8334 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards ca21b8d614 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 944a2f0550 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 210d357159 91: onsuccess: #870: 1: Success after binutils: 5 commits discards b92e0a7854 90: onsuccess: #867: 1: Success after binutils: 4 commits discards aacde7d407 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 56850db3b1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards d729771c05 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 082ebaa733 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards cf59a34cb3 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 4f5a103149 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards c794f38c3b 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards f4872e2a96 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 537691bc5a 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards ee16fabed9 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 75a2999b12 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 6d9fd679d5 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 5c890e2443 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 4b417e87ed 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards f6ac0e6a64 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 57f44d123d 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 870779c9ab 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 2b9f2c0cc0 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 23b3be85b5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 0247f62103 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards a9ce0a7424 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards c65cd87cdf 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards c1eff0722c 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards cc18c11327 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 1ab82a2136 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 052b87fef1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 9e9ac5adc4 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 7951b0663b 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards f192488dde 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards bcfa2c4ff4 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards b48f656bb4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 28a8e3a8ed 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards b291b2bb91 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards c37337a3d1 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 9931a9cd76 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 7768251f14 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards ecd1077eb9 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 766871ca0b 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards c9a3e67b4c 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5ee9f7c7f1 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards b8b0373ba7 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards a9680d427a 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards bd1415ed79 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards e9514c6dfc 46: onsuccess: #818: 1: Success after binutils: 10 commits discards cb3c68f51d 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 0dc3526f61 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 2a64d677bc 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 0ef9cf7518 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards ff59dc4453 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 9591d0bc79 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards c83003eed9 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 54befb6c15 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 32a2b9e059 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 193a409445 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards d3c49a38b1 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 9b553a4ee9 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 3113c1ef8e 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards c41b541130 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards d800f5026e 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards 8de8924fcf 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 0d39790fb2 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards 27cd634760 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 89ea0ba10e 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards 3299c3632c 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards a7dc0be315 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 41850eb8eb 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 63f6f67aba 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards d4001cf451 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards b5ecde8d03 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards c12eb70a37 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 4bead6a1f1 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e71a259631 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 52f34f049a 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0d4a21b739 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4e34bdd4a7 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bbbb9f88fc 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1d0fd60368 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 922701312c 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd92aab549 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2cffaea3bc 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b67b9b9292 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c24a80f7e3 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 81826cdbbb 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3da6f87c58 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8311cfe71c 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b9984df9f3 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c7ae72253f 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 65b9bb14c2 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 1ebc9239a2 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f0ee9ce0c5 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 2c7403c80e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c15b46172f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 51ad7fcf21 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fdc4c57ea7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e0f323a8d0 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5f38684789 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0282c281fb 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b1907b5356 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb1f6195c9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad274aee4b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0103ef5058 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a76276b89d 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eaa1138a16 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7e13ae8dba 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f4412a5b52 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 6516ad2b07 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new c72cd118ca 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new 43d0b5c066 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new 5cfaae1a96 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 39664eac68 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new f841098c31 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new def9b557ba 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new d340311c85 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 14f35064ff 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new ed7d70ad4c 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 73f8f47f1f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new 713230eb65 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 22e00c71c0 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new da4736c897 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 09d22cc188 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 381616ce7b 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new b8db35566f 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 4ffd1ae34e 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 319ec36513 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 169b4b3f7a 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 2454b590a4 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new ce25736efa 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 1fd8b4329d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new bfbe9cdd36 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 5b2b02033b 45: onsuccess: #815: 1: Success after binutils: 6 commits new ac6949f256 46: onsuccess: #818: 1: Success after binutils: 10 commits new 8ea1b962f3 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 786980a2e4 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 32777bbac2 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 0691a818c5 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 00607c35a3 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 173af1004f 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 21e3377857 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 9d1968ca3d 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 96483ac007 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 7982579770 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 8cdc6511d7 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 02d5e3ce47 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 09f70a3c15 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 3a41c7e4f9 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 945d81eb67 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 9f77b18d2f 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 56cd414b81 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new ba9e674ebe 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new fef7116ad7 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 78336dddd7 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 3da1104c6d 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 468865250c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 2d546a01cb 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new ae63ff2024 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 1bd91ffc72 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 86098d6592 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 8df28e5cfc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 5dfc6c4055 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new d5ad105be8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 7f86bc7fbb 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new e0079abaa0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new d2a78a7d5d 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new e57a5d2ece 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new d25866320f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 30caf88efa 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new f8708d5a45 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 5ce35c0c48 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new d497a96179 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 17318b7659 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new a68555e9d6 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 09a8bd4df8 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 146a248ee9 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 851b6b20b0 89: onsuccess: #864: 1: Success after binutils: 25 commits new ec33bea0b7 90: onsuccess: #867: 1: Success after binutils: 4 commits new 1f18e056f9 91: onsuccess: #870: 1: Success after binutils: 5 commits new 3a3cc37885 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new ef6801d830 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 47deec3147 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new e98cd96f6c 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 52118d7777 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new c70a2c4797 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new c29162bab0 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 8061595ef6 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 05dbdc2e5c 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 756753d794 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new bb9699e583 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new cda52e39cd 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new e428cfd90a 104: onsuccess: #885: 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 (fd9d421ae6) \ 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 1680 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39312 -> 39852 bytes 04-build_abe-gcc/console.log.xz | Bin 212764 -> 215508 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8256 bytes 07-build_abe-glibc/console.log.xz | Bin 243600 -> 243396 bytes 08-build_abe-gdb/console.log.xz | Bin 38872 -> 38768 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2024 -> 2304 bytes 11-check_regression/console.log.xz | Bin 11820 -> 17720 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 24 +- 11-check_regression/mail-body.txt | 119 +- 11-check_regression/results.compare | 51 +- 11-check_regression/results.compare2 | 4001 +++++++++++-- 11-check_regression/results.regressions | 51 +- 12-update_baseline/console.log | 54 +- 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 | 121 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 51 +- sumfiles/gdb.log.xz | Bin 1878280 -> 1921028 bytes sumfiles/gdb.sum | 9721 ++++++++++++++++++++++++------- 30 files changed, 11283 insertions(+), 2958 deletions(-)