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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 9e24e503b4 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards b7fe61c15e 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 47c902f6b6 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 7f0c30b1cd 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 4c4ef76ec6 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 2f25e84e95 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 3e0986460f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards eebce76ff7 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 64714af42c 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 208e765723 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards c52a8413b2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards bc422a6aee 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards b3a62c2ac8 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 40c661f858 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 45f0e79f88 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 53e46c8481 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 57d53d69e9 127: onsuccess: #874: 1: Success after linux: 219 commits discards c2c8d7b216 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 3f0aae12fc 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 01dc0e7770 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards a53a6da6e2 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards f8f52511f9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards c8ec0f95de 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards ad3e31ab15 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards a1dc543e81 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards bbfc7f4c4e 118: onsuccess: #863: 1: Success after linux: 12 commits discards 6dfc06d53f 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 14dd49d2f6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 077c2cbb9c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 63bfd40657 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards f472b2d4e8 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards ebf0d2ae5f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 1dee7cb721 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards caaaaf475e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 93964a6905 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 761c2b3ae1 108: onsuccess: #850: 1: Success after gcc: 2 commits discards a31262c584 107: onsuccess: #849: 1: Success after binutils: 5 commits discards f40d4a077e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards cb0b49ec3d 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 58aa93f7d8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards be036af736 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards b352e63d62 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards ccb41f6f46 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards c45035f4c8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards c691098b47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 8cbf686355 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 36d98ca4f8 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards e324ddbe4e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 26e8dd63c8 95: onsuccess: #835: 1: Success after binutils: 3 commits discards cd5e7f0fdf 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 9c9c9eb441 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 4b78d222a5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 56e449485d 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 807e08b410 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards e67a1c2f3c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards f853c97731 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards f697139498 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 385ae38bf4 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 85971cc643 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 0048c063c8 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 3b53ef1483 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards de924adcd0 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 2e222f9989 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0b6dac95f8 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 2bd598b802 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 12af03224b 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards f1862164fc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards f895d6eac4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards e0a60bc39d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 177dfe372c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards b711be8381 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards c40cceb691 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards d905362749 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 63bf975e38 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 57a0d4f843 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 4a625c12ab 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 26df8d8547 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 6a67f5cae2 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 290a1193d7 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards cf895c42f4 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 4375eed3ec 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 2e6c1f5ed7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 9d46137902 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 7ec5826572 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards e81113a750 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards d5264bd26f 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 9c056a71fd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 02ec84db40 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 7a8fc7708d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards bd745a82a2 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 6637b4e30f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 51f590e967 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 9ca0279232 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards b0626addad 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards d41a8315c3 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 8832bfaa9b 48: onsuccess: #782: 1: Success after binutils: 8 commits discards a55848614d 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 185c5f25f4 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 92fea1ea6c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards b4bb5f776b 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 8b8a0b1e00 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 7e4596d41e 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 29d1b93781 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new d365b578f5 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 74c31ad4d5 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 1adc18cce2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new b31b100852 48: onsuccess: #782: 1: Success after binutils: 8 commits new 0b1b120554 49: onsuccess: #785: 1: Success after binutils: 12 commits new 0415cf1c39 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 1292b09ed4 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new e1ccc60399 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 543cd79c6f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 6cd53f163a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 96526bfe65 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 295774c30a 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new fea32b80b9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 36a5002f8a 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new fba45f217b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new f39f6a3c44 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 10e94b81f1 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 5327f1d355 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new df2ccd9da0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new f5eff59d75 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 5dd1ae1133 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new aad3b641d6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 8f65c70663 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 268bbffdee 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 80b074a62b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new ebb6b78f0c 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 24ee31c89b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 5e267444ee 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 04ff134229 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 8683f57d9c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 333065644e 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 3ec44caac0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new d54a435ee4 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new dfac8582f1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 7f59f761ac 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 7e3881f187 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 080ba6c4f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 402f69e6ef 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 8691904441 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new cbfd8fd6fd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 36e0550617 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 76badb6424 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new b490c099f6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 2400f643e0 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 9d5c42b655 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0f54c2e826 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new abc07571a3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5b4accfc6b 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 06df8271ed 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 026786b387 94: onsuccess: #832: 1: Success after binutils: 5 commits new 3ca9126fdd 95: onsuccess: #835: 1: Success after binutils: 3 commits new 06988a334f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 96b0f5b851 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 568d9cdc57 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 94d02e6b04 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 52e95e95a8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 55a98a2798 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new aecfdbdc96 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 985666ec4a 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 2ff6e6f6ab 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new d145dc8d4f 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new c48b7da249 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 8f5c62498e 107: onsuccess: #849: 1: Success after binutils: 5 commits new c71a7d355a 108: onsuccess: #850: 1: Success after gcc: 2 commits new af304e8035 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 7b3ce70931 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new d6ed9c2243 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new fd0c431ead 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 0401b9c15c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 6f14db952c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 7d3409d1ab 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 574c04f0b1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 530eba5ce5 117: onsuccess: #861: 1: Success after binutils: 18 commits new 85fd1a565c 118: onsuccess: #863: 1: Success after linux: 12 commits new fb41c51340 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 2e394f9b39 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 97d336663c 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 641a9d8151 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new c421e848fb 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 47c1b23d33 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 835dd77589 125: onsuccess: #871: 1: Success after binutils: 26 commits new 657c50cfcc 126: onsuccess: #873: 1: Success after glibc: 2 commits new 6bc40fe449 127: onsuccess: #874: 1: Success after linux: 219 commits new 81023c14aa 128: onsuccess: #876: 1: Success after binutils: 12 commits new 4c87e70201 129: onsuccess: #878: 1: Success after linux: 3008 commits new faa1da1510 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 8729bb78a5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 0fb0b1148a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 006b8a3763 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 9c385c1025 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new cacb58b1df 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new b30d62a1f9 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 74297ec058 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 839d381ef7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 112ace12b3 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 3c4bcacabc 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 978d00d000 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 3e41c40e51 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 375724eb76 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 77a393f38d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits
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 (9e24e503b4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40344 -> 39800 bytes 04-build_abe-gcc/console.log.xz | Bin 214880 -> 214496 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8348 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 244776 -> 244684 bytes 08-build_abe-gdb/console.log.xz | Bin 39712 -> 39348 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2424 bytes 11-check_regression/console.log.xz | Bin 5464 -> 5656 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 18 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3768040 -> 3731524 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3313864 -> 3291524 bytes sumfiles/gcc.sum | 4845 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1081568 -> 1079284 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232920 -> 232132 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 459756 -> 456444 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2607 insertions(+), 2598 deletions(-)