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 e8323e5666 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 57ecc9fb9e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 1e01531c53 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 33aed7791b 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 7241c59c1c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 442d96edc2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 2b7d0fa59d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 9aaba25af3 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 5af9a7f77f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 17ec99acd8 122: onsuccess: #909: 1: Success after linux: 2753 commits discards f577900930 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 65bcaeda62 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 6c6f60c128 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards ee7c3c4dd0 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 40e9a1bb5d 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards fa4043d955 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 1986d992a3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards eaa4e12348 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 8ebe270575 113: onsuccess: #898: 1: Success after linux: 3 commits discards ff0d021276 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 95be9af82a 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 52c1fdb53e 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 1034c0f6e0 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 754689aac0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 8b148611c8 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 1f2a546fd9 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 0c2f0350da 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards d5e535e51d 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards f91d183ab7 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards f4c6c1d200 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards a735ab0aae 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards d9aa027f3e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards f24ea4dbf6 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards ef168c51bb 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards a8d3efb453 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards e844c256f5 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 0d87b013bc 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 08541fd055 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 9643a1bcf5 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards d9a5acce01 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 9c859d421a 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 8feb52e079 90: onsuccess: #867: 1: Success after binutils: 4 commits discards a072671a14 89: onsuccess: #864: 1: Success after binutils: 25 commits discards f0ccae1beb 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 5a7ac9e4e3 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 826c00b9ad 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 2f9936b642 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards a824e1bc86 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 18e1671a6c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 2e65a5b720 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 5f242ea3df 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 8ed86fdeb7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 459c053f7f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 58b2793408 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 218e7aed04 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards a352837242 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 44c26028b8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards a753c3c68b 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 0b83945a9c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 9410760e9b 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 28cc87bd16 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 521c25cac4 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 4c159e91a8 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards f0744a8e6a 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 4beb021f84 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 5b9cf9bc50 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards f61652fcd6 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 8480b3f529 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards d100257934 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 9db0f172d9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 7e98896d5d 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 32728acc41 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 4a96b50952 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 11cb2ee18b 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards a460414523 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 9fec3d9bd1 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 66d533cdfa 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards c02405897e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards fe60a8fc41 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 5c83b56c6f 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards cd380c7d04 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 9ed1fe759f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 9576bef942 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 2978683100 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 73f37ee634 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards b060b4c02c 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 25b2e8e93e 45: onsuccess: #815: 1: Success after binutils: 6 commits discards bb0708751b 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 3326efef5e 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 69789c866f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards b291a1e804 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards a62cef7509 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 3b16700b78 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards c4a7c166a2 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 80cc4a2e3a 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards b54fd89e5e 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards bd8199ec72 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 699f1c7aa2 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 4d0bc121d0 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 21bf83b6fe 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 20b5093ebb 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new 68bb8108ef 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new fa9d2c7c5e 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new d38f1c24df 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 2d562f2597 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 043b84fbbb 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 2b1699a0f7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 577618bc2c 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new d2dfd71ff6 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new b08562e2d0 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 974951557b 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 87bf851867 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new c4ee8f5474 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 982a2bd066 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 6b2681ec0b 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 6d705f4be8 45: onsuccess: #815: 1: Success after binutils: 6 commits new 85b8469064 46: onsuccess: #818: 1: Success after binutils: 10 commits new b7f7a4ca47 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 51ffa5b2fb 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new df88a7d1b2 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 8fd0d2e183 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 89d0819fcb 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 515736b144 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new d62cd270dc 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 214ca7d270 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 551fd253d8 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 0fd29d9526 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new c01a728672 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new c7d1a318e9 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 858f6ec34e 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 7de1eefbdb 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new d4fb9f1ef1 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new ecbdc1e99f 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 7b8028e7fa 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 1c6cab2fa9 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new bf24fe152a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new eff632d1f9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 98071d6f84 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 41913bc587 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 0c93bd147f 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 8f6a7042e1 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new c3e3475dfa 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 4814af3524 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 695c0c24cc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new e4d3aff4fd 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 6b3d2fa426 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new da46239853 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 29e389896a 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new d91da83556 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 417019b146 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new b09aea5494 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new f8bd565d1b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 9b737b6ce6 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 0938bb40c7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 19d55c4533 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 1c9ee422df 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new fe056b4dc5 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 15fe23e98e 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new f14f0ddae7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new bdc40425d8 89: onsuccess: #864: 1: Success after binutils: 25 commits new 8242e6b414 90: onsuccess: #867: 1: Success after binutils: 4 commits new e4714c2a1c 91: onsuccess: #870: 1: Success after binutils: 5 commits new 8a14ab3531 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 0a547adc4b 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 935bea6e42 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 9cfe459bad 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new c1bee80025 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new da57026b78 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 79e0b213c8 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 5989301084 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 5faa341734 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 98a68171d3 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new cf1fe1bf37 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 166759e503 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new f3a91db686 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 5138d26c7f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 583ee9602e 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new d0d1d1ca01 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 5a17d0f695 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new e137d9a7f1 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 092c15e10d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 919cfd0cc9 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 2d4df4c321 112: onsuccess: #896: 1: Success after binutils: 24 commits new 1420d68ea6 113: onsuccess: #898: 1: Success after linux: 3 commits new 909b3c9685 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 9669d4af69 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 232525dcef 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new ca1588d37b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 24fe3bc930 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 2188191cc9 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new e1590d9069 120: onsuccess: #906: 1: Success after binutils: 29 commits new 7f6da679a4 121: onsuccess: #908: 1: Success after glibc: 2 commits new 54767ca56f 122: onsuccess: #909: 1: Success after linux: 2753 commits new ad10244e0d 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 11501d8243 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new cccbf445f6 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new fd21d2c1e4 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 662055e0cd 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 9c87cb3e9c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 4a5d0c4bfb 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 0b0b1c029e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 1fbb85d6d3 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 4c82651904 132: onsuccess: #919: 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 (e8323e5666) \ 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40824 -> 39980 bytes 04-build_abe-gcc/console.log.xz | Bin 215472 -> 215820 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 8692 bytes 07-build_abe-glibc/console.log.xz | Bin 245556 -> 245000 bytes 08-build_abe-gdb/console.log.xz | Bin 39752 -> 39396 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2128 -> 2128 bytes 11-check_regression/console.log.xz | Bin 13524 -> 11276 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 55 +- 11-check_regression/mail-body.txt | 216 +- 11-check_regression/results.compare | 121 +- 11-check_regression/results.compare2 | 4475 ++++++++++--------------------- 11-check_regression/results.regressions | 108 +- 12-update_baseline/console.log | 60 +- 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 | 218 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 108 +- sumfiles/gdb.log.xz | Bin 1956904 -> 1947788 bytes sumfiles/gdb.sum | 1395 +--------- 30 files changed, 1939 insertions(+), 4873 deletions(-)