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

discards f9ce3baa051f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards d0460eed1c8d 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 87a5ee122f89 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 05abb3adc7d3 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards c98dc08ffc91 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 67e194627247 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 93a03d3587c4 123: onsuccess: #655: 1: Success after binutils: 22 commits discards e1a9727906dc 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards b0b80f7eea7c 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 7d017a8a6d05 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 64909d66a9f1 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 28b9b5bd251e 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 022e803ea546 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 2b1ebe550ed3 116: onsuccess: #647: 1: Success after linux: 3 commits discards 907a4f7767d3 115: onsuccess: #645: 1: Success after binutils: 27 commits discards b1d49c1afdb2 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards 104abdf86d73 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 3dfa0f6d9053 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards ab325b0866d1 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards 2afeac9e86da 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards b6c7d6da3045 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards 9bc96422867c 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards 71bbbc04a4e1 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards 3687cd214871 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 473ea4b304b0 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 4fce703f385c 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards c60b4cdecb02 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] discards b7e54e774301 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] discards d1b074fb3d0d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 59a7d957bf64 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards e7a4ea4cca3b 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards eef8b9e72406 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 712c4010b783 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 41c501670b06 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards fd74f1e3b8d1 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 911762e5030f 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 96bac62075b3 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 77659fb94424 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 0e3fbaf3097e 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards fb84d5a0fbb1 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c9d4e8f2e85f 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards aad1051b5377 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 7c95ffaadd38 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards b61a6de3ddd8 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 8ea33feed6b1 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards c5a1d17128ca 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 83bf4b6562ec 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 8725a80b845e 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards d1a20cf74af8 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards f7e6f0cc4209 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards e5e1dd672127 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 272452375ab4 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 770861bdfe1b 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards e4d7a31b39fc 76: onsuccess: #592: 1: Success after linux: 63 commits discards 9d7982dbdee2 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 5d0e081f1c51 74: onsuccess: #590: 1: Success after binutils: 16 commits discards ffbcac1c1770 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 09b5fc839b78 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 7294a5ece2f7 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 9e434b5493da 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 4749c4d80182 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 2694e66b7aaa 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards ee2517dd32e9 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards 65048ad59c2d 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards 1e820ba667bd 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards 360501971794 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 52841b001612 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards ea290649d27a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards ae3ec9f89488 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 145dfd1abfc6 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 38f76eacd0e1 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 3989eda37e93 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 568823a53e39 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 584b19159b90 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards a5e8dae70e4d 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 13c6aa366a76 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards bd79c794b99f 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 2a089516543d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 62b6c2643d00 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards f85e7364501b 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards df2d2bd0d1c8 49: onsuccess: #562: 1: Success after binutils: 9 commits discards c6f71c4ccb98 48: onsuccess: #559: 1: Success after binutils: 6 commits discards fffd93467b43 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 6ede67f0e9e8 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards cce4ab75f1e9 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards c5f4ae5dc9a0 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards b8d20d1aa06c 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards bc2f1758b496 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 9f2e85f3d10b 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] discards b412b2741bdf 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 848ba603546e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] discards 08809b5448e6 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 6b5e94d97462 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] discards d1c508493619 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 2ecb524c2705 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 11c9daf7c2e3 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards f64b1665179f 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards 1698972210aa 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 56ccc9be66b2 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 1ba96c305b57 30: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] discards 0a116ff0deed 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new fa0830f951c7 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 2c6735c55f76 30: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new ecf5ec7c0c98 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 01b6e8dd7ac6 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new aaaef3041302 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new 960b14a4b616 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 5f6955e7d2c3 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new ac848c950dde 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new cd414867c410 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] new 7193d58d05be 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 9ef5c5860d7e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] new 521aea1d7ff6 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 736c33dec853 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] new a4e2ce686c86 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 09c79b5d8277 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 6cf52f2decab 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new cdb1f0b82ea8 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new e6bf66277ade 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 0d27c7370ce9 47: onsuccess: #556: 1: Success after binutils: 12 commits new 2fe266b117c4 48: onsuccess: #559: 1: Success after binutils: 6 commits new ba167f8ffbbe 49: onsuccess: #562: 1: Success after binutils: 9 commits new 6eeefa7d37e8 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new f7094224e705 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 590978d82d2e 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 639fb56cf48c 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new fa831e897668 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 33f8ee29fa15 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 5fd970252bfc 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new ce65968c9641 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 2dd7999b6caf 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 2ef50d79c47c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 9a57fcb74bf6 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new dd50c64d9040 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 3bc1ae45f2b7 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new aec94c16321c 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 772316f8c63e 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 89849ef6f361 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new 52b7c15685d5 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new e8f6aea0075d 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new 56c52bf010f7 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new f9a1b85c0fdd 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 3830f989b289 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 835b7acb8c1e 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new f78934378a1c 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 1ed5f3e3d3a0 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 94f20b15b2d4 74: onsuccess: #590: 1: Success after binutils: 16 commits new 73226cfdab82 75: onsuccess: #591: 1: Success after gcc: 25 commits new 4d2224e53cfa 76: onsuccess: #592: 1: Success after linux: 63 commits new c22fe5b9fecc 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 1fa3b9ed858c 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 0025db812c0b 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 129e63ec1d54 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 8df301282b19 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 8dbc5cc211e0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new a962f2f7458b 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new c845fb30d04b 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 5b98301034a0 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 0d3b7ee52952 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 63a93a8ad820 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 3002065e3b3c 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 2bf65482f42d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 328d1ac4c3f5 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f823fc1fc0a7 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 4aa903315259 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 5ce57a07e031 93: onsuccess: #613: 1: Success after binutils: 19 commits new fbcf1503eef8 94: onsuccess: #616: 1: Success after binutils: 2 commits new 76ccf3eb5ac3 95: onsuccess: #619: 1: Success after binutils: 5 commits new 44fe8f970c7b 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 4854ef46770d 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 49bad25295c7 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 007c5ac2a80f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 38bd5b1c758d 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 9d4dbf8b4d78 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new 940a4ad17f7b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] new db53f46d0d8c 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] new 928d9db32d6d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new 189d05e3a3aa 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new 5083540ee17b 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new f0ce772b8654 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new 273423be3f92 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new a450a9ff9db7 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new a87943966fa5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new b205385177a7 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new 6c765f2c7640 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 1358e25d44ad 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new 77f6e0d0f6c3 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 6642d5dd89b0 115: onsuccess: #645: 1: Success after binutils: 27 commits new 262b74bfcc57 116: onsuccess: #647: 1: Success after linux: 3 commits new 2b09cd90f023 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new a838c3a3dae0 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 853c1d19c149 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new afad14f8e94f 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new 0e22a16b0759 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 1199de66fec6 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new fa152f9f5b3f 123: onsuccess: #655: 1: Success after binutils: 22 commits new 3e41b84a6f93 124: onsuccess: #657: 1: Success after glibc: 2 commits new 004d15d9f404 125: onsuccess: #658: 1: Success after linux: 3224 commits new b975ecc36e26 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new beedafcec486 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 59a0c8e869d0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 2f325ccd1596 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new dafa76de5fdd 130: onsuccess: #663: 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 (f9ce3baa051f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]

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 1792 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40696 -> 40040 bytes 04-build_abe-gcc/console.log.xz | Bin 216176 -> 213568 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8680 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 243760 -> 243232 bytes 08-build_abe-gdb/console.log.xz | Bin 40164 -> 39048 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3884 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2620 -> 2136 bytes 11-check_regression/console.log.xz | Bin 6068 -> 5612 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 29 +-- 12-update_baseline/console.log | 36 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 63452 -> 63044 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83856 -> 83828 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121916 -> 121716 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 391 insertions(+), 408 deletions(-)