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 f951d5485b4d 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] discards 2dff7be9f8ee 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] discards 26f1e1e69bed 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] discards 0eadb10dddce 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] discards 89a897961ae8 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] discards 6f30f353fc17 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] discards 0f024f0e28e8 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] discards 445663799869 122: onsuccess: #909: 1: Success after linux: 2753 commits discards c4761bde0313 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 30d8c4b4016f 120: onsuccess: #906: 1: Success after binutils: 29 commits discards d30f5c9b613d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] discards 25fa4dddb1f2 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] discards 11c8fd710739 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] discards a8f8ee0f21d6 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] discards e80dbdb5650d 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] discards e7c6de495358 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] discards e278362fd595 113: onsuccess: #898: 1: Success after linux: 3 commits discards 343bd61a6429 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 602a66fd3f10 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 291894ff4f29 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] discards 423e7f6e7ba7 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] discards 665e219c2641 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] discards af95e40dc876 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] discards a3a076706b29 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] discards ee875b22fa52 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] discards 5175b83ff785 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] discards cce16cd51dd6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] discards a81b68dc1ee2 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] discards e435dfc74515 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards 915663051277 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards b4a4bd611e4b 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] discards 110b7eda244c 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] discards cc0d501548be 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] discards 34f222fca35d 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] discards 714b49875d67 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] discards a2cc6620f997 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] discards 436b575a398c 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] discards 87f05a395c91 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] discards b95e8f268a6a 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 64135375d9d1 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 9e5ec9e8844f 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 4de9cf8b2ec7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] discards 9b0f3c449efe 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] discards 7571424a1737 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] discards c06f4f256652 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 3651245f6772 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards c984edbc3016 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 9676d7e59a0d 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 86253bcc97a4 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 2f9e065ba6e9 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 8f5cecabe4d9 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 52b3683dbb5d 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards c85df5d2cb42 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] discards 90d4a7d5bcfa 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] discards 731dd999dc42 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] discards 461a31bc29ba 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] discards 7c2329862d43 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 49ec05f1d6a7 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards bc96aa9b06f2 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] discards d255b924b1a6 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] discards 7ab58ebc71d2 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards b7a007e91390 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 27b7ad9fc8bc 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 680ab0738f22 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] discards fd0b5216acd8 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards 397bcf3c9c53 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 04e3fca24e80 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 9ac6074b73eb 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] discards d2a712f0bb9a 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] discards 31b907db23fe 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] discards f6b8e9604e78 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] discards ce958e3865ba 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] discards 0724a4585c24 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] discards eabb5f919185 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 215f29632294 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards b245a59aa1db 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards e3715d7701ef 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards ca41b96d28a1 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards 06bb12b6ba37 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 655d53f7150f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards d7957b85b37c 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards e20eac871ff4 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 367688a14f5a 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 9d1388d5aa6a 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 7416d2e6bbac 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 72c58df5cb0c 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards b074d5e8de0d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards 9f774cb64f59 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards 0abbfd9dfffd 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 57fc458af52c 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] discards eab83e63c1c5 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards aafb4acdd964 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] discards 6aad927f6f3d 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards af447ac6659a 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] discards dc2f58fb575a 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards ec15716db245 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] discards 6283d49a2a53 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards 424e63c01e9e 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 49f0ad102c4f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards df0025b6624b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards c998b5e28a66 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] new 781ee7694a2c 29: onsuccess: #797: 1: Success after binutils/gcc/linux/g [...] new 6de8811a429d 30: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new fcbfff623e7e 31: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 762fb7d41c2d 32: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new e7e00262a6d1 33: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new d38f62bfebcc 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/g [...] new b24e358b0562 35: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 9fafddeadf22 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/g [...] new 6fe5f360957d 37: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new c4582d06ca37 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/g [...] new ab2bb2ae6c08 39: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 5e9ad08c067f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/g [...] new fb7667ef5af3 41: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new 23e002e57f42 42: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new 69d0fa4108d0 43: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new 8231c6615004 44: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 978e4e7c1323 45: onsuccess: #815: 1: Success after binutils: 6 commits new 71546ac3c780 46: onsuccess: #818: 1: Success after binutils: 10 commits new b606d0740e39 47: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new 4f90ce24795e 48: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new b334683b6ad1 49: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new 21c4d1d2373d 50: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new 2d6069bcdac7 51: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new 07b0bdecda37 52: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new 62382a4d3c92 53: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new 7c417386c18d 54: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 618b19a2cc69 55: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new 3979a037e561 56: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new 014cf35b4b38 57: onsuccess: #831: 1: Success after binutils/gcc/linux/g [...] new 5fd3c2b40e35 58: onsuccess: #832: 1: Success after binutils/gcc/linux/g [...] new 0e1468380f59 59: onsuccess: #833: 1: Success after binutils/gcc/linux/g [...] new 90485d274d06 60: onsuccess: #834: 1: Success after binutils/gcc/linux/g [...] new 07d2e72ab543 61: onsuccess: #835: 1: Success after binutils/gcc/linux/g [...] new 66c3043bd395 62: onsuccess: #836: 1: Success after binutils/gcc/linux/g [...] new 4bfa5abae363 63: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new ef7ac46f8fb2 64: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new 080cb85adc2b 65: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new a1284860c6c3 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/g [...] new 2ad9c941b64e 67: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new e3ebdd10931e 68: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 816886134719 69: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 3da5b6612594 70: onsuccess: #844: 1: Success after binutils/gcc/linux/g [...] new fccefa529aed 71: onsuccess: #845: 1: Success after binutils/gcc/linux/g [...] new a4106c414386 72: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new bd42af191bdd 73: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 1b3095cc7986 74: onsuccess: #848: 1: Success after binutils/gcc/linux/g [...] new b88fadb18293 75: onsuccess: #849: 1: Success after binutils/gcc/linux/g [...] new 8cacd2cb8b09 76: onsuccess: #850: 1: Success after binutils/gcc/linux/g [...] new e8d2aad774cf 77: onsuccess: #851: 1: Success after binutils/gcc/linux/g [...] new 6781554a8823 78: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 00a0b8830700 79: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 24055d96d14e 80: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new a99b1d35ca6b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 20dab2066b29 82: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 9506482f1de9 83: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 4ca7c16ede29 84: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new e98ab9c30afe 85: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 1d6610fec9d5 86: onsuccess: #860: 1: Success after binutils/gcc/linux/g [...] new 5f1b7d136388 87: onsuccess: #861: 1: Success after binutils/gcc/linux/g [...] new cf6e7a671702 88: onsuccess: #862: 1: Success after binutils/gcc/linux/g [...] new 390a647d1d6e 89: onsuccess: #864: 1: Success after binutils: 25 commits new b397fef28684 90: onsuccess: #867: 1: Success after binutils: 4 commits new 06c948b6e81a 91: onsuccess: #870: 1: Success after binutils: 5 commits new 394c0d926682 92: onsuccess: #872: 1: Success after binutils/gcc/linux/g [...] new 277bf3c4b68a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/g [...] new d12f1bd346d3 94: onsuccess: #874: 1: Success after binutils/gcc/linux/g [...] new e1243a8da49b 95: onsuccess: #876: 1: Success after binutils/gcc/linux/g [...] new 99473a8b5352 96: onsuccess: #877: 1: Success after binutils/gcc/linux/g [...] new 51f956fa49e2 97: onsuccess: #878: 1: Success after binutils/gcc/linux/g [...] new 5f1ad5b550bc 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/g [...] new 1159e20b59fa 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 [...] new b351338e9381 100: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new 7b112b7091c9 101: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new 4615dcf0e150 102: onsuccess: #883: 1: Success after binutils/gcc/linux/ [...] new dea110e19074 103: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] new 935dbb754230 104: onsuccess: #885: 1: Success after binutils/gcc/linux/ [...] new 5085acb4bc66 105: onsuccess: #886: 1: Success after binutils/gcc/linux/ [...] new cdd3a27e21cf 106: onsuccess: #887: 1: Success after binutils/gcc/linux/ [...] new cf069cbd416a 107: onsuccess: #888: 1: Success after binutils/gcc/linux/ [...] new 4b2b37b25b25 108: onsuccess: #889: 1: Success after binutils/gcc/linux/ [...] new 1cf1d4affbf4 109: onsuccess: #890: 1: Success after binutils/gcc/linux/ [...] new 3246c4b02da6 110: onsuccess: #891: 1: Success after binutils/gcc/linux/ [...] new 7dc4c21d019d 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 5f4157fd1e39 112: onsuccess: #896: 1: Success after binutils: 24 commits new a77c5d4ece92 113: onsuccess: #898: 1: Success after linux: 3 commits new 80c0c45811cb 114: onsuccess: #899: 1: Success after binutils/gcc/linux/ [...] new 6005c9196ed6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/ [...] new c9b843c6a97f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/ [...] new 9063dd1ec5b8 117: onsuccess: #902: 1: Success after binutils/gcc/linux/ [...] new 80287a18764e 118: onsuccess: #903: 1: Success after binutils/gcc/linux/ [...] new 6de2c48a538d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/ [...] new 3ba9532d5dd4 120: onsuccess: #906: 1: Success after binutils: 29 commits new 24da19c36d00 121: onsuccess: #908: 1: Success after glibc: 2 commits new 49d117b28bac 122: onsuccess: #909: 1: Success after linux: 2753 commits new 96b8238e9fe6 123: onsuccess: #910: 1: Success after binutils/gcc/linux/ [...] new 28b91095f6eb 124: onsuccess: #911: 1: Success after binutils/gcc/linux/ [...] new a191a8e1baad 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] new 64502159081f 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] new 0056005bae56 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] new aec1e8e03e1f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] new fcba92118d6e 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] new 23d9c24e7677 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...]
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 (f951d5485b4d) \ 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 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40056 -> 40108 bytes 04-build_abe-gcc/console.log.xz | Bin 216476 -> 217264 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9172 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 244584 -> 244668 bytes 08-build_abe-gdb/console.log.xz | Bin 39296 -> 39124 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2232 -> 2284 bytes 11-check_regression/console.log.xz | Bin 14772 -> 19652 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 60 +- 11-check_regression/mail-body.txt | 209 +- 11-check_regression/results.compare | 122 +- 11-check_regression/results.compare2 | 3948 ++++++++++--- 11-check_regression/results.regressions | 117 +- 12-update_baseline/console.log | 38 +- 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 | 211 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 117 +- sumfiles/gdb.log.xz | Bin 1909608 -> 1927284 bytes sumfiles/gdb.sum | 9597 ++++++++++++++++++++++++------- 31 files changed, 10920 insertions(+), 3553 deletions(-)