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 e4f3b0292b 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 466ff89205 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 07db5d17fa 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards b4b2fb5886 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards a81fb16269 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 70c434daaa 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards b035e69aa9 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 1eace63df6 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 1c10ad3d57 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards f528094797 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 8287d0ef82 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 740b9eba8a 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 4ec5e08936 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards e84c980475 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards c693086500 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 2a97a594b5 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards f09af1ded4 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards c3413ae347 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 98a9f79678 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards b921783bc9 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 371055dde5 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 4cfb464791 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 39141313ee 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards dd27bad618 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 3227dcbf8d 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 16c730b87d 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards c0448dae61 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 038651f1ab 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards bd27ada0a9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards e498535385 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 6cea89b64e 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 6ec5e581bc 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 91a8445ef8 122: onsuccess: #909: 1: Success after linux: 2753 commits discards edc1653388 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 388469a84c 120: onsuccess: #906: 1: Success after binutils: 29 commits discards d746b6120f 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards c72eaedc0e 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards f2ec35ec7e 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 407273ad79 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 38ef291d0a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 2f29fc9a27 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 815faf0df1 113: onsuccess: #898: 1: Success after linux: 3 commits discards bc2af890b0 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 296099472f 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards b246cecc60 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 17b59a0ac9 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 40c13354ac 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 931dcdd3a7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 2c92bb3af1 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 723670ed7f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 50dbc8b12a 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards d311b566e6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 0b792e8e45 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards ea9bbd989d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 6b8f8e37c0 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 8b515b0550 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards f112fa6cb2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 92fbfe568b 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards c1d3ee41db 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 57165465f3 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 5c0401374e 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards a423ca0cf3 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 5727cd0847 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 042ea8e315 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 616fac8e55 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 47e26dcb96 89: onsuccess: #864: 1: Success after binutils: 25 commits discards dec1d532be 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 2721c746c3 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 25a0f7630e 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 6c0e20589c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards c3e2bf8944 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 733566fbc9 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 953bc1e08f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 18a949199b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 318111ffc1 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards f3532fe634 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 20a8cb3fce 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 800c396ae0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards a3b9cd4eef 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards be5ec0c9e1 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 114d47c504 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 747502d44e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards b3a74a903c 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards fe25d3177a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 7838437d6e 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards e7ab6b7a6d 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards e4371357d0 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 71efa32340 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 1b20c507cf 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 1f91bc13fc 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 78341eed20 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards fdc4aee764 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards e8641e2b9f 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 9883c28c87 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 27494a691a 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards a12d833964 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards aeb3d12203 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 9235518d9b 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 04fdcb058d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 46cae52ea1 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 048c630917 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 196fe6982f 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new c13d9c992c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 33e2331375 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 442889ab4e 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 84a7001223 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new c89cdb74ca 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 3c924ae303 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 1af4d5efb7 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new d067874807 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 47ad225b5f 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 43db386afe 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 3969c33284 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 6c3a6df73d 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 04caed3442 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 7c12b52640 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new acec55e8b4 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 83600c6e16 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new ac8c5ffe77 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 4e870e855e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new d65032ad74 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 3bbb7649e0 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 64e8d0b389 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new c5c8871a79 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 5729110aa0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new a45c7d1484 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 8e99c9b876 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 81ce43a00d 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new a7146a41aa 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new f7c1c7c5e8 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new e5c0f7290d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 1c4557c823 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new a39a797e10 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 7cdc07407e 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new ed8454ff7a 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 85eef90079 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 90ec675134 89: onsuccess: #864: 1: Success after binutils: 25 commits new 27c9ae6131 90: onsuccess: #867: 1: Success after binutils: 4 commits new 53b53d9d4e 91: onsuccess: #870: 1: Success after binutils: 5 commits new aecf796dfc 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 1954f2d86b 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 9cc824a667 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new ff32047114 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 2c2ae763ef 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new c3a1ca646f 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new a9468c2257 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 5dadeb386f 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 7918a6875b 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new a0db735464 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 3bc36f906b 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new e1ba42435b 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 2206872ae0 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 47c5eb1605 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new f1b405e147 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 9de086c20b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 6093535e8f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new eb9b825df5 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 7b58f6d033 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 35503ad037 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 403eb6a7a5 112: onsuccess: #896: 1: Success after binutils: 24 commits new 0cc836e4a0 113: onsuccess: #898: 1: Success after linux: 3 commits new 2b1f8ac5fe 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new c6e3497344 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 22c4badeb6 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new a4fd3f9d8e 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new bf051e19fa 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 7dfc1ca785 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new a0479c9212 120: onsuccess: #906: 1: Success after binutils: 29 commits new 6e0f39790b 121: onsuccess: #908: 1: Success after glibc: 2 commits new d3cde1059f 122: onsuccess: #909: 1: Success after linux: 2753 commits new c39c3e41de 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 0669215dd4 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 7e2839bcfc 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 3d7ea2ed57 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new b6f1505030 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 8db084f071 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new ed4ce8f95c 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new acca7ee411 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 87a02a825f 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 1275069f0f 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 4dcea8b397 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 20ba23c51f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new ef361631b6 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 4746cb892b 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new b26f8965d5 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new e8bbdbc425 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 4bdd2e1fa5 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new cd2236dfe0 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new d22686657b 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new cb32f3d480 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 009c0abcb9 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 71aead88e7 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 1a38693b4e 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new c0c34665e3 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 6ebf137ce2 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 5c63714082 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 5448198a4c 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 3f3da45bcd 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 51a169e6eb 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new c18686ae7a 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 9a184757b9 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 71b479850e 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new bc07bffbad 155: onsuccess: #948: 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 (e4f3b0292b) \ 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 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39504 -> 39652 bytes 04-build_abe-gcc/console.log.xz | Bin 213972 -> 214212 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8552 -> 8844 bytes 07-build_abe-glibc/console.log.xz | Bin 244696 -> 244744 bytes 08-build_abe-gdb/console.log.xz | Bin 38980 -> 39260 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2176 -> 2436 bytes 11-check_regression/console.log.xz | Bin 8248 -> 15452 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 22 +- 11-check_regression/mail-body.txt | 133 +- 11-check_regression/results.compare | 56 +- 11-check_regression/results.compare2 | 4258 +++++++++++++++- 11-check_regression/results.regressions | 56 +- 12-update_baseline/console.log | 30 +- 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 | 135 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 56 +- sumfiles/gdb.log.xz | Bin 1982084 -> 1951640 bytes sumfiles/gdb.sum | 8421 ++++++++----------------------- 31 files changed, 6561 insertions(+), 6660 deletions(-)