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 86e5368409 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 209f35c60d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 6c8c759f7e 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 30fec44d37 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards a393bb6b8c 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 502be231f2 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 041165f30a 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards f75c5e2c13 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 5ffaa273f6 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 505f871e01 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards b8ca54a115 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards e359c87472 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 7c7edfbf11 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards a617d94db0 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 2fbc285bf5 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards c5aa3e2613 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards b3c6d838e4 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards fa57e73d6e 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards f907804fea 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards fefb6331c3 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 6f581fb281 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 6f670d7656 120: onsuccess: #906: 1: Success after binutils: 29 commits discards f6899e7edd 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 139a158226 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards b3b15f8af3 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards c4a99fc49c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 468da1ea7e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards f42ab7acc4 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 840779a306 113: onsuccess: #898: 1: Success after linux: 3 commits discards ed627e978e 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 9928009691 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 096b6194c1 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 64c5a0b2d7 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards f75a67be89 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards dad5433a0d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 31f239d3bc 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 5a311c2b4a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 276ee3da04 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 25ee8313d4 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 534becb22c 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 592f93b133 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 668c2cf3b5 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards e542ce1061 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards b7c3fcb273 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 540478dd55 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards b94a065342 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 2fc434cc74 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 058bf3c26b 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 5386e51eee 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards a6d42ff9b7 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 4f8c6d0a6d 91: onsuccess: #870: 1: Success after binutils: 5 commits discards f702c02fa7 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 6018c57543 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 98d5fd9224 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 066a5b9fe6 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 0d6c6b4c67 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards b86e180536 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards ffa259e045 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 68a39643a7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 304207814b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards add0f0cdf5 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 7571129d16 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 708c6bc208 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards ee651a1d33 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 26cf9acc5d 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 526d3f56be 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 8d66b2ab97 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards b11a2815cc 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 0dca6f35fc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 6ed08fa9f9 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 972e05a721 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards fa9ac4674d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards cf8648424b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards fa33a39d31 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards dff7732110 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 59b2f9b926 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 00cefc679a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards f297875f2a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 06852e8fd6 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 4c762952a5 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 7f37bbf944 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 2fbf299aaa 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards c5e9779eef 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards d9913a7d62 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards be724a86ab 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards a0dad0056f 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 95cc18222a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 1a2cb55e07 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards b43216c40d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 80ce888d73 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards da643950c1 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 2db51156f9 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 3a3d798a42 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 3fd66cd31f 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 77dd1c191e 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 94d8eea2b1 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 879744cd8d 45: onsuccess: #815: 1: Success after binutils: 6 commits discards bd5cbdbd0d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 1ddda772c1 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards a2cff50d78 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 778306bad9 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new b91f4ac71d 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 19d0f3657f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 9bb005139f 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 0aa8c4b7cd 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 31f118d5d5 45: onsuccess: #815: 1: Success after binutils: 6 commits new 7db1610c5f 46: onsuccess: #818: 1: Success after binutils: 10 commits new 601a51cd1b 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 3877160c34 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new ad6972bc3b 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 4bcc5f9290 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 67ffe562e6 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new c7982b3163 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 91bc28461d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 5569ecf55f 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new ae9d99c9eb 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 0447bf4853 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 65eaa2ea74 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new e834c926b0 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 8ad860df31 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 54303f234c 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 9e6d22da52 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 909053c3a9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 51a943283f 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 75fab3ee99 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 83b379d88e 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new c1d5aca205 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 96cd6c502b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 4ad7335289 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new cbc9618e71 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 28c613efde 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 9bb1b61bc6 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 9e41d9221d 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 4415b2d79f 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new ffe2003fa1 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 3c43953ee4 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new c953ff5364 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new c811b389a0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new f6b7a4b381 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 06bdc09c0b 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 463d0fd152 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 305bb428cb 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 423408a4b6 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 9fe8ab811c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 824e8337b4 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 0563d06638 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 59cd1da4f9 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new caf79758ac 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 7e6998dfba 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 20eab1c217 89: onsuccess: #864: 1: Success after binutils: 25 commits new 4eec281843 90: onsuccess: #867: 1: Success after binutils: 4 commits new 2583aeb158 91: onsuccess: #870: 1: Success after binutils: 5 commits new c4c23a0ed9 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 2e12348fa6 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new c40cf77d59 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new eeda7e03d1 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new ea4b27dff6 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 45a8c1ce9a 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 1e1e7fbeb3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 876a985277 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 6c4460290a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 5bb5b921b4 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 23f786c579 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 622664c1cb 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 85614bce11 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 6fd8a73a29 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 89bf97b7ec 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new f2b94aa75d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 3df07bdd0a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 6323a5b3fa 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new a0d7a59b8a 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 40401e9c07 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 98e09e4273 112: onsuccess: #896: 1: Success after binutils: 24 commits new 71c167d6df 113: onsuccess: #898: 1: Success after linux: 3 commits new 4e06d4cf48 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 5a888abd18 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 689f391848 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 84d808a5d4 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new c5291bb2bf 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 19fa823fc7 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new e6069108b0 120: onsuccess: #906: 1: Success after binutils: 29 commits new 3cfef615cd 121: onsuccess: #908: 1: Success after glibc: 2 commits new 411d220cc5 122: onsuccess: #909: 1: Success after linux: 2753 commits new fb33d50cee 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new db668394e2 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new ee5aacfcf6 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new be0eff5efe 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 3d9f634f41 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 5b42e6b5f7 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 737df30940 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 0a295b51f1 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 10395eab79 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new a7982744dc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 928b1b34dd 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new a7870626ff 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 754af37281 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 3087c70da7 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 356504ec36 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 07edcce430 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 508d536562 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 6c82e47f14 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new c809cecb73 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new da77b21462 142: onsuccess: #929: 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 (86e5368409) \ 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 1744 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 40740 -> 39952 bytes 04-build_abe-gcc/console.log.xz | Bin 216528 -> 215980 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8308 bytes 07-build_abe-glibc/console.log.xz | Bin 244832 -> 244692 bytes 08-build_abe-gdb/console.log.xz | Bin 39280 -> 39652 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3892 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2036 -> 2240 bytes 11-check_regression/console.log.xz | Bin 14992 -> 18136 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 70 +- 11-check_regression/mail-body.txt | 197 +- 11-check_regression/results.compare | 118 +- 11-check_regression/results.compare2 | 7459 +++++++++++++++----------- 11-check_regression/results.regressions | 115 +- 12-update_baseline/console.log | 42 +- 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 | 199 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 115 +- sumfiles/gdb.log.xz | Bin 1930128 -> 1889436 bytes sumfiles/gdb.sum | 8897 ++++++++++++++++++++++--------- 30 files changed, 11033 insertions(+), 6227 deletions(-)