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 1482c80fe1b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards fe54bda4268 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 672b1ea6cba 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards fcc2398e9f4 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 52d0ef85a95 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards b313c628184 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 842dc065163 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 94341bd892b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 9cb89efb50c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 816a6574336 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 79706618f70 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards e753b4beeb1 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards c8c7d32ff05 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 1faad4c6196 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 8abc57f027a 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 8db70f05f56 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 6a87b09d06e 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards fa0587a1d44 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards dab5c3479db 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 3f34977503e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 60147f05423 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 9a46b278190 90: onsuccess: #867: 1: Success after binutils: 4 commits discards a22ea1cb4d3 89: onsuccess: #864: 1: Success after binutils: 25 commits discards c8513994b54 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 006d95529dd 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 5854dfe4a10 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 75686053dbc 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 9ebd935ae49 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 4716e0e4263 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 05b64c5a168 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards c7648a99f59 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards c95536c1743 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards b9d1c8d3d10 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards de89dc65a4a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards dd768c203b2 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 45f2e3dbdf8 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards df434d74ee3 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 28c970321ea 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards e884b169c5a 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 54ed2129e05 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 8e7b2001ad4 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 006b02bb56b 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 8a063c4ab90 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards eaf8efc8138 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 1d18af96543 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 9b8dbbf5b53 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards f825bb71a9d 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards c14d0e4536d 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards fc8e705ad11 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 775cd2c3313 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 6d456f8d19a 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 2037f20bb68 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards dadfe8df020 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards b4d1f3ef7ff 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 56071252e46 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards c7158072ab7 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 0ee6e773ef5 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 5eb2629b157 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards e11c3446956 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e2dd316e6ea 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 816f8c34cf3 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 6be735333d6 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards c29ce4352a1 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 1a92e0871cd 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards f93575f4476 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 96e90c3fa80 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 0c5b2e2a74d 45: onsuccess: #815: 1: Success after binutils: 6 commits discards a399adb19bf 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 2dec686c908 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 82fe825d828 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 7d250bdb0ad 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 148c490e33f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards c88721f460b 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 4017238c4f5 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 02b441edd5e 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 5ae208a30fb 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards aaed779b735 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 4fa38dfd8d5 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 402a3ef3495 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 6163f0ce31d 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 8d003c6694f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 7b040443cb8 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 6710f6fd7f9 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards c8598fb2013 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 6d49a90e859 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards f900b66233d 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 6d5b5c20519 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards bfcb9224df1 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 21a63208676 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 83198a077d1 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 8a396e6f3e5 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards c6e8d310bfa 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 9c83288dc2a 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 54bed41d8f1 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 987df348724 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards dfb45b6f753 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 3f48ab81aa3 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 18beb837f83 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 76067262178 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 94c9f2cc465 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 40a3f73e05e 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 48c80c5ad9c 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0d268e76f16 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 328ede7d02d 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 609d79d32f4 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 5cd208d8311 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new e0ed4a5008d 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 9554a08dcc8 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2c92b49b158 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 18d6273a885 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b6438aec083 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new e9c0c2444f1 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 8c76bc087ba 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 36f689d2173 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new f931c20ba1a 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new c62895081fc 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new eefe89f08f4 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 410f732df7b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 87d5825cace 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 81806cb5c75 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new d4def2beab4 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 10209fbd839 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new c5ba3690b64 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new c29bc18920c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 1bae6db8431 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 742d4ebfb25 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 176c1b0abe7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 6e949bee668 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 645e4305d9b 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new c4f49065eb4 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 22ea07792aa 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new ad42e605a32 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 60dd88e1c37 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new a940af46104 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 9a451d5f75c 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 5b0ac2bdd7f 45: onsuccess: #815: 1: Success after binutils: 6 commits new 47124fecffb 46: onsuccess: #818: 1: Success after binutils: 10 commits new 937563dd452 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 41a2258e684 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 151418d81ad 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 06070ef7e24 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new ecc85badf10 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 86b05d72656 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new efc07b74650 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new b613a325055 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 51be3092df7 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 02b97769fe8 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new c7d551cad89 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 623b8252abf 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 464d4b395a7 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 9fd0335e280 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 94f50818410 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new ca411192ff0 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 71c3a3c5caa 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 7aa2e6b32f8 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new c41344f2853 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new ca21bb939fb 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 55a61c39340 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 093771220a3 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new dfb4f3bff6d 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 6a0bf962e71 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 4559cd33c33 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 0368cb4453e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new f1beaf19834 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 30f5c720efd 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 7cb124f33c8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new bb6d4eaa5a9 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new dd4e8622d10 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 4cfd7151c0f 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 81f421328d7 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 97e771bbbd4 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 9cdc0490706 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new da05f23cd3b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 612342cfd89 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 1b6c34099b6 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 7ab9a2e4e8a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new ae994b0b127 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new b96333786d0 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new bcbd276fc08 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 7b78bfc4d78 89: onsuccess: #864: 1: Success after binutils: 25 commits new d385c78c64e 90: onsuccess: #867: 1: Success after binutils: 4 commits new 6c12f6bc8f2 91: onsuccess: #870: 1: Success after binutils: 5 commits new e9fb6a8070d 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 68def7917f2 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new a7b02cf966b 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 44c2ce4d2f9 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 71864d6f317 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 082f91bb67e 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new b07c8e9e499 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 38ab1cfe869 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 3596f01111c 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new b6b323b493e 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new b0230a6643b 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 63719f4c19d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new fbf0a95679c 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new f440447708a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 23c2ef85e26 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new db3c6adfc9f 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 55d573332e0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 0750f2cd821 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new e24ee60199e 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new c8bdc6e47c6 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 0c77dc65cda 112: onsuccess: #896: 1: Success after binutils: 24 commits
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 (1482c80fe1b) \ 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 1784 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39092 -> 38996 bytes 04-build_abe-gcc/console.log.xz | Bin 212476 -> 213780 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8292 -> 8416 bytes 07-build_abe-glibc/console.log.xz | Bin 244344 -> 244392 bytes 08-build_abe-gdb/console.log.xz | Bin 38856 -> 38840 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2132 -> 2132 bytes 11-check_regression/console.log.xz | Bin 12936 -> 8496 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 34 +- 11-check_regression/mail-body.txt | 117 +- 11-check_regression/results.compare | 68 +- 11-check_regression/results.compare2 | 3257 ++------------------ 11-check_regression/results.regressions | 68 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 119 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 68 +- sumfiles/gdb.log.xz | Bin 1867132 -> 1922068 bytes sumfiles/gdb.sum | 4907 +++++++++++++++---------------- 27 files changed, 3011 insertions(+), 5699 deletions(-)