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-arm in repository toolchain/ci/base-artifacts.
discards e70a663a17 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 541472372b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards abc5846d86 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards cec1903fdc 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 3b52f7044b 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards dca61cd0ea 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 5991c4e4c4 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards a61240fc91 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 2d05ab044a 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 1238d33f95 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 1cf473a6ca 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 8723029550 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards c10066d611 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 9546a08d3d 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards ea0b9bac1a 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards c822a83bcb 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 73955d06b3 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 019f6b0215 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 7bc8407fbd 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 002c0640be 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards d002622e23 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 519390b7ae 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 627fbed8d0 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 41f1622e6c 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards d57dc54ef7 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 82ef8c8da7 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 9e0085e0b6 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 0bf8238810 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards d570d731cf 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards b54a9530be 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 955995a47e 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 38ae79bd9f 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 877a18e9c0 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 6e2272191d 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards a0061d330b 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards b58c129f38 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 956f833429 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards b466448985 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 4597bb9e83 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 638a597f5f 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8575a1ed92 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 0dc411dd71 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards fe3e73cc52 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 4092f11235 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 9d2e46cf63 125: onsuccess: #614: 1: Success after linux: 12 commits discards 902cc5d488 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 928bf1bc2b 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 031e401aac 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 252a9eca79 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 3418b05c2d 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 89cf4097d0 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards b53b867ad1 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 46744b312b 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 9bf53a2d4c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 08251fc77b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 448f552be1 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 811874dc82 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 87e8a599db 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 73541fb197 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards d1031bd393 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 87307675fc 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards e4e4549c41 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards c7c87cc43f 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 7daa47e524 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 5e77fa12e3 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 0cb35ea2eb 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 832c637986 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 2ec76f1cbd 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 4c38a47db2 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 03bd016d36 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards ae89153266 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 2928c2061d 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 08f6287c61 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards d6c8b4ba51 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards e3c2fadecc 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards d2906a3ca8 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 6e3552ea83 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 3d797514c8 92: onsuccess: #575: 1: Success after linux: 34 commits discards cbf6870a47 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 100923c53f 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 390feb0f07 89: onsuccess: #570: 1: Success after linux: 11 commits discards 96c161fa31 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 4283b6ce52 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 46924c9a14 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 011da02472 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 7a608a4a8f 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards f2d1bafb3c 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 6763549b97 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards ece06e37da 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards cb3af58d6e 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 8d372e7586 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards b5bbd2fe9f 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards a83e9ed4c2 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards a98213f5f1 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards b1fc1a5a6b 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards a50b7ef6b7 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 57ab7bf547 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 5571285d80 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards a227eb61a3 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 2128b0aef6 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 882d74f7f2 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 723fadce9d 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 45fb304871 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new fc379bc9ba 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new b373553e80 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new be601c1c55 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new ea2db97c95 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 242131c3c4 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 16b41ea9f3 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 7376debbdb 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 815e18fdae 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 857a16b61d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 92c766c444 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 80d4fa8e1f 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 240a3c0a58 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 51239847d3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 0aeaf87c2b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 5a8a530048 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 8631bc52a7 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new db350cc89d 87: onsuccess: #567: 1: Success after binutils: 8 commits new 365248701d 88: onsuccess: #569: 1: Success after glibc: 10 commits new ade197a599 89: onsuccess: #570: 1: Success after linux: 11 commits new 633af88ac9 90: onsuccess: #572: 1: Success after binutils: 15 commits new fa9f03d0f3 91: onsuccess: #574: 1: Success after glibc: 3 commits new ae68290690 92: onsuccess: #575: 1: Success after linux: 34 commits new b610e5f4e1 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 699650c026 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new f13807db6c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new e24d070449 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 9f22a1248a 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 076fbcf8a2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 056a34719a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 7ee0e2a10b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 6ce3f60e1b 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 40a31d1d1a 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2de18223c3 103: onsuccess: #589: 1: Success after binutils: 3 commits new f5c1fe43a9 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 89612b7c08 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new ca139cb31f 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 0452b5b835 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 7c4869a2b5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 55b3bd2b80 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 27d989623f 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new a9ad00a7f5 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 6f7287235c 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new b8f2c907ad 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 1c5381e338 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 6cb2b469ea 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new e4fb6a76c7 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 55aa8106fe 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 0589e7e190 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 9b6e7cebe1 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 4517054be5 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 3c29690fdd 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 2bce347912 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new f08cd45dfd 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 9fecf54710 124: onsuccess: #612: 1: Success after binutils: 18 commits new 3e5aaad2d2 125: onsuccess: #614: 1: Success after linux: 12 commits new e1c0bb56f5 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new fd16adcff4 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 45b8ec3224 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 93c7cb4069 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 6988b5962f 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new de07a5d9d9 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 2ac05cd1f9 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 26f9e5b4ec 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 1d4bae1578 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 65368bdcd8 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new d59a9f3a93 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 012a5c3a49 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new b10705b9ea 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new f94e7f2a0c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 26a41acaad 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 0ded5a2bc0 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new b243985fe7 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 89c42d8788 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new da46a90983 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 498f11110d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 0e4fc31f87 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 76c454a0b1 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 48fcecc248 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 432928a33f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 32363c143e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 9a43779055 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 17e044bcdf 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new eadb432219 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new b265c698b4 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new c990a843a2 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 657469d3a0 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 7c189d98ec 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 694efcf3cd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 390e73fddf 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new b193a3ff50 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new cba9932696 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new b3a5fac286 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 661a788d72 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new fd46016330 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 5a9ab14857 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 4f93725d5b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new cead47fdcd 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 3849c38d62 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 599509c61a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new f7e7d5c26a 170: onsuccess: #664: 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 (e70a663a17) \ 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 1752 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 51472 -> 52084 bytes 04-build_abe-gcc/console.log.xz | Bin 238116 -> 238680 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 235868 -> 236128 bytes 08-build_abe-gdb/console.log.xz | Bin 51136 -> 50636 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2128 -> 2264 bytes 11-check_regression/console.log.xz | Bin 10136 -> 10144 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 41 +- 11-check_regression/mail-body.txt | 168 +- 11-check_regression/results.compare | 78 +- 11-check_regression/results.compare2 | 2561 ++++++------- 11-check_regression/results.regressions | 78 +- 12-update_baseline/console.log | 64 +- 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 | 170 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 78 +- sumfiles/gdb.log.xz | Bin 1863512 -> 1819980 bytes sumfiles/gdb.sum | 6107 +++++++++++++------------------ 31 files changed, 4074 insertions(+), 5327 deletions(-)