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 ad747f2e3d 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 392dfa6a66 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 00a28c7bcf 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 2e3ebe7915 103: onsuccess: #589: 1: Success after binutils: 3 commits discards ea04f6bd58 102: onsuccess: #586: 1: Success after binutils: 5 commits discards a41198e345 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 215d329b19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 8169404e1c 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 62bc4158ef 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards aca0690a23 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards befb26d69d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards a000c011ed 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 29ea301e62 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 100ce21e48 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards dba7d1e11e 92: onsuccess: #575: 1: Success after linux: 34 commits discards a7f6c58097 91: onsuccess: #574: 1: Success after glibc: 3 commits discards fed377228d 90: onsuccess: #572: 1: Success after binutils: 15 commits discards ec347c2585 89: onsuccess: #570: 1: Success after linux: 11 commits discards e0ff28adff 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 1aa01191cb 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 39bfa66f21 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 3cd4dbca77 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 1a47a816d6 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 40b9073650 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards c465d66047 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards e192a66f8e 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards c672fd7499 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 0b25d5aa10 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards ad9a789ccd 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards e963165e3c 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards bed8ef6a42 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 444aececee 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 525532b8f3 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 0f59dffd17 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards a03398ca7e 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 8ffbbc92ee 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 19a82fb123 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 97426bd3c1 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards f262f1324c 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 56e564ddf5 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 94e803c109 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 5307912a3e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 10903702e7 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 8f443aa285 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 4e0bdea030 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 4a99154121 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards ff8fcff926 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 15cec891ca 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards a0cca6d0cb 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards dc7839abcd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 9896efad77 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 4fa56bd985 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards cd5a26e911 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 0c4f3d1156 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 7f4d2dd5a4 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 8d0c649601 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 15b85290e1 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards bebf7d5de2 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards f5e4da360d 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards b3148e607d 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards c833816993 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards d1f1de0cd5 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards b66ec19316 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards bf07112156 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 20d5900039 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 1c3c284af0 41: onsuccess: #514: 1: Success after linux: 64 commits discards 66b2b43da8 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 2285660d25 39: onsuccess: #511: 1: Success after binutils: 8 commits discards b6fa846f3c 38: onsuccess: #508: 1: Success after binutils: 3 commits discards c038def0d7 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards a4e440be8c 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 17f7110de3 35: onsuccess: #503: 1: Success after binutils: 11 commits discards dac5f1f34c 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 70c71db5c8 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 056ebbb339 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 1d2dd0523e 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 8f5777b3d0 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards d65a6fadb1 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 3e2fe46b77 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards a6706e2e5c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 5df662e489 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 8e709936ae 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards d73433debd 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards fd8888600b 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 92210b90a7 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 650cd0cc02 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2f308d36f8 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0da74e70c9 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2d4a47d35f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6581c62d02 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1f7c6180a7 16: onsuccess: 1: Successful build after binutils: 4 commits discards a939f5d5e7 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 525dbb1f0f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aac2287c9b 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7edfff1467 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f8e89a11d8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8ee62b579 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a78e8288c 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 21315fb335 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 2a35d72b3d 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 9211da7af4 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6f538a74a9 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9c68dfa7de 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new fa4a640749 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e863e8c536 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 40b5deb2df 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5edfc42f2b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5134493b6 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ec804e0b0d 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 28b1e7cfec 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c2da457e6c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebe95edac8 16: onsuccess: 1: Successful build after binutils: 4 commits new 61e0ce5440 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1cec99ab96 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a6f04bee1 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 41a230dc9d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a259b3e853 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e2188a4b54 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ec53d3d88d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new f66e4f08a0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new a44a178fd9 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 9e712a6c6d 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 96035bc2e4 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 09aaabba77 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new fa00a7e1df 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 1e33c13ee9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 51f63a324a 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 234d81bf5b 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new f101e78d5d 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 308ddd570a 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new cb9a98c86a 35: onsuccess: #503: 1: Success after binutils: 11 commits new db418681ed 36: onsuccess: #505: 1: Success after glibc: 3 commits new 1563b9c851 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new cf52af0506 38: onsuccess: #508: 1: Success after binutils: 3 commits new 760ad34f29 39: onsuccess: #511: 1: Success after binutils: 8 commits new f306ee8053 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new e846ccb5e3 41: onsuccess: #514: 1: Success after linux: 64 commits new 6dc24c3733 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 8dae927960 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 8b1b807366 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 247cfe95f2 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 7f22e8f203 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new d93182586f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 00a05ed7bc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 1ad35f0736 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 2f581cbfce 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 84238ea724 51: onsuccess: #525: 1: Success after binutils: 8 commits new 2819bb557d 52: onsuccess: #528: 1: Success after binutils: 8 commits new 169d0130e4 53: onsuccess: #531: 1: Success after binutils: 12 commits new 3299e19375 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new ea40d9ed7b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new be2d1d8787 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 3da1fb3cbc 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 97473bb138 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 9a87ddc45b 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new de857ee181 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new bf669c3527 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new f3c0c223cb 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new d6c98c7274 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4d2419c12b 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 3f3b2a9da6 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new c63e232f4c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 4404a9a057 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 513758380b 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new bcd630e1b2 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 22ef809bfb 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 6adc9073f9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 97dd94fd41 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 600950e063 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 1190b00d1c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 733726095b 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 4af6444f9e 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new d0156a255c 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 3875d8918b 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 04e5573a3a 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new e1c2f4ea3f 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 06bd4c0250 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new b327b4b92e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 31a72aca3a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new ea0fcb6f63 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 5f87a3c9bc 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 99dcf97145 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 74e94904c2 87: onsuccess: #567: 1: Success after binutils: 8 commits new d9a8d91029 88: onsuccess: #569: 1: Success after glibc: 10 commits new 3e1d86bf28 89: onsuccess: #570: 1: Success after linux: 11 commits new 46edf05259 90: onsuccess: #572: 1: Success after binutils: 15 commits new 56404bda13 91: onsuccess: #574: 1: Success after glibc: 3 commits new 8df4275e9e 92: onsuccess: #575: 1: Success after linux: 34 commits new c142a08264 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new d97330c9d6 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 51a1c3bce5 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 780d841699 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 8f5bcb2cdb 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new f59d32eeea 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new ce6afb7a90 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 7e8350ed19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 495deb9955 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 7429bbe90e 102: onsuccess: #586: 1: Success after binutils: 5 commits new 25ca9dc340 103: onsuccess: #589: 1: Success after binutils: 3 commits new 954658d918 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new a3529a00b1 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 4b79ce8a09 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 36bdd7eb49 107: onsuccess: #594: 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 (ad747f2e3d) \ 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 1736 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 53736 -> 53296 bytes 04-build_abe-gcc/console.log.xz | Bin 234392 -> 236832 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8428 -> 9200 bytes 07-build_abe-glibc/console.log.xz | Bin 235732 -> 236028 bytes 08-build_abe-gdb/console.log.xz | Bin 51668 -> 50916 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2280 -> 2624 bytes 11-check_regression/console.log.xz | Bin 11272 -> 11888 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 46 +- 11-check_regression/mail-body.txt | 188 +- 11-check_regression/results.compare | 87 +- 11-check_regression/results.compare2 | 3905 ++++++++++------- 11-check_regression/results.regressions | 87 +- 12-update_baseline/console.log | 40 +- 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 | 190 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 87 +- sumfiles/gdb.log.xz | Bin 1806128 -> 1728584 bytes sumfiles/gdb.sum | 7182 ++++++++++++++++++++----------- 31 files changed, 7285 insertions(+), 4581 deletions(-)