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 e013fd4b33c 128: onsuccess: #876: 1: Success after binutils: 12 commits discards a6ad1c1d36b 127: onsuccess: #874: 1: Success after linux: 219 commits discards 3af8cabf8b8 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 1c426a74124 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 4183cc380f9 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards fd2bf22aae7 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards f3627707e26 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 68d1fa572d6 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 74a9870cbaa 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards b2c58b813ff 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards ad9a2de0d66 118: onsuccess: #863: 1: Success after linux: 12 commits discards 64ac98a4193 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 67464f41eef 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 8cc641a53cd 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 4a1ed264b71 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 6295e1492ee 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards c2e61198da3 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards ba82ab543e2 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 07db1483d29 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 8fd51f3ec19 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 1258c122dea 108: onsuccess: #850: 1: Success after gcc: 2 commits discards bacd61d48e0 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 541cb8a7875 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 6e51612a160 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards cc5814dcc96 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards a89c7aaea91 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards deb534468a7 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards f43497919da 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 750d69a394d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards cf07d2d2306 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 0a788a3479e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 3d5d20a2747 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 95d4d60d0d1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards eecf69684be 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 2d4fbdcd9d3 94: onsuccess: #832: 1: Success after binutils: 5 commits discards f668fdb4791 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards b52c4498bf5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 902351f8d53 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 6aa4c5a98c3 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e88ee6c0bee 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 7671406cd2f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards a601205f72d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards c9412b9c12b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 090046e7ed3 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 4445a6499d4 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 0d8d1a4b89e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 846a827a9bf 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards a6bbf118d7c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards ff3d1640044 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 05f88d72a0f 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards fba1f34feb7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards d81cef9c5a2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards b8cc6ae8395 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 2d3087341ec 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 9f915a78c3c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards ca11acfb6e9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 79467be59fc 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards bcffd521e8a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 8fccbbb9021 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 93120211d14 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 9a4dde9c134 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 557879eace5 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards a2f00b86661 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards e850c5291aa 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 1bf3f2f1633 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 88391493e47 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 241d254e3d2 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 93eaa6aaee6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 81e39e32b40 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards b25d0b42597 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards f8b8470d8fe 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 4546987c65d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards ae7eff1a29e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards a145a7e0436 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 940d3950d31 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 7f293f9c940 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 298c3edba7d 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 8e80b1be663 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards cde9fa6e6c2 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards ad8d8b5eb67 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 871992d41cf 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 42efa61bd59 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 2abc71184f2 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards a38d2f14550 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 9bbb37cc20d 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 4fa28a42aed 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards a98b20dc7b9 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards d0e02943341 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 57b6c1b4344 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards a858443d5bb 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 950ace9f8b3 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards ae9bea16205 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 7f85919fd99 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards bba25b6ac36 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 754ba4c2214 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards dfc0ad17ea0 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards f1b32e7954b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 3fb18565df6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 71b86a3a039 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 06cdf3c2453 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 65398d42d54 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 595e15bc82f 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 43ea4a71228 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new ad47126dd38 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new ca7b1f9ff6b 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 2147795ec38 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 12742a20788 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 61ca5b67fd5 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 919b05ae5da 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new afc24e91073 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 46526b3116b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 89180703d05 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 28c3622e374 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 169ec236231 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 182513b1cc3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new ff1c3753c53 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 10e66dff5b1 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 5cc92ed8198 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new f29321bcd62 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 9d89c49e640 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 04e85c75cd5 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 634bce0b4a2 48: onsuccess: #782: 1: Success after binutils: 8 commits new e353fabb9a7 49: onsuccess: #785: 1: Success after binutils: 12 commits new f64dc710e52 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 202bc0225fb 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 13a3aca08d4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 06374c0c6ab 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new de1c1ebcc2b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new f5c2f57af42 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 8cd408906b8 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 8a28edfd87f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new e67790bf8f7 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new ecd3019385d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new f80542befc0 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new c545a1aefff 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new b125aa0f46a 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new d56af85e434 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new efeb8846d53 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 8fe7888fe2e 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 9519f381a52 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 591a0ea7e44 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new d24ed20b888 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new b13d82df5a4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 7d1d2fdcc26 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new c6bbba2119d 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 77813345893 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new f3f29123c0c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new ff6008e71cf 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new db4fe159f57 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new b7ed11b59e0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 02b92768198 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 3f96c08b638 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new fd23ecc286b 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 8a65176e83f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 41c72e340b1 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 09b84958170 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 1754e1dadb8 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 5945c6caccd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 92d986141a4 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 36d87104a84 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new d9f926a1a06 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 3de0d66f817 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new f8265cb0984 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new cfcdad1ffca 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 61090bd8f47 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new b379f29e26d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 1c040f5128e 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new db6c814964f 94: onsuccess: #832: 1: Success after binutils: 5 commits new 0f0578be1d6 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7efed152dd7 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 19974f710d1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 54c5155be76 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 87812bbff02 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 3ecbdfc1247 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new cab44ad61bc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new bacf8009211 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new d86af9f0bd0 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 1c2291b42ca 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new b5d6ebeab31 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 3359d0e26c3 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 68ff76dd74e 107: onsuccess: #849: 1: Success after binutils: 5 commits new 466b8e1331d 108: onsuccess: #850: 1: Success after gcc: 2 commits new 634f5c4483e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new b8e390ef567 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 22b2f0f3aec 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new ad34133894a 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 54e9ec3fa2a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 4e0f30621e8 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 25f10302e95 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 8770a938e9a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 462bdd55640 117: onsuccess: #861: 1: Success after binutils: 18 commits new d5307d874b1 118: onsuccess: #863: 1: Success after linux: 12 commits new 03663f03b6a 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 6efcbc34eb2 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new e000dbb8e55 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new be777a4b198 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 79e68a4058f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new f713ea5033d 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new a4beb986f30 125: onsuccess: #871: 1: Success after binutils: 26 commits new 0d34824c44a 126: onsuccess: #873: 1: Success after glibc: 2 commits new abea1408b26 127: onsuccess: #874: 1: Success after linux: 219 commits new ba10a267310 128: onsuccess: #876: 1: Success after binutils: 12 commits new 05df84e8113 129: onsuccess: #878: 1: Success after linux: 3008 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 (e013fd4b33c) \ 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 1820 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 41052 -> 40276 bytes 04-build_abe-gcc/console.log.xz | Bin 216744 -> 216032 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8860 -> 9456 bytes 07-build_abe-glibc/console.log.xz | Bin 245808 -> 245304 bytes 08-build_abe-gdb/console.log.xz | Bin 40972 -> 39460 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3964 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2664 -> 2748 bytes 11-check_regression/console.log.xz | Bin 4872 -> 4848 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/g++.log.xz | Bin 3762068 -> 3769128 bytes sumfiles/g++.sum | 136 +- sumfiles/gcc.log.xz | Bin 3316376 -> 3297096 bytes sumfiles/gcc.sum | 4922 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1080012 -> 1073704 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233172 -> 232008 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457880 -> 451356 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2625 insertions(+), 2625 deletions(-)