Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (fd93ac119d -> 1245520270)

by git＠git.linaro.org

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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards fd93ac119d 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards c5521171e6 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 4b7e4cdf1e 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards a571932d6a 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 2ea7e8ecf8 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards eaa715bd66 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards d54ab36920 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards f79e4debac 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 588c71e391 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 368322c120 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards efe11b3422 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 9e6a971f18 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 5aaf1f4b0b 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 575bc195ea 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 48190697c6 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 4910d938d9 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 45693d1992 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 660674b871 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards b87b6ef87b 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards acd7d0a297 127: force: #27: : Failure after baseline build: no new commits discards 3b58adac4a 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 752fdc89aa 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards dd3915249e 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards a44c15ec02 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 1a9e5937f7 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 6147955549 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f90d1315ae 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 6377324453 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 711559ca7f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards ce0e48c15a 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 852cd1d390 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards d17be42640 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 240157d3d0 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 86438d9ab0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 88d4cddf1a 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards deb64551ea 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards abd10a4897 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 2c2469a75d 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards da79e0289f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 4efe044a9a 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 6eae76e4fd 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards ade5d563dd 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards c9c8652f20 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards f71169d0fa 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards b25a6a40cd 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 3eb08ae939 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards d43123a17d 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 3ac0c1da17 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards b54d80d0c4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 91ca193c4d 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 85631e8583 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 32d39a1a46 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 6c8d4f5a81 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 8e312c0aa5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 4584f26d93 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 90c2002768 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 4d1ffe4792 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 9ad85f958c 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 57811ef6d6 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 8acb79c455 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 4ad014dab5 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 26c437f54f 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 5fd4693057 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 667793cc44 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 31486a75e3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 69e5d63999 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 810f6e4520 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 928575713c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards bdddc5ff4d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards bdd8590177 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 245d691259 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 0991943234 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 23cc9e1011 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 5611e866f2 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c108542dfa 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 200e580e2d 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards e61719fae9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 5f62c676f4 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 33e4323442 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards fe7979accf 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ec04d2c941 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 1fad4c5ca1 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 30e1009cbb 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 4ceae63b29 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards ed704c6f86 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 6239e0cfc4 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards f57b443eaf 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards e7239cfdae 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 1845273ce9 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards d3513430b1 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 362fd5561c 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards b3f0ee5616 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 7fa7271a3c 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 57d598ebc9 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 0fc8b5607d 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards e5479eae51 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 7d911abefb 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards 83df806a9a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards dc55969291 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards c613ad6ffc 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 4d65385ba7 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new aa7a9e1983 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new b58dfa6f6d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new efc52cebce 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new afb8952a7c 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 089fb2080c 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new 055c874da5 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 74cbd3e542 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new fcebfd7f60 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 998f2e676d 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new eb3a8a6007 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 7a0966c5ad 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 54539a588e 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 578ae7dc87 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 4913567191 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 64358b3321 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 4de88b9405 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 8fb426b66d 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new dcdeee1157 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new f73899f782 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 32d8cd1373 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 75a26096ee 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 43e19e7736 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 093eb58153 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 950b7c676c 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new d1c200ad80 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 6f25e6cb88 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new c449a3d21e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new c9180bcf7d 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new b2986057a8 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new b918bd0965 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new c136aeb180 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new d4f8db3922 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 343915106a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 9cd3f9e8cc 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 3bdc3788be 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new d07755eff2 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new c8cb82ca42 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new eb55c8c77d 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new f0a7997861 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 6a831dacf1 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 844de0884c 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 7e2ae585b4 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new f18ede61fe 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 7b0a84abf4 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 577e7e63b5 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a31c1a357a 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 54870bbdcd 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 7a9f8a5323 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 73cee8d33c 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new dc9bfbeb5e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 7d4707254f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 3461166fbb 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 97cbd48961 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 33d012efe6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 74214a0c54 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 3ecb29b49f 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 3df332c325 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 70928215fc 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 3996a2afea 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new d34e48e649 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 780832a5aa 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 2915881155 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new caae57f7d2 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 772bcf7270 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 7b7c4ba465 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 653dea9417 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new d42a0f4397 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new c8a4d4dd04 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new fe10f3e9ff 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 9822692796 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 13b92b3888 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4b507043bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 8bbbb6385c 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new def059a9b8 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new aa088dca85 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 924ced55ef 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new cd8c1ee39d 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 95f2c477a9 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 51973fa128 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 95653fb8fc 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2e860750e0 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new ef02e5bf45 127: force: #27: : Failure after baseline build: no new commits new b5a0964311 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 9a5165c516 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new c3d47369e5 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new abdf1c725e 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new efd0d89eb6 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 1b84f9165d 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 18f3ef58b1 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new bd66919db1 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new fc9c195549 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 280a3073c7 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 61f4c7ebd7 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 6ad8870916 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 3c29c80ef5 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new ce0630fe05 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 83943cd771 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new f2c92f2cdc 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new bedeff33ff 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 87857b970b 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new fcb30fef79 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 1245520270 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] 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 (fd93ac119d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 2056 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 35064 -> 35084 bytes 04-build_abe-gcc/console.log.xz | Bin 203288 -> 203964 bytes 06-build_abe-linux/console.log.xz | Bin 9068 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 241080 -> 241756 bytes 08-build_abe-gdb/console.log.xz | Bin 34744 -> 34836 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2824 -> 2800 bytes 11-check_regression/console.log.xz | Bin 4932 -> 4168 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 38 ++++++++++---------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++++++++--------------- manifest.sh | 32 +++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14436 -> 14440 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 75 insertions(+), 91 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (15d7a0915c -> 0fed20147b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. discards 15d7a0915c 235: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] discards 259282aac7 234: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] discards e891949d30 233: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards 7afc77611f 232: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards 2287d80105 231: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] discards c7f7f2d9a3 230: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] discards 96579f4461 229: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] discards e7d6e27c02 228: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] discards e738c52294 227: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] discards 78b6730253 226: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] discards 50d4c8fd0b 225: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] discards 6107872966 224: onsuccess: #35: 2: Success after binutils/gcc: 7 commits discards 00585f4084 223: onsuccess: #34: 2: Success after binutils/gcc: 7 commits discards cdb53e8b8e 222: onsuccess: #33: 2: Success after binutils/gcc: 32 commits discards 6ee398361a 221: onsuccess: #32: 2: Success after binutils/gcc: 32 commits discards 6a0349061b 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits discards 70f3f0da6f 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits discards 383ab494b1 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits discards e2db0477f9 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits discards 0a8518ecfe 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits discards b1225ba964 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits discards a17e85502a 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits discards 11fa55f9c9 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits discards e2aef55835 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits discards d90fd09ff7 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits discards f693f1dbaf 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits discards e80a06951b 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits discards 52718f46cc 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits discards 8aa315a7d0 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits discards abe76b7d78 206: onsuccess: #16: 0: Success after binutils: 17 commits discards 01e8146d32 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] discards c57ea90097 204: force: #14: 2: Success after binutils: 17 commits discards 7f09d8469e 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits discards 0d9c239108 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits discards 56f4727971 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits discards 7c943e788e 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits discards 7b9f1538b7 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits discards a26e39b23e 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits discards 8b41d39ec7 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits discards 33f0cc8bfd 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits discards 82e5b34639 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits discards 058988e458 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits discards 2920640266 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits discards 65f1bf35a0 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits discards 12c1d43528 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits discards 0aebfbbaf9 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits discards 86e97c0078 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits discards 0139c68570 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits discards 814246393f 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits discards 3e776b2e10 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits discards 6a90566ef8 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits discards 923fbfb504 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits discards 3e73d06e88 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits discards 1a59350565 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits discards 8607ceb334 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits discards 96b80ad7b3 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits discards 007c3737e3 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits discards 0c9ecdcd1e 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits discards 64cdbd147c 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits discards e09858c3b6 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits discards 4cb97bc42b 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits discards cd6a32fafd 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits discards b7274a0cfc 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits discards 36203eb919 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits discards 07b268cf18 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits discards 83aa888e49 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits discards f1f41bc075 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits discards 831fb1f438 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits discards fd4ab83760 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits discards 1bc9e02be4 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits discards bf447d4347 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits discards e287e0c7c7 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits discards 855bc9d040 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits discards 55f9014902 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits discards d1ed6cadaa 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits discards 223b965d77 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits discards 914d959dc0 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits discards b38fe647ac 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits discards 5e267ee885 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits discards 215ff1f8fa 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits discards 491e12ea27 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 7fb5cd1285 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits discards a67da8636c 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits discards a2ab7f21d3 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits discards 676c84598c 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits discards 6eebcf082c 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits discards ba9058c8af 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits discards e6991f02b3 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits discards 776e89872a 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits discards 697fbda178 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits discards 612e978d44 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits discards 321dd0b656 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits discards 6fa13e766e 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits discards c982272d7f 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits discards 8f08264265 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards e8d203999e 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits discards f08b484402 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits discards 0bbad641f8 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits discards 76b0057b68 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits discards 746d6ef0c7 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits discards c4680a19db 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits new 1f37521eed 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits new 0579774307 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits new 3407ca0e7e 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits new 93d3e7e07e 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits new 9524c055c1 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits new 3dafa910b4 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits new f765bf3d09 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 6c5f2a932b 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits new b49a7ac3f8 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits new e86cefe31d 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits new 7608c20564 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits new a53c5831b9 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits new 6023efb0aa 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits new 955cee4b12 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits new e53624b2ea 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits new 4aa8d42047 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits new deaf634f33 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits new 3a23a3f5a9 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits new ef972d4a86 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits new ac44badc0b 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits new a634ca9321 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 94a1b2e20c 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits new c66d153dbd 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits new 2dd0b4721b 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits new 3e6d525262 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits new 4b9d941e70 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits new 66c73dc07a 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits new 0c738b9778 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits new c87e0b679f 163: onsuccess: #596: 2: Success after binutils/gcc: 65 commits new bd3a7f5e97 164: onsuccess: #597: 2: Success after binutils/gcc: 40 commits new 7e2cf83f0b 165: onsuccess: #598: 2: Success after binutils/gcc: 43 commits new d84af8a7fd 166: onsuccess: #599: 2: Success after binutils/gcc: 44 commits new 471f2fd790 167: onsuccess: #600: 2: Success after binutils/gcc: 15 commits new bda7cb0a97 168: onsuccess: #601: 2: Success after binutils/gcc: 47 commits new b3170f6e47 169: onsuccess: #602: 2: Success after binutils/gcc: 30 commits new 32656d9e0a 170: onsuccess: #603: 2: Success after binutils/gcc: 63 commits new b9da2874bf 171: onsuccess: #604: 2: Success after binutils/gcc: 104 commits new d09f121bd2 172: onsuccess: #605: 2: Success after binutils/gcc: 57 commits new a74d2de15f 173: onsuccess: #606: 2: Success after binutils/gcc: 17 commits new c4f6100f25 174: onsuccess: #607: 2: Success after binutils/gcc: 50 commits new 5fd52a3245 175: onsuccess: #608: 2: Success after binutils/gcc: 106 commits new 380ad92e46 176: onsuccess: #609: 2: Success after binutils/gcc: 42 commits new 6f79f8b205 177: onsuccess: #610: 2: Success after binutils/gcc: 58 commits new 922656c93a 178: onsuccess: #611: 2: Success after binutils/gcc: 29 commits new 9b38e2a5e5 179: onsuccess: #612: 2: Success after binutils/gcc: 14 commits new 2ba9ba57e3 180: onsuccess: #613: 2: Success after binutils/gcc: 24 commits new 55f6d067dd 181: onsuccess: #614: 2: Success after binutils/gcc: 16 commits new 06f0e3dc85 182: onsuccess: #615: 2: Success after binutils/gcc: 37 commits new 8738e775f2 183: onsuccess: #617: 2: Success after binutils/gcc: 85 commits new af591431e9 184: onsuccess: #618: 2: Success after binutils/gcc: 64 commits new c8ea6a0e04 185: onsuccess: #619: 2: Success after binutils/gcc: 109 commits new e5b9527193 186: onsuccess: #620: 2: Success after binutils/gcc: 93 commits new c86ea65757 187: onsuccess: #621: 2: Success after binutils/gcc: 25 commits new 83427aae0e 188: onsuccess: #622: 2: Success after binutils/gcc: 114 commits new 8b4affe76e 189: onsuccess: #628: 2: Success after binutils/gcc: 281 commits new 7f0f5e88f7 190: onsuccess: #629: 2: Success after binutils/gcc: 34 commits new 5996e0c456 191: onsuccess: #630: 2: Success after binutils/gcc: 41 commits new 5e16938d57 192: onsuccess: #1: 2: Success after binutils/gcc: 29 commits new e53af04077 193: onsuccess: #2: 2: Success after binutils/gcc: 19 commits new 4bf1292f15 194: onsuccess: #3: 2: Success after binutils/gcc: 8 commits new 987c0387b0 195: onsuccess: #4: 2: Success after binutils/gcc: 7 commits new ec2ccbe841 196: onsuccess: #5: 2: Success after binutils/gcc: 40 commits new 2e1f5922a7 197: onsuccess: #6: 2: Success after binutils/gcc: 47 commits new 40bd8db35e 198: onsuccess: #7: 2: Success after binutils/gcc: 24 commits new 7c4a573a64 199: onsuccess: #8: 2: Success after binutils/gcc: 40 commits new e325580f45 200: onsuccess: #9: 2: Success after binutils/gcc: 53 commits new 407dc0924c 201: onsuccess: #10: 2: Success after binutils/gcc: 17 commits new 2db86727a6 202: onsuccess: #11: 2: Success after binutils/gcc: 18 commits new 141b7927b9 203: onsuccess: #12: 2: Success after binutils/gcc: 27 commits new f6da67ac0f 204: force: #14: 2: Success after binutils: 17 commits new 30a5d5c8f3 205: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] new 60171be501 206: onsuccess: #16: 0: Success after binutils: 17 commits new 6b96b8591e 207: onsuccess: #17: 2: Success after binutils/gcc: 55 commits new 3d2fe7fde3 208: onsuccess: #18: 2: Success after binutils/gcc: 33 commits new 74d8881eb8 209: onsuccess: #19: 2: Success after binutils/gcc: 57 commits new d8e121e7f6 210: onsuccess: #20: 2: Success after binutils/gcc: 15 commits new 3d053fb4ec 211: onsuccess: #21: 2: Success after binutils/gcc: 15 commits new 00b0d26d4a 212: onsuccess: #22: 2: Success after binutils/gcc: 42 commits new 472dba812f 213: onsuccess: #23: 2: Success after binutils/gcc: 56 commits new f4c2f8fdb6 214: onsuccess: #24: 2: Success after binutils/gcc: 37 commits new 828870a248 215: onsuccess: #25: 2: Success after binutils/gcc: 36 commits new 3cc19d764f 216: onsuccess: #26: 2: Success after binutils/gcc: 45 commits new b1ad20de6a 217: onsuccess: #27: 2: Success after binutils/gcc: 33 commits new 2530574b2e 218: onsuccess: #29: 2: Success after binutils/gcc: 43 commits new 1d245bf1b7 219: onsuccess: #30: 2: Success after binutils/gcc: 40 commits new a74c108856 220: onsuccess: #31: 2: Success after binutils/gcc: 38 commits new f416174661 221: onsuccess: #32: 2: Success after binutils/gcc: 32 commits new 3767dd6a33 222: onsuccess: #33: 2: Success after binutils/gcc: 32 commits new 9d6b6cef40 223: onsuccess: #34: 2: Success after binutils/gcc: 7 commits new 689360be66 224: onsuccess: #35: 2: Success after binutils/gcc: 7 commits new 4b50f33c0b 225: onsuccess: #37: 2: [TCWG CI] Success after binutils/gcc [...] new 04bdba2733 226: onsuccess: #38: 2: [TCWG CI] Success after binutils/gcc [...] new 62385b1b07 227: onsuccess: #39: 2: [TCWG CI] Success after binutils/gcc [...] new 86685a8a41 228: onsuccess: #40: 2: [TCWG CI] Success after binutils/gcc [...] new daebc75937 229: onsuccess: #41: 2: [TCWG CI] Success after binutils/gcc [...] new 8d24db3a2e 230: onsuccess: #42: 2: [TCWG CI] Success after binutils/gcc [...] new 14afa715a3 231: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] new b257313cca 232: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new a825249825 233: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new e1dbf2709b 234: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] new 7a0dc21d7b 235: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] new 0fed20147b 236: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] 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 (15d7a0915c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1896 -> 1912 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2532 bytes 04-build_abe-binutils/console.log.xz | Bin 49100 -> 48888 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 468728 -> 468004 bytes 06-check_regression/console.log.xz | Bin 2944 -> 2492 bytes 07-update_baseline/console.log | 44 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 14 +++------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 18 ++++++------- manifest.sh | 18 ++++++------- 13 files changed, 47 insertions(+), 55 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig updated (1ff449fd8a -> e220bade2e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 1ff449fd8a 51: onsuccess: #9: all: [TCWG CI] Success after binutils/llv [...] new e220bade2e 52: onsuccess: #14: all: [TCWG CI] Success after binutils/ll [...] The 1 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 1980 -> 2004 bytes 02-prepare_abe/console.log.xz | Bin 2556 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 27588 -> 27024 bytes 04-build_kernel_llvm/console.log.xz | Bin 66608 -> 65272 bytes 05-build_abe-qemu/console.log.xz | Bin 32376 -> 31264 bytes 06-build_linux/console.log.xz | Bin 3404 -> 3388 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4360 -> 4316 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 48 +++++++++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++------------ manifest.sh | 32 +++++++++++------------ 17 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-defconfig updated (07791c6e4b -> 4cb24cafbc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-defconfig in repository toolchain/ci/base-artifacts. from 07791c6e4b 58: onsuccess: #10: boot: [TCWG CI] Success after binutils/l [...] new 4cb24cafbc 59: onsuccess: #11: boot: [TCWG CI] Success after binutils/l [...] The 1 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 2016 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27180 -> 26860 bytes 04-build_kernel_llvm/console.log.xz | Bin 65880 -> 65088 bytes 05-build_abe-qemu/console.log.xz | Bin 30888 -> 30972 bytes 06-build_linux/console.log.xz | Bin 2976 -> 2956 bytes 07-boot_linux/console.log.xz | Bin 5656 -> 5632 bytes 08-check_regression/console.log.xz | Bin 3836 -> 3448 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 32 +++++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 ++++++++++++++-------------- manifest.sh | 24 ++++++++++++------------ 15 files changed, 43 insertions(+), 49 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-defconfig updated (e29fd652d9 -> 9cec1fdd30)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from e29fd652d9 58: onsuccess: #10: boot: [TCWG CI] Success after binutils/g [...] new 9cec1fdd30 59: onsuccess: #11: boot: [TCWG CI] Success after binutils/g [...] The 1 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 2008 -> 2000 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 27656 -> 27224 bytes 04-build_abe-stage1/console.log.xz | Bin 71424 -> 71356 bytes 05-build_abe-qemu/console.log.xz | Bin 31204 -> 31268 bytes 06-build_linux/console.log.xz | Bin 5068 -> 5056 bytes 07-boot_linux/console.log.xz | Bin 6112 -> 6096 bytes 08-check_regression/console.log.xz | Bin 3756 -> 3332 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 32 +++++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 ++++++++++++++-------------- manifest.sh | 24 ++++++++++++------------ 16 files changed, 52 insertions(+), 49 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig updated (2f8cbc0ca1 -> c9569344cf)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 2f8cbc0ca1 61: onsuccess: #14: 21953: [TCWG CI] Success after binutils/ [...] new c9569344cf 62: onsuccess: #15: 21973: [TCWG CI] Success after binutils/ [...] The 1 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 2024 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27404 -> 27032 bytes 04-build_abe-stage1/console.log.xz | Bin 71484 -> 71132 bytes 05-build_abe-qemu/console.log.xz | Bin 31048 -> 30920 bytes 06-build_linux/console.log.xz | Bin 8088 -> 7660 bytes 08-check_regression/console.log.xz | Bin 4272 -> 3812 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- results | 2 +- 16 files changed, 55 insertions(+), 61 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig updated (6d3b697ba7 -> 9a0d746b40)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 6d3b697ba7 55: onsuccess: #10: all: [TCWG CI] Success after binutils/ll [...] new 9a0d746b40 56: onsuccess: #11: all: [TCWG CI] Success after binutils/ll [...] The 1 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 2020 -> 2004 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 26864 -> 26912 bytes 04-build_kernel_llvm/console.log.xz | Bin 65272 -> 64824 bytes 05-build_abe-qemu/console.log.xz | Bin 29980 -> 29764 bytes 06-build_linux/console.log.xz | Bin 2952 -> 2884 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4208 -> 3792 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- 16 files changed, 54 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (7393f928ad -> 750963d33e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 7393f928ad 59: onsuccess: #10: 21797: [TCWG CI] Success after binutils/ [...] new 750963d33e 60: onsuccess: #11: 21797: [TCWG CI] Success after binutils/ [...] The 1 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 2020 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 27196 -> 27380 bytes 04-build_abe-stage1/console.log.xz | Bin 71092 -> 71028 bytes 05-build_abe-qemu/console.log.xz | Bin 30264 -> 31568 bytes 06-build_linux/console.log.xz | Bin 9556 -> 9520 bytes 08-check_regression/console.log.xz | Bin 3832 -> 3404 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 32 +++++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 ++++++++++++++-------------- manifest.sh | 24 ++++++++++++------------ 14 files changed, 43 insertions(+), 49 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (3898eee693 -> 50019bdb29)

by git＠git.linaro.org

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 3898eee693 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards e3aa4d038e 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 8bc8ce8a59 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 1e7a1d48f6 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 4a3c6d9234 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 6b051e167c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 29e056215b 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 3e8df3a4c3 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 7451f2362a 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 81eccc3785 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards ad2aaf43bd 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 8621d77109 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards a9d97e8f43 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards ea23a510db 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 3e76183513 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 226bbbd085 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 6601e06ae2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 7e0d32c124 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 36b4ca9cbb 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards afddf5f741 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards a4e5d635df 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards c09de1065e 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards e0aabc5cfe 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards c9cb803c3f 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 048b45b0f7 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards f97d0bcba4 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 97661feb68 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 645ac075c9 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards bf2ef85f5a 212: force: #45: 1: Success after gdb: 22 commits discards eed8b00321 211: onsuccess: #44: 1: Success after linux: 26 commits discards 07f654e1b8 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 1488888bd6 209: force: #37: 1: Success after baseline build: no new commits discards fe1380ba80 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 0d32d6756c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 79f313bf45 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards b5e1089b36 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 7b437074ca 204: force: #26: : Failure after baseline build: no new commits discards 64956d05b3 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 6b5e93735b 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 27d5db3125 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 712e23bad0 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 1f61bdc6e4 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c424f4881e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 5402db83ae 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5f6c8eae7e 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards fe5bb1f0da 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards da6c3bdc1a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 0840c50c09 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 894b57e85d 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7db05181e3 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 2d575f3559 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards bcc5423f9a 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 80006c0c21 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 7b9bfb066b 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards d570695df3 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 63d45b479d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards e019adc91d 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards f3df020db6 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards e6eba68f47 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 58b06bc048 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 18644e67f5 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards fe34145386 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards ddfc19dd1e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards c22c42a6c5 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 6e95b0ef4a 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards f1b8488af0 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 3029fa6c61 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 1c8f946704 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 0f4ee555b9 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards bea6f7f034 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 2b4db8214e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 8246e57ae0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards abc374549f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 8dfd0b3cab 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards b19588ef9b 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 48be4138a2 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards b112ba0b3c 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards f4c7e71d70 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards cee38be3dd 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards bb43ac82f1 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards afdc171697 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 23cb026610 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards ad2d01651f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards cbad330778 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 0e2e16bebc 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards fe3a60fd53 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards a24309b28d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards fd6b046aeb 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 48ce170cf0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 1b0c8baf61 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 3b8e2d13a5 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards cb13b2fa3d 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 3813e186fb 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 144e98212a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 9f60fdc111 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards f742f99bae 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 2e039f6ea0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 8528abc0b2 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards fe27b941a2 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 6a1a02a797 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards f5ed340a96 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 447186866f 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 4dac7c83b5 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new d350db195a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new a1ffc5ad44 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 0f0dca9b2d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 5791559dfa 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new e142bde3ae 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 27eefcd125 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 4d2b274b3e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new edcf6822b4 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 75a38af914 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 3a90b97e0c 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 4feed10e28 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new b8237f1345 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new b0d378a61b 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new faa3211ca4 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 843046d22d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new eeeb05bc60 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new a33becb746 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 73e4c0da52 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new d5c48f3e34 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new bbe3493b56 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new cf94419145 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 42ddcc8452 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 28566e64ab 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 03102ddca3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 12251e6ee8 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 480e69f608 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 83bd4a036d 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 7c53b94b76 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new f6d3166b68 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 2331d4f262 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new a04ab63597 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 7127d09e1c 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 50e74b306e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 4163d6b13e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 19407e69d4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 5b7fa20b6b 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 9768c338cb 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 586e7d51dc 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new fb96ff87a9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new b4d50aca83 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 8c77bea947 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new f0585eb225 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new ca335f29cb 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 6f384938ec 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 56930e59b2 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new ae624785d5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 6ee797fe4c 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 6143c8a9d8 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 59f7e62287 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 220ca48365 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 75914bf466 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b5f2c7a42a 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new c9be668f16 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 508f6f9534 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new f6c1608659 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new ab061da5fc 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 2e67f9f0e3 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 3bb131701f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new c271f6501c 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new cfe3710b9d 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 487948fbed 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f5dc578f32 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new f22f507cb9 204: force: #26: : Failure after baseline build: no new commits new 8c08609290 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new bfaeddc1c1 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new b444924074 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new ee0683754c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 7018cb0ead 209: force: #37: 1: Success after baseline build: no new commits new caeb00033f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new d439e08c47 211: onsuccess: #44: 1: Success after linux: 26 commits new f3f6e4647a 212: force: #45: 1: Success after gdb: 22 commits new 384ef89332 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 27579603e0 214: onsuccess: #47: 1: Success after gdb: 21 commits new cf9acbb44c 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 66700d037c 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new c8dddb8809 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new cc434bf8b7 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 4a48e6ac6a 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 84eb0f91bd 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 94e0a61b51 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 89e8c43e7a 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 95bf542f95 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 67b90a02a3 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new f781f3c4bf 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 92c6a9a2b1 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 1fbabc78f8 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 9e7720466e 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 0219916bda 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new bbf4c3e305 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new cdfc078b62 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new a2757c3b1d 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 180e03e6ad 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new b190a8db38 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new c3a4ecf6fb 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 3611c9cc86 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 8afa88d014 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 03a4164f86 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 161da876b5 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 1a73660738 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 50019bdb29 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 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 (3898eee693) \ 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 2080 -> 2208 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 34952 -> 35036 bytes 04-build_abe-gcc/console.log.xz | Bin 203604 -> 204088 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 240648 -> 241032 bytes 08-build_abe-gdb/console.log.xz | Bin 34688 -> 34752 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2640 -> 2620 bytes 11-check_regression/console.log.xz | Bin 5132 -> 4152 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 111 ++++++++++++++++------------------ 12-update_baseline/console.log | 42 ++++++------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 27 +++------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++----- manifest.sh | 26 ++++---- sumfiles/gdb.log.0.xz | Bin 1988900 -> 1999124 bytes sumfiles/gdb.log.1.xz | Bin 28456 -> 15124 bytes sumfiles/gdb.sum | 26 ++++---- sumfiles/gdb.sum.0 | 29 +++++---- sumfiles/gdb.sum.1 | 103 ++----------------------------- 25 files changed, 145 insertions(+), 261 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-arm updated (274310bfbc -> 819c0d73b5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-arm in repository toolchain/ci/base-artifacts. from 274310bfbc 13: onsuccess: #16: 1: [TCWG CI] Success after binutils/gcc/ [...] new 819c0d73b5 14: onsuccess: #17: 1: [TCWG CI] Success after binutils/gcc/ [...] The 1 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 2088 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 26876 -> 26896 bytes 04-build_abe-stage1/console.log.xz | Bin 88688 -> 88972 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 8276 bytes 07-build_abe-glibc/console.log.xz | Bin 232476 -> 233044 bytes 08-build_abe-stage2/console.log.xz | Bin 225332 -> 224968 bytes 09-build_abe-gdb/console.log.xz | Bin 34320 -> 34384 bytes 10-build_abe-qemu/console.log.xz | Bin 29852 -> 30748 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3872 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2188 -> 2152 bytes 13-check_regression/console.log.xz | Bin 4864 -> 4776 bytes 13-check_regression/results.compare | 4 +-- 13-check_regression/results.compare2 | 4 +-- 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/changes-list-long.txt | 38 +++++++++++--------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +++++++++++++------------- manifest.sh | 42 ++++++++++++++--------------- sumfiles/binutils.log.xz | Bin 62084 -> 62084 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 101040 -> 101012 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 114160 -> 114132 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 71 insertions(+), 79 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023