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 f42726ad671 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 87149c28765 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 99114195cd8 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 143597b9d87 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1c75ca6d2c8 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards db2ab0f8de5 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2e1a5fcde3a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 20b51b06cf9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 625926bf491 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9784d034d89 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 178abaecff8 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards f903ce1f5c2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 8baeeb222d1 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 3723fcf875c 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards a4e89db554c 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 152553cb179 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 1f83acbf8f3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 6c6c2262a5d 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 5e3200bd5d4 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 1acc8e86f6b 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards bd00dd17ddf 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 71b1a417fc1 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 19097b4b21a 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards d3c03d7bb96 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 09b86c1613d 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 99476144c1f 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 57eca79bf1d 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards fb8521603d3 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards e8ccbdf5be4 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards e4ebd9d0f45 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 6f436dbbefb 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards e8f0170fc4c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards bc1b70d1f19 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 5325862bcdb 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 1ef4bdfd474 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 534df809bc6 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 7aaeffad619 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9f548d3467d 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 54186c896d5 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 51e7dd48aee 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 8c188a50783 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 085b730c658 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards fbb03fce523 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 7d9157e776f 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 203923c26dc 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards c6e77266f23 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 734001b9843 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 2e39329136c 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8da95baf731 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 1678a4c08c3 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 6f3de9eb0fb 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards caf2290f99b 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards d9005c2820f 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 6dd21b269bc 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 48dbc7dcba4 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards edb55622a44 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards bf4b817acd6 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards b72cf915003 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards dead2a097fa 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 26f47f1e1bc 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards a64ca28686c 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards dbe554ed306 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards e88f2e432f1 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards d9368b48ca4 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 9e225321a07 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 0085818e167 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 29b55984cc0 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards c2a01c22989 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 70e054c9fac 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 10523db4d06 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 846fb98efea 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 475b4c132f6 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards cd3eb540b74 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 57e613bfc46 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 44d6b39ad3c 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards fd9e5bdde0f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 6f18a810584 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 57525691af6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 0db30703e66 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 3626e6c5a49 125: onsuccess: #614: 1: Success after linux: 12 commits discards a024effa05b 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 952b7ca2407 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 5fc6c202274 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards ba107db7678 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 5d8cb9714cd 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 0853bd92569 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 8f2ee92b36b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards cbe0e744ac8 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards c4934a9f1cf 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 91166f577ff 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 4f3ef4a0480 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards bf6ed6dd973 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards ac02db36dd7 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 506418dc475 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 03ec27b4504 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards e4fb7f4d962 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 077f2527f83 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards cf8d1287ae3 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 55034f2159f 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards e9c024321e5 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 54a2688aa58 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 66a7ecc41c4 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 96f99acd72f 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 23098f17a1a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 55845ce3db8 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new e5518cf5036 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new b48c648b1c1 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 4c7cec082e0 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new d1e9ce70f4c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new d03952b7210 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 4fb72f0b828 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new d8541d1f3e3 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 2a17fe37bad 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 9afadb1a4ea 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new d76c14491b7 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new ccfb48ca5c0 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new ca419d89a5b 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new e7e9e3fedcd 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new fe2bbfb00b2 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 8c920cb739f 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 2240af1faab 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 99f51169ab5 124: onsuccess: #612: 1: Success after binutils: 18 commits new 375968e7da1 125: onsuccess: #614: 1: Success after linux: 12 commits new 3b87c8dde98 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 49bd356b6a3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 413322d175e 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new ccbdfffdd4f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 891973390e1 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new d1201b05be7 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 4af97a29873 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 2003cda7726 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 42c0ef91aa0 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 3b26d4424dc 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 1ea4dfff72d 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new fdf9f95673e 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 2272142be17 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 53bfd2e48f8 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new acb433b90d5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new bf933db4032 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new ad8102376d4 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 70d5a2a73e8 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new b9f68048942 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 7240af720e0 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new eb9634f2e84 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 78e07290ab5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 94e19fa00ca 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new e1bc7ba9970 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 36190add4f3 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 15f7ebc1a1a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new b7fb589a45e 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new aadae350937 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 385c201b529 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 30aae4b30fa 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 42e1fa6496f 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new dd14ed26e0c 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 7c635f295fa 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ec58c9a5943 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 32134f867e6 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 1178181b02c 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 32dc48294d8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new be94c6e1406 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new a64d468b0bb 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 65214ac32d1 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new cd79be3796c 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 22330c49425 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 23d2ff89cbb 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 7b83349d8dc 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 82a0f8f2f1c 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 6fa4e49ed90 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 225380f5023 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new f07e4570432 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new d818d322534 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ab0a9e5dde0 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 48f0d900246 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 34f824e3b2a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 6abd5214fcc 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 803d4dce5c5 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 353357154f8 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new dbdbfc2c9f4 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 82947a6c5ed 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 2324144cf2b 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9c8c16eb4b0 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new a859e3986be 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 42720cd079c 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 95a826e8852 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new e4fbc3c4482 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 7dd8f268c1e 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 67f6b6f1b97 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 0d9cd421160 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 61eb7d6bfaf 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 49491ba3f52 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 798a364e85e 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 35b5e308ac6 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7a1ec0e2555 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 8576aaf98cd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ca48664377d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 2e2ccdbe167 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new bc78622a584 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ccd9f675029 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 4d50fb1b3b6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a16d98a8cec 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new fafdc3a651a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 888161dd0f5 205: onsuccess: #14: 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 (f42726ad671) \ 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 1780 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 53080 -> 52600 bytes 04-build_abe-gcc/console.log.xz | Bin 237836 -> 236468 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9572 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 236176 -> 235904 bytes 08-build_abe-gdb/console.log.xz | Bin 51500 -> 51008 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3756 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2340 -> 2008 bytes 11-check_regression/console.log.xz | Bin 8424 -> 7620 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 34 +- 11-check_regression/mail-body.txt | 127 +- 11-check_regression/results.compare | 67 +- 11-check_regression/results.compare2 | 323 +-- 11-check_regression/results.regressions | 67 +- 12-update_baseline/console.log | 62 +- 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 | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 67 +- sumfiles/gdb.log.xz | Bin 2941420 -> 2949580 bytes sumfiles/gdb.sum | 4389 ++++++++++++++++--------------- 31 files changed, 2529 insertions(+), 2792 deletions(-)