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 290fbba36533 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] discards ca822c8b04f8 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] discards 5f96d013d3eb 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] discards bf5760ab3b77 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] discards 718b7944d902 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] discards 3554aa8eef38 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] discards bd9ad6648c24 122: onsuccess: #909: 1: Success after linux: 2753 commits discards d49939fcad50 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 1c08def51019 120: onsuccess: #906: 1: Success after binutils: 29 commits discards a173af47b19f 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] discards 2434d4d1301d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] discards 265caa292893 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] discards 49ae028edd72 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] discards 1cddcaa8e38a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] discards 53add98d280e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] discards 91accc23b93c 113: onsuccess: #898: 1: Success after linux: 3 commits discards 35d7c499b26a 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 619724f5b1ac 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards c2394433c907 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] discards 77ffa9f549ce 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] discards 9c6eb28ab3f6 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] discards d77cf82e1077 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] discards 8a86523cf23c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] discards 98175aab5172 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] discards a13b9d6c0b22 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] discards aeae2ac8e3fb 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] discards 0122c1231d2f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] discards 4e4ecf0f8a7f 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards 4adecabe89fa 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 2a50ab571057 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] discards 413b782c2cac 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] discards 9fa90d8721d5 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] discards 54f63ffd1732 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] discards 540a2cedeebb 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] discards 72b1c305e85e 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] discards 207154bf22aa 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] discards bc8e8d9100b9 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] discards e372312146b2 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 2929e690e3d4 90: onsuccess: #867: 1: Success after binutils: 4 commits discards acf5332f3833 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 918af72c62dd 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] discards 4a8b781fb287 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] discards 9e74b11aa0b0 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] discards 0caa35b598fa 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards e1107dc73025 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 26d6a8cab70d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 9cfe49aaa37b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 47c784fb5bfe 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 2fe0b788826e 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards d451bb3dc21a 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards d8ef177fae25 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards e13f5aeb53c2 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] discards a3885649dd01 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] discards 728f66de1a53 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] discards 52a168b34ada 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] discards eb8d3b477f90 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 9bd303d5a6c1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 9151b62df152 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] discards e582627606e6 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] discards 23bffd83f7e1 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 8b3f804dac07 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards a9ad39e19a3d 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 7002aaae7891 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] discards a52aff5592f5 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards 7c3ff005505c 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 798c12ec0bf5 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 901f14430e2d 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] discards c435d42e2461 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] discards 2d436e78fc3f 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] discards acfbaeec0939 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] discards 19d304d827d7 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] discards 551492da3e5a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] discards 8fff65a5b632 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 1a433a97b796 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards 36ccbe186cc9 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 9d540975b609 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards 8e89f0fc13be 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards 7a2304be0d4e 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 8dd85d0014c2 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards 63ef2593144e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards 167f95674acf 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 9862a377a461 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 960ecbc5bb89 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 6214a1a098cb 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 5af7d0f30cd2 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards 75082f4ae3ef 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards a499a55e7cfe 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards 23815e664f92 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 2523551ff86e 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] discards 0572b30c0cbc 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards 87c829c0260e 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] discards 6832ea58e788 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards ac4e1756f9e0 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] discards d3085e58bf87 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards 6e879140a60c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] discards 1e8cf78eaefe 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards 60edc5cd5ba1 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards b192a34f191e 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards da3680a2f608 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards 613f1d5dcd2d 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] discards e0fa5ab21d73 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new ef0fea9eea3a 28: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new c998b5e28a66 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] new df0025b6624b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 49f0ad102c4f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 424e63c01e9e 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new 6283d49a2a53 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new ec15716db245 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] new dc2f58fb575a 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new af447ac6659a 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] new 6aad927f6f3d 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new aafb4acdd964 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] new eab83e63c1c5 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 57fc458af52c 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] new 0abbfd9dfffd 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new 9f774cb64f59 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new b074d5e8de0d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new 72c58df5cb0c 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 7416d2e6bbac 45: onsuccess: #815: 1: Success after binutils: 6 commits new 9d1388d5aa6a 46: onsuccess: #818: 1: Success after binutils: 10 commits new 367688a14f5a 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new e20eac871ff4 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new d7957b85b37c 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new 655d53f7150f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new 06bb12b6ba37 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new ca41b96d28a1 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new e3715d7701ef 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new b245a59aa1db 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 215f29632294 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new eabb5f919185 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new 0724a4585c24 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] new ce958e3865ba 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] new f6b8e9604e78 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] new 31b907db23fe 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] new d2a712f0bb9a 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] new 9ac6074b73eb 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] new 04e3fca24e80 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new 397bcf3c9c53 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new fd0b5216acd8 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new 680ab0738f22 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] new 27b7ad9fc8bc 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new b7a007e91390 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 7ab58ebc71d2 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new d255b924b1a6 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] new bc96aa9b06f2 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] new 49ec05f1d6a7 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 7c2329862d43 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 461a31bc29ba 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] new 731dd999dc42 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] new 90d4a7d5bcfa 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] new c85df5d2cb42 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] new 52b3683dbb5d 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 8f5cecabe4d9 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 2f9e065ba6e9 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 86253bcc97a4 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 9676d7e59a0d 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new c984edbc3016 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 3651245f6772 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new c06f4f256652 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 7571424a1737 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] new 9b0f3c449efe 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] new 4de9cf8b2ec7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] new 9e5ec9e8844f 89: onsuccess: #864: 1: Success after binutils: 25 commits new 64135375d9d1 90: onsuccess: #867: 1: Success after binutils: 4 commits new b95e8f268a6a 91: onsuccess: #870: 1: Success after binutils: 5 commits new 87f05a395c91 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] new 436b575a398c 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] new a2cc6620f997 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] new 714b49875d67 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] new 34f222fca35d 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] new cc0d501548be 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] new 110b7eda244c 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] new b4a4bd611e4b 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] new 915663051277 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new e435dfc74515 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new a81b68dc1ee2 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] new cce16cd51dd6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] new 5175b83ff785 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] new ee875b22fa52 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] new a3a076706b29 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] new af95e40dc876 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] new 665e219c2641 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] new 423e7f6e7ba7 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] new 291894ff4f29 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] new 602a66fd3f10 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 343bd61a6429 112: onsuccess: #896: 1: Success after binutils: 24 commits new e278362fd595 113: onsuccess: #898: 1: Success after linux: 3 commits new e7c6de495358 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] new e80dbdb5650d 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] new a8f8ee0f21d6 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] new 11c8fd710739 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] new 25fa4dddb1f2 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] new d30f5c9b613d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] new 30d8c4b4016f 120: onsuccess: #906: 1: Success after binutils: 29 commits new c4761bde0313 121: onsuccess: #908: 1: Success after glibc: 2 commits new 445663799869 122: onsuccess: #909: 1: Success after linux: 2753 commits new 0f024f0e28e8 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] new 6f30f353fc17 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] new 89a897961ae8 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] new 0eadb10dddce 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] new 26f1e1e69bed 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] new 2dff7be9f8ee 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] new f951d5485b4d 129: onsuccess: #916: 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 (290fbba36533) \ 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 1740 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40564 -> 40056 bytes 04-build_abe-gcc/console.log.xz | Bin 215276 -> 216476 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 9172 bytes 07-build_abe-glibc/console.log.xz | Bin 243300 -> 244584 bytes 08-build_abe-gdb/console.log.xz | Bin 39212 -> 39296 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2020 -> 2232 bytes 11-check_regression/console.log.xz | Bin 14744 -> 14772 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 66 +- 11-check_regression/mail-body.txt | 215 +- 11-check_regression/results.compare | 92 +- 11-check_regression/results.compare2 | 5406 ++++++++++------------ 11-check_regression/results.regressions | 92 +- 12-update_baseline/console.log | 56 +- 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 | 217 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 92 +- sumfiles/gdb.log.xz | Bin 1924584 -> 1909608 bytes sumfiles/gdb.sum | 7478 ++++++++++++------------------- 31 files changed, 5807 insertions(+), 7961 deletions(-)