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 f0e3534a54c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 5cfa94992a7 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 253d048c6d7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 95e96ecde2b 113: onsuccess: #898: 1: Success after linux: 3 commits discards 9753c30dc93 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 0db5a83e25b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 82062370428 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards b83bce98317 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards a1e1f68c087 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 75c669d5bb3 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 1e46cc37683 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 0c5395d62b3 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards c7d98880011 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards c7a43e975ff 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards ad0dd9c7155 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 9e85c87b12d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 6397f68a425 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards fad77287c07 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 3490c09bd56 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 0a822ffdeaf 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 1082a8a1862 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards b1870d56f5a 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 5f53b6c5687 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 4b3b12f16c1 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 5cf930eb346 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards c240c8beeeb 91: onsuccess: #870: 1: Success after binutils: 5 commits discards f3824f9c990 90: onsuccess: #867: 1: Success after binutils: 4 commits discards d6418269223 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 885fd4ae7d7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 85e086becd0 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards edbdefbab24 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards a5430412f66 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 422fd69cabd 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 495a5b15f86 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards be78c7fb7c1 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 30c4d5998d6 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 84d33388f5f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards ec2a3cfeb75 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 40f5ff08503 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 4152f301d5a 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 02693153e1f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards ee9dbff490b 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 8229c4b5d86 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 9341ba24dab 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards f8b429eb2e8 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards be1d412a5b1 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 817e4abccbf 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 8ab427e34d7 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 29926ed2bc9 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 2097e9c0af8 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 0c7c3b1df15 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards b5628524c9a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 319c4d3f152 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 8da6160e4b2 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 57674ffe09c 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 5ce02b44f82 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards a27f3061a7f 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 9588658df72 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards bf6011717b1 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards f8410f86fe2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 42d5f137aae 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards de9fafc1a07 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards b03d03cabc8 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 7c47592175e 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 9dd3201e298 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 0990429cdb2 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards cf07ec11f6a 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 5c247e70589 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 94fb18cf8c7 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 47cdaf4ca0a 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 62c6d306846 46: onsuccess: #818: 1: Success after binutils: 10 commits discards e0a98e8064b 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 27901b0cd31 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 9f12ae9b9a3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards f6b3dcc4b56 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 23539344e57 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 44769232c94 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards cd63c31318e 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 2741fe667bd 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 4755befe8eb 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards b4070b09f09 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 76d512c4b80 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards bd730219112 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards ad4acb22f9e 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards c3fdaa2c677 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 33e0c320528 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 1d173fee3a8 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f4388ae5a39 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards a142d129d63 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 487863e448f 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards e91b3b00d1a 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards b933e11375a 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 7515f0a8a36 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 2a67166c1ca 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 47c35c7a38e 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 11f5cabe986 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 5c10e7b2807 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 71de4b94cbe 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards ad96d452a13 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a82a6928cab 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 6c79a7870ae 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 9211999f08b 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 446061f4f5f 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c0540799f74 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ff2c29e72e6 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0fb3af28d72 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 75a47c01ac0 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 882291c9030 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 90170d15b2a 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new ceef21a5c5e 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 1fd8aa68d5a 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new fdea7ae9d78 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 9bba45cba7b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 931c8548140 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new eb413b368ed 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 32788008eee 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new e84736a6d43 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 40e803f8c11 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 048e3bc4cde 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new f6710550f75 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 3b056b5f1bd 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 4003f8efe05 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 338615c1798 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 064d1a3f91c 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 4df407ffcda 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 7182402da12 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 813d53b60d8 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new f45b125f535 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new deb2c223ff3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new cf161ed628d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 83159e019eb 45: onsuccess: #815: 1: Success after binutils: 6 commits new 6dd8f02aede 46: onsuccess: #818: 1: Success after binutils: 10 commits new 125fe9f13bb 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new da27bc1d833 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new c662a6898d0 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new f698aa737d0 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new a3fdf33c2fe 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new de95ab3e96e 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 9552972e0b5 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 802c4ac9bb9 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new f7d5cc572db 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 273e4d9f757 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new c9e957fbbd3 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 48cddd9c7b8 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new a45beac880d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 8e1b1e68da9 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new c814fc38ea0 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 521d9b1ef1b 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 015aa1445dc 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 2ff5975ea77 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 7541cd6af80 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 1109c589198 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 1038749475a 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 4a7dec337a9 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 5646ab1575b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 02eddb576d5 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 4c75992b4e0 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 6856f8ed5d1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new ef1dd90a872 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 3aeb33a6d5a 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 6689e478265 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new d08f987afd9 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new a927cd973bc 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 5df194d256a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new fc3a68eb82c 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new f5ce8f4e2cb 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new e9faf111b94 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 8500a2d0f13 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new b174fe853fc 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 04f7e1f95cf 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 2d194ec1599 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 2f544290145 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 67a98358aba 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new b4df038adeb 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 9a843214bcd 89: onsuccess: #864: 1: Success after binutils: 25 commits new 3dbd830c12d 90: onsuccess: #867: 1: Success after binutils: 4 commits new b880f945ec5 91: onsuccess: #870: 1: Success after binutils: 5 commits new 894544bf9cc 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new f2ae4c3aae9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 858deb36e4d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 69c100c3d09 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new b0077ab8f50 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 43338d496cf 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new c4fd27a0ddd 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 7f9de7fabd6 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 0a2dbdc84f6 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 9ac9b82009e 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 52be5204b3a 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 566673dd5b6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 89723433075 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 1dca1f1ab39 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 599b401166b 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new a32c6b427e7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 5be0adc6738 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 05977ad1508 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 7b0869e29e6 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 45d978aef04 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 48e728fc8ae 112: onsuccess: #896: 1: Success after binutils: 24 commits new 8585e77da39 113: onsuccess: #898: 1: Success after linux: 3 commits new 1107584579a 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new d03a3809256 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new dfe0bd9ad0d 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 55af42f02c1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...]
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 (f0e3534a54c) \ 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 1748 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 38908 -> 40848 bytes 04-build_abe-gcc/console.log.xz | Bin 213680 -> 216956 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8864 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 243712 -> 246992 bytes 08-build_abe-gdb/console.log.xz | Bin 38632 -> 40780 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3896 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2028 -> 2960 bytes 11-check_regression/console.log.xz | Bin 16104 -> 12996 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 38 +- 11-check_regression/mail-body.txt | 129 +- 11-check_regression/results.compare | 73 +- 11-check_regression/results.compare2 | 1287 +----- 11-check_regression/results.regressions | 73 +- 12-update_baseline/console.log | 42 +- 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 | 131 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 73 +- sumfiles/gdb.log.xz | Bin 1950092 -> 1860072 bytes sumfiles/gdb.sum | 7197 ++++++++++--------------------- 31 files changed, 2623 insertions(+), 6474 deletions(-)