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 ffa457e1f0 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 9389bc42a0 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 17c8294e70 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards c9213a36e7 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards e7f228bcc2 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 78d197364d 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 17b0eb7758 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 0f87fcc601 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 6fe3724ece 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 3c0b389af9 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 8f66a4b45d 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards eba58818f0 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 2e6624ea34 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 89614bd853 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 855c129d37 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 3432d2d0df 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 1ecfc56df7 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 28747f43c3 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 6f8a811fa9 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 3c85d319bd 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards c3a4641499 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 6a1a6c60e4 122: onsuccess: #909: 1: Success after linux: 2753 commits discards bf625bff63 121: onsuccess: #908: 1: Success after glibc: 2 commits discards e1ea228eda 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 49920cca41 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 76778e274d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 51755eeedc 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards f753118b2e 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 9060ebf013 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards aafd2358fb 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 79e10b6fba 113: onsuccess: #898: 1: Success after linux: 3 commits discards 903617817d 112: onsuccess: #896: 1: Success after binutils: 24 commits discards b2d8b08f85 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 2d3987c43a 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 033ecf65a2 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards d398c62a2e 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 032923d343 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards f3422cb5fa 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 5fdaa6ea01 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 4d089170f9 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 6eb1845268 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 10a8c1000f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7301fa5d8e 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 5e9c03fc91 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 148a8a24a3 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards c00ebdff8d 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards b9e76d0d77 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards e5e9e8f2b6 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 4619ddb9a8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 89d440bd31 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards cb3bde1476 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards dd847c6805 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 8a1811dd90 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 0ca16ad358 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 160427677b 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 4bb64b6621 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 4b07e11584 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards d861f7f6bc 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 3a27746e7c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 2609f0d650 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards d33a80aca0 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards f10e15da71 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 47082dcfe0 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards c943836105 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 278cca1eca 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 845c80a851 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 7d36971db5 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 840307cafa 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 198f6d646b 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards b4a28522f1 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards a79dd8b20f 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 7bccad48db 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards f1938cc523 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 9d7b849a7e 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards b1468a8555 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards a2831c910c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 20b63eb5e4 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 5b8284f17c 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 5767e3a260 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 52e2a43fcc 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 012aa721ff 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards a6126c5c79 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards fb1c3a15bf 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards beedd6b2e3 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards fffe5abe17 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards e1e90d61a7 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 3eab7dd793 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards ec43f5d955 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 7f0d7fd131 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 85f5fe61da 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 11be73dd32 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 62ba30436c 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards ac7ef0b577 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 9aa90a5a59 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 04b717448e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 1775a0f458 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 1582403214 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards c93515b3da 46: onsuccess: #818: 1: Success after binutils: 10 commits discards c3077e7c84 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 58116e4693 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards b773a47d87 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new ce6e7cca72 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 00cb2694f5 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 69008a0074 45: onsuccess: #815: 1: Success after binutils: 6 commits new eedc58379f 46: onsuccess: #818: 1: Success after binutils: 10 commits new 1fb6a026ff 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 9fded8c126 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 78bd5e1158 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new d8d568a85b 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new bba6d7f953 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 15a89d30e7 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 5f9f424c66 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new d83e4513b5 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 1ab2738880 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new fccddc1772 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 434f61fc3a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 345ba63f1a 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 19e253863b 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 9eef2c9e4e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 68a8019dbe 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 965955ce80 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 03dad23496 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 51afc5779f 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 8b43091255 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 2cba38a0fe 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 954be2af0f 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 8f9a5514d2 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 58bc101122 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new c12d6e035a 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new c91b98c3cd 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 0bb487bdfc 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new bab5b6342e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 7f8e39840b 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new b9fdc32e06 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 48f54001b4 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 7dba43f97e 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 1a762c754e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new f3b5ac7372 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 88074fdad7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 0c5f781d62 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 6c7e8355e5 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 4bea49edf7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new c78ff4ee4f 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new d1211652d3 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 3aa7505f99 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new eaa8b5a497 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 6d11e4a667 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 42eece3d47 89: onsuccess: #864: 1: Success after binutils: 25 commits new 48fd8954ee 90: onsuccess: #867: 1: Success after binutils: 4 commits new c5d194df70 91: onsuccess: #870: 1: Success after binutils: 5 commits new 9dd29938ee 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 2f735ed689 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 2e0a938b9d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new c3f79f6cc7 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new a8d2981f76 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new e1c86130bc 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 88c3f11e71 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 69e8d23111 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new f01a322c1a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new aeaa88988b 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 91b6960c6a 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 5ff71188c8 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new fab931607a 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 32e6915d3e 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new a105701777 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 4635d83668 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 3be6e48e87 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new d995e9a6be 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 26d6d22786 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new f39c9a3eb3 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 8739302bf8 112: onsuccess: #896: 1: Success after binutils: 24 commits new 2558355f77 113: onsuccess: #898: 1: Success after linux: 3 commits new 2277008c51 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 73caba6f5e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 9a6f6b967a 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 2b7769f6f4 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 666e89c872 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 3002f43560 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 855c9030a1 120: onsuccess: #906: 1: Success after binutils: 29 commits new 86b15acf49 121: onsuccess: #908: 1: Success after glibc: 2 commits new 8e95954c69 122: onsuccess: #909: 1: Success after linux: 2753 commits new 1a3fe0c282 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 0f927dfceb 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 31e4626d25 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 929bccf409 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new a7c5ecd692 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 15aab9a95e 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new f38e24f2e1 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new a0ffbdb4fc 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new a263a830c7 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new d24309b1f9 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new b29c4520fb 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 8935dae9ef 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 90f9992b82 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 500ebe113f 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 9e844bd561 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 2ad9806c07 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new ef3dcee3a4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 1a05a14ec4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 947eb3f121 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new f4b2ce9b3d 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 7f6a79f72f 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 3d7a89758e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...]

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 (ffa457e1f0) \ 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 1776 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 40620 -> 41324 bytes 04-build_abe-gcc/console.log.xz | Bin 213668 -> 215908 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8868 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 244684 -> 244996 bytes 08-build_abe-gdb/console.log.xz | Bin 40016 -> 40144 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3948 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2256 -> 2600 bytes 11-check_regression/console.log.xz | Bin 15760 -> 18480 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 49 +- 11-check_regression/mail-body.txt | 201 +- 11-check_regression/results.compare | 124 +- 11-check_regression/results.compare2 | 8207 +++++++++++++++------------ 11-check_regression/results.regressions | 115 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 203 +- mail/mail-subject.txt | 2 +- manifest.sh | 33 +- results | 115 +- sumfiles/gdb.log.xz | Bin 1878432 -> 1920316 bytes sumfiles/gdb.sum | 9303 ++++++++----------------------- 30 files changed, 7541 insertions(+), 10865 deletions(-)