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-arm in repository toolchain/ci/base-artifacts.

discards 0e80a300ae5b 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] discards 06180f122ad6 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards d0b24d392af7 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards c0c7cd81f973 141: onsuccess: #601: 1: Success after linux: 794 commits discards 1630ec00c4ac 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 7f50bc54a7ff 139: onsuccess: #599: 1: Success after binutils: 10 commits discards b8e7ffe47d4e 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards f6aac32ebc69 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards ee3dadbc91bf 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards 326966755683 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards 6ebdf46627ec 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards 79514261c80c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards bebd59d41cf8 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards 456e7535ef5b 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards aad3aca07ae7 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards 3e6aa301fbc5 129: onsuccess: #588: 1: Success after linux: 4 commits discards afa93a310ca4 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 52bd31ea6301 127: onsuccess: #584: 1: Success after linux: 21 commits discards 14ff3301701c 126: onsuccess: #582: 1: Success after gcc: 9 commits discards f6c451681257 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 681d4bb50dec 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] discards 7a9e865973d3 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] discards 66da2471c2c5 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards d14aa7d900e8 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards 25a915683a2f 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards bf26a8a3a0ec 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] discards ca09a0047e4d 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] discards 55c5d3191390 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] discards 42d84b75cef4 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] discards c0278b8e0cdf 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards 33ce42922c97 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] discards d13aeeb651ae 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] discards 9e877a4dd7b3 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards 42a698d6751e 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards 90ec3a8fbf62 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards 90029301a34d 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards 223494c1106c 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] discards 851b0d4abfd3 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards 1ecbb4968a5a 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards 14958ea5a0f1 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 14c457d6df61 104: onsuccess: #558: 1: Success after binutils: 3 commits discards e62e19a93187 103: onsuccess: #555: 1: Success after binutils: 4 commits discards db3311e6f25c 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards de475f991135 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 7a6eab72a6f4 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards 63aa52a9c87d 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 0b806cddde20 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 8af7b357958d 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards a84e17482695 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 6c244e6378a5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards aa87dd8f6287 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards b556b8d78fe7 93: onsuccess: #544: 1: Success after linux: 34 commits discards b32e36b855ad 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 8926d0fe3e85 91: onsuccess: #539: 1: Success after linux: 27 commits discards cdd81a79829c 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 81824bf85231 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 62f08e002ee0 88: onsuccess: #534: 1: Success after linux: 12 commits discards 1568a781b3b4 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] discards 92f18afb8a7a 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 15d5460bbe6d 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards e5f913926daa 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] discards b3ea7223a4b7 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] discards a6ee4b700c0c 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] discards 85761e26a0d7 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] discards 6ffd2029fe85 80: onsuccess: #524: 1: Success after linux: 9 commits discards 54179e24df47 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 12831863ae96 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 5c2093d4b430 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] discards 838f6a91d4cf 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 7773aef67160 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards 8d52dc8a518a 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 9ac7427e04f6 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] discards 363dbbe51a78 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] discards 9fca6bfdd8ef 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards 0723e260aee7 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards e54a418de600 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards d0ad8e8639fc 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] discards f68ffc667cb4 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] discards 3d1836698bcc 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] discards 4791f515f3d5 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] discards 09c9befef30b 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] discards 0b54cb6bfd0f 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] discards e507ceeac6f1 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] discards d687f2592585 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] discards 2d2fbde57c1c 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] discards 252b9a49f052 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] discards 6caa45fd6027 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 982aef4df58e 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards bafafd6117ec 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards 7ffafec27935 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards 6e16c56b075e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards d6049e0c8699 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards c9281f49afe1 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 4b6c42523add 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 864048cbff86 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 464b68124a09 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 15e735d1a94f 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards f7c1f4fa8d6d 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 923a393e45ae 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards 6602148bc1c8 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards 59c6ffe4ae78 44: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new a6b9477f2e7a 44: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new 45bce13d6703 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new 2c574f45b53b 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new f03a8c5dc0e2 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new 3027ddabdf79 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new 56d6fe89b1ba 49: onsuccess: #487: 1: Success after binutils: 11 commits new 908ec345c698 50: onsuccess: #490: 1: Success after binutils: 6 commits new 51092b465ea2 51: onsuccess: #493: 1: Success after binutils: 13 commits new e3098b269d9d 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new 2f6cbf78feb8 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new 7da8b492c1ba 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 32970bd7a14e 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new dc8016af548b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new 3ceae8dd3101 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new fc12f00f2d73 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new c71954a4aa04 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] new b4ecb05c7053 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] new ee1f9aecb283 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] new 04139432cab4 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] new d862e2b48a1b 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] new 25bab2f54b69 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] new ec6245cd3ba6 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] new da1c71be5977 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] new f27c36ceb4e3 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] new ed92aaad242d 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] new d1347535cd6d 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 5d3d69b73fb4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new 4fdda91308e0 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 2dc253c276f2 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] new 485a3e942b41 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] new 11cf4061734a 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 2f890a352fe6 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new d8fdd29c4609 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new cfacac862dff 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] new cc070032512c 78: onsuccess: #522: 1: Success after binutils: 10 commits new d0da93739540 79: onsuccess: #523: 1: Success after gcc: 25 commits new 0cbf14689fec 80: onsuccess: #524: 1: Success after linux: 9 commits new ffb1207de804 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] new ec2b7e59b3d5 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] new 335600022c86 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] new b64c732226db 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] new 264dd9ca0d2d 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new 96a6a8b7d5c6 86: onsuccess: #532: 1: Success after gcc: 16 commits new 42966ffc55dd 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] new dd5a3c164be6 88: onsuccess: #534: 1: Success after linux: 12 commits new 7cdb416ec12a 89: onsuccess: #536: 1: Success after binutils: 27 commits new 29aa6f739e42 90: onsuccess: #538: 1: Success after glibc: 10 commits new 6829e3fed813 91: onsuccess: #539: 1: Success after linux: 27 commits new 1b96df00648f 92: onsuccess: #543: 1: Success after glibc: 4 commits new a2dcf33f9ce7 93: onsuccess: #544: 1: Success after linux: 34 commits new b0993a7b3d09 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 36e09ae4a4f9 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 4b69579e191c 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 759b80a0c7aa 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new f67f68508970 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 1b2a44e34895 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new d434171c266e 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new e8833be54e29 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new 0dc7cdadc44d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new fe6bf2bde775 103: onsuccess: #555: 1: Success after binutils: 4 commits new 8bbf8126d875 104: onsuccess: #558: 1: Success after binutils: 3 commits new dfd95e86089b 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 00ba84b7c85c 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 56793c40fc61 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 2768e22f6ffe 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] new c9148630102e 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new 105ac265bd34 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new b1456ad4b7c9 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new cc7843816dd8 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new d3a44b79cfa7 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] new 13e86efa30b7 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] new 1e984746d694 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new 23e8c424eda1 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] new abb14c4c5955 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] new 938691b39759 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] new 1e22d40805cf 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] new b566124b2af2 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new cd7a837cac06 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new 2221e86b1cd2 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new 277148ca71b1 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] new f6f06b6ff1d3 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] new b32330bbdc58 125: onsuccess: #581: 1: Success after binutils: 4 commits new ccf253d5a580 126: onsuccess: #582: 1: Success after gcc: 9 commits new a7cb57716a12 127: onsuccess: #584: 1: Success after linux: 21 commits new 9eee28bca476 128: onsuccess: #586: 1: Success after binutils: 22 commits new 8ff8a53643a4 129: onsuccess: #588: 1: Success after linux: 4 commits new 5d9347dbdc5b 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new a13421bfdd59 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new c5c5ab7af9d8 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 8b5b231a3f0d 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new cfa1857c750e 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new f2800571da1a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 6cb6952c27ef 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new ac424870118a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new d63c535faed4 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 3086bb5f304a 139: onsuccess: #599: 1: Success after binutils: 10 commits new 07c482451822 140: onsuccess: #600: 1: Success after gcc: 23 commits new a08f4390987a 141: onsuccess: #601: 1: Success after linux: 794 commits new 2403ad5f3a5d 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new a71366877014 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 2b0513291123 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] new d0c6f2946e89 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...]

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 (0e80a300ae5b) \ 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 1800 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52732 -> 54044 bytes 04-build_abe-gcc/console.log.xz | Bin 234472 -> 235540 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 9228 bytes 07-build_abe-glibc/console.log.xz | Bin 234656 -> 236940 bytes 08-build_abe-gdb/console.log.xz | Bin 52152 -> 52128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3824 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2672 -> 2536 bytes 11-check_regression/console.log.xz | Bin 5760 -> 7140 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 11 +- 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 34 +- 11-check_regression/results.compare2 | 74 +- 11-check_regression/results.regressions | 34 +- 12-update_baseline/console.log | 64 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 34 +- sumfiles/g++.log.xz | Bin 2910864 -> 2912752 bytes sumfiles/g++.sum | 149 +- sumfiles/gcc.log.xz | Bin 2550408 -> 2592436 bytes sumfiles/gcc.sum | 5282 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 949524 -> 950768 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230460 -> 229736 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469580 -> 468764 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 3077 insertions(+), 2868 deletions(-)