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 3d7a89758e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 7f6a79f72f 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards f4b2ce9b3d 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 947eb3f121 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 1a05a14ec4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards ef3dcee3a4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 2ad9806c07 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 9e844bd561 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 500ebe113f 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 90f9992b82 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 8935dae9ef 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards b29c4520fb 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards d24309b1f9 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards a263a830c7 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards a0ffbdb4fc 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards f38e24f2e1 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 15aab9a95e 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards a7c5ecd692 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 929bccf409 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 31e4626d25 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 0f927dfceb 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 1a3fe0c282 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 8e95954c69 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 86b15acf49 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 855c9030a1 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 3002f43560 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 666e89c872 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 2b7769f6f4 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 9a6f6b967a 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 73caba6f5e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 2277008c51 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 2558355f77 113: onsuccess: #898: 1: Success after linux: 3 commits discards 8739302bf8 112: onsuccess: #896: 1: Success after binutils: 24 commits discards f39c9a3eb3 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 26d6d22786 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards d995e9a6be 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 3be6e48e87 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 4635d83668 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards a105701777 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 32e6915d3e 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards fab931607a 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 5ff71188c8 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 91b6960c6a 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards aeaa88988b 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards f01a322c1a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 69e8d23111 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 88c3f11e71 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards e1c86130bc 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards a8d2981f76 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards c3f79f6cc7 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 2e0a938b9d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 2f735ed689 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 9dd29938ee 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards c5d194df70 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 48fd8954ee 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 42eece3d47 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 6d11e4a667 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards eaa8b5a497 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 3aa7505f99 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards d1211652d3 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards c78ff4ee4f 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 4bea49edf7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 6c7e8355e5 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 0c5f781d62 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 88074fdad7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards f3b5ac7372 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 1a762c754e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 7dba43f97e 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 48f54001b4 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards b9fdc32e06 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 7f8e39840b 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards bab5b6342e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 0bb487bdfc 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards c91b98c3cd 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards c12d6e035a 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 58bc101122 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 8f9a5514d2 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 954be2af0f 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 2cba38a0fe 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 8b43091255 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 51afc5779f 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 03dad23496 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 965955ce80 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 68a8019dbe 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 9eef2c9e4e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 19e253863b 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 345ba63f1a 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 434f61fc3a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards fccddc1772 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 1ab2738880 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards d83e4513b5 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 5f9f424c66 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 15a89d30e7 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards bba6d7f953 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards d8d568a85b 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 78bd5e1158 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 9fded8c126 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 1fb6a026ff 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards eedc58379f 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 69008a0074 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 00cb2694f5 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 2fcc2c9de3 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 829faae66c 45: onsuccess: #815: 1: Success after binutils: 6 commits new f188a86f71 46: onsuccess: #818: 1: Success after binutils: 10 commits new 0eace92d8a 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new a3b5b262cd 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new ecb1b27fb3 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 91bfbd2168 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new d162fa0c96 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 3e18a062c4 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new f4aae7dca4 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 193610389b 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 62602b2dd3 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new cb9db5cfc2 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 02710a927c 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 67a120183c 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 24a4bdd077 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 659963a3dc 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 8b58a394fd 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 11d7d65de9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 1f8b768d43 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new df61512736 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 4a8e25dc24 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new f3138c29e3 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new a11efc9d2e 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new a70455a4d5 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 8eafec6dd3 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 7d6fc380d7 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 1a90ebd434 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new a9539501b1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 04f80bb9c5 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new c2a4f4a4c6 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new e3e4842f1e 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 2e644e1577 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new f5a9aaae75 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 3b7d202a6e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new aad1273d7e 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new a82d468516 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 34ff2295c3 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 1bf5b687b9 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new a403cd538a 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 681ea63580 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new feb2d55a1a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new e1273942a2 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 83a762685f 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 3d5c98ac05 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 18e325c140 89: onsuccess: #864: 1: Success after binutils: 25 commits new e3ccfe8281 90: onsuccess: #867: 1: Success after binutils: 4 commits new fe1a0a3fd7 91: onsuccess: #870: 1: Success after binutils: 5 commits new f86da65c74 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 836ce03bba 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 606ae8d3e6 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 68807b2e36 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 1df40ffc20 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 46ac6e6559 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 43994a6784 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 78af0ed760 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 1bb9c96c5e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new d41d473f0c 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new a2eb5ced73 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new d049de4381 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new aadeb4c382 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new e889922c43 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 37c1d17bc8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new ed20520f84 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 0910ef01fa 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new b0d9eba425 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new c071dc1602 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 94aaee1235 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 56789bbd1d 112: onsuccess: #896: 1: Success after binutils: 24 commits new fe672f2974 113: onsuccess: #898: 1: Success after linux: 3 commits new ccad635f1f 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new f475a8ff9a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new c330ff002c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new e905885766 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 18251104d4 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new f18763c681 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 155edcc2b7 120: onsuccess: #906: 1: Success after binutils: 29 commits new 365059444d 121: onsuccess: #908: 1: Success after glibc: 2 commits new e0887fda76 122: onsuccess: #909: 1: Success after linux: 2753 commits new 2beb06f5b1 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 8f29698dad 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 0fd9c070c3 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new ef6f603342 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 2247a2a66e 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 7491e7fd68 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 0f6eee1034 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 2dbb581ddb 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 009e5ddbd2 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 8ec3a36feb 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new b3b548a36a 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 54df76f2ed 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new a73f745772 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 49253c69f1 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 925fef68f4 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new c96d14d5c6 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new b3387dacd4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 0a250310f4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 5300b76615 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 963d80c91c 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 81f951ce76 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new f54de475c3 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 332f18e093 145: onsuccess: #934: 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 (3d7a89758e) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 41324 -> 39688 bytes 04-build_abe-gcc/console.log.xz | Bin 215908 -> 214916 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 8956 bytes 07-build_abe-glibc/console.log.xz | Bin 244996 -> 245528 bytes 08-build_abe-gdb/console.log.xz | Bin 40144 -> 39516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2600 -> 2196 bytes 11-check_regression/console.log.xz | Bin 18480 -> 21344 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 55 +- 11-check_regression/mail-body.txt | 205 +- 11-check_regression/results.compare | 90 +- 11-check_regression/results.compare2 | 4327 ++++++++----- 11-check_regression/results.regressions | 90 +- 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 | 207 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 90 +- sumfiles/gdb.log.xz | Bin 1920316 -> 1892492 bytes sumfiles/gdb.sum | 10340 +++++++++++++++++++++++------- 31 files changed, 11234 insertions(+), 4262 deletions(-)