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 991d465a66 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 0d8ea12c85 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards e26ce817a3 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards dc405f8ea2 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 50d129f0dc 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards faf7dc3cb0 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 0f6cfe5a02 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards a6e9d89511 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards dd5d832549 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 1c0cc4c03a 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards d6989c46e5 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 72e7e7565c 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 9d57ed37c6 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards c4e4b59d8d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 6ad5b58011 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 233bdad6ca 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 0fbd53fcdc 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards d697199ba3 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 4df8117da4 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 9235f828cc 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 3e127600c6 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 45e9f96f23 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards dbe78c506c 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 2744c55677 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards de5f36aba4 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards d38d93a5b5 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards bf46eb6b6a 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 687c2ff4d2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 3d47092c7a 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 4463714ecd 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards dfd2f05a10 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 7472bfd86d 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 32b1be7c01 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 4ded0bb372 120: onsuccess: #906: 1: Success after binutils: 29 commits discards fd226d616b 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards aad134688a 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 04973c6f68 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards c7b4c0eca8 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 685db4b29e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards f614d2dd62 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards de58f2616c 113: onsuccess: #898: 1: Success after linux: 3 commits discards 5aa0a72f2a 112: onsuccess: #896: 1: Success after binutils: 24 commits discards c70bbb6508 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 375597ee5f 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 3a364f1a4e 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards b83daf5282 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 22b0e7a989 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 099e441703 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 2590a7ac0b 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards bd63cb9306 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 2a492cd68d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards f4ac983b38 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7afc055ffb 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 558e172408 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 3aee900fcb 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 9ce11ddbb6 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards e8a3d21e98 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards fcaf4b3f58 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 20db23e801 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards ebab62891a 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 3f3d4020bc 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 08ea45ce89 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 6e84750b94 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 9fa55f9c94 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 495bcdf4b4 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 96f5add3c7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards dabc120982 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards e32c45a770 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 3d0dd4b763 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 9331319bba 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 2fd184223d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards e902dfb17d 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards c346c71a09 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards ba96c2c736 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 78ce04d5c0 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards ea60f02a48 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards a244e8eda8 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 787c4cedfb 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 5042f50767 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 5af2adeb66 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards b6a456ffc6 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 6218723699 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards d44ff0507f 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards a79b84aeb7 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 8c3d24a277 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 90d975d7e6 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 0ae8e7e4bf 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards dd7f4acdb6 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 3f2b15138a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 926ef3125a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 006c7d5649 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 18dd131a63 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards f22fe40d65 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 2965ee7152 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 2bbb4b2b57 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards a60af7b97a 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 070e03e3bb 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 5b32355899 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards ae1eedc4b8 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards fad0b67cf0 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards e94c3d625e 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 03f1f8d45b 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 048c630917 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 46cae52ea1 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 04fdcb058d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 9235518d9b 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new aeb3d12203 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new a12d833964 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 27494a691a 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 9883c28c87 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new e8641e2b9f 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new fdc4aee764 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 78341eed20 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 1f91bc13fc 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 1b20c507cf 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 71efa32340 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new e4371357d0 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new e7ab6b7a6d 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 7838437d6e 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new fe25d3177a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new b3a74a903c 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 747502d44e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 114d47c504 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new be5ec0c9e1 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new a3b9cd4eef 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 800c396ae0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 20a8cb3fce 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new f3532fe634 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 318111ffc1 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 18a949199b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 953bc1e08f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 733566fbc9 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new c3e2bf8944 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 6c0e20589c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 25a0f7630e 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 2721c746c3 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new dec1d532be 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 47e26dcb96 89: onsuccess: #864: 1: Success after binutils: 25 commits new 616fac8e55 90: onsuccess: #867: 1: Success after binutils: 4 commits new 042ea8e315 91: onsuccess: #870: 1: Success after binutils: 5 commits new 5727cd0847 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new a423ca0cf3 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 5c0401374e 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 57165465f3 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new c1d3ee41db 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 92fbfe568b 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new f112fa6cb2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 8b515b0550 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 6b8f8e37c0 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new ea9bbd989d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 0b792e8e45 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new d311b566e6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 50dbc8b12a 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 723670ed7f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 2c92bb3af1 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 931dcdd3a7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 40c13354ac 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 17b59a0ac9 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new b246cecc60 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 296099472f 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new bc2af890b0 112: onsuccess: #896: 1: Success after binutils: 24 commits new 815faf0df1 113: onsuccess: #898: 1: Success after linux: 3 commits new 2f29fc9a27 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 38ef291d0a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 407273ad79 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new f2ec35ec7e 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new c72eaedc0e 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new d746b6120f 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 388469a84c 120: onsuccess: #906: 1: Success after binutils: 29 commits new edc1653388 121: onsuccess: #908: 1: Success after glibc: 2 commits new 91a8445ef8 122: onsuccess: #909: 1: Success after linux: 2753 commits new 6ec5e581bc 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 6cea89b64e 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new e498535385 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new bd27ada0a9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 038651f1ab 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new c0448dae61 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 16c730b87d 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 3227dcbf8d 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new dd27bad618 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 39141313ee 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 4cfb464791 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 371055dde5 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new b921783bc9 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 98a9f79678 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new c3413ae347 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new f09af1ded4 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 2a97a594b5 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new c693086500 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new e84c980475 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 4ec5e08936 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 740b9eba8a 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 8287d0ef82 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new f528094797 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 1c10ad3d57 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 1eace63df6 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new b035e69aa9 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 70c434daaa 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new a81fb16269 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new b4b2fb5886 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 07db5d17fa 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 466ff89205 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new e4f3b0292b 154: onsuccess: #947: 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 (991d465a66) \ 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 1792 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39380 -> 39504 bytes 04-build_abe-gcc/console.log.xz | Bin 213904 -> 213972 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9064 -> 8552 bytes 07-build_abe-glibc/console.log.xz | Bin 244800 -> 244696 bytes 08-build_abe-gdb/console.log.xz | Bin 38872 -> 38980 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2020 -> 2176 bytes 11-check_regression/console.log.xz | Bin 11196 -> 8248 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 30 +- 11-check_regression/mail-body.txt | 139 +- 11-check_regression/results.compare | 77 +- 11-check_regression/results.compare2 | 2450 +---------------- 11-check_regression/results.regressions | 77 +- 12-update_baseline/console.log | 60 +- 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 | 141 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 77 +- sumfiles/gdb.log.xz | Bin 1990000 -> 1982084 bytes sumfiles/gdb.sum | 4375 ++++++++++++++++--------------- 31 files changed, 2614 insertions(+), 4866 deletions(-)