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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 0cbef42b73 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 63575cd147 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 3337da84bf 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards fdc89ce190 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 8b61ac3666 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards dbbc8fdf66 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards e145fd6c44 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards d465154297 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 376aee789f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards cbebd27861 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 7122e13db4 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 7a11c3af36 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 2c904e58da 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 7725315500 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 67a1377939 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards bee5ccf97f 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 3ffdf74d37 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 368fbaf77c 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards eda935ea1a 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards ebd25c7ad8 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards a53f17ff7b 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 4960191b7b 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 2b8b0be5c2 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 3d8e127a06 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 39144ff7d2 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards a0c299b8bf 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards a2e12a9556 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 42c5038c00 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards a9001a102c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 8a612db198 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards fae89091b8 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards aa01b9e285 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards d068bbc7cb 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 0ee6b98e96 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 0d0ce470d2 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 7e2e3a900a 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards a375e26cbb 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 23f7ad4058 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 8f7a1ece91 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 51f266fdec 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards eb2cb96dae 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards aa65db0897 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards cbf7908fe6 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 52bb06dcdb 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 94fbf88c81 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 4530b0c5d0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 47cefdfefa 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b1b8269c9a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a8dd98b17e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5b63cb81c1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards ce79d78553 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards e8681e56e3 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 49ef4e90c9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards f003418ed9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 503389a262 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 8c717686f5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 675c646658 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards a22d6e3672 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards b902f9a0a5 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 66c2dc2f62 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 7a69368ea5 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 63d93b3e4a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards db8b02351b 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards b117e0c13b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 5877f39d0e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 8cd0d7f6b3 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 612c658d70 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 628b558e56 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 66fba19183 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards fd1d20b361 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 0b1a912582 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards c0494e8318 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards f5ddc5c61f 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 96ab48bed9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards c258111ca5 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 71b504f554 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards c738b18588 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 236d53777d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 3ef02f13e9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 441d7e84be 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 4013db3e64 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 6581053911 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards c54ca29e9d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5430e9d5ad 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 9cbcc82d49 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 3e900bc249 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 31b0bbe335 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 21f55295a5 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 619f93ec4a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 5f697d2dd6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 26d95a3a1d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 82d02b3ae7 75: onsuccess: 1: Successful build after linux: 44 commits discards 24f85211f8 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 28346e894e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 81a348c453 72: onsuccess: 1: Successful build after linux: 12 commits discards e166e742b2 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards a75219c749 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 1fbf0bbeb3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards d52a4f3571 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c60041cf16 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards a5fdfb9c76 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 10a4454b91 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 33984b6383 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 303e370a82 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dcdfd99573 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new cd14098c1b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 19d80c21c3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 9e0e9cd1cb 72: onsuccess: 1: Successful build after linux: 12 commits new 00ef89321d 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 03db72c66c 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 8813be423c 75: onsuccess: 1: Successful build after linux: 44 commits new 9a4ad1ab5e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29aa62165d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 4066ec7914 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new cc0406817a 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 752facc15b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b3a72dcbef 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new c1c6bc72c9 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 8b2ff1eccc 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new b51b6fca60 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 41f8984d0c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 7fec6691ae 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3b03645566 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 5ad24e3b3e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 16802c5b4d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new a72287906d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 23f695fde9 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new bb54266af7 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3db96e734e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 15c02147ce 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new fa5eef648d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 1295fb9196 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 2ae54d8ff6 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 5f653f45a1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 3aae0c1005 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 7a9f925cca 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 62d4ed0d59 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 6bb1f093cb 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ede47a6e8d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new eadf00b3a1 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 305a6914d7 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 8deb52e74d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 48483804fc 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 21fae951cd 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new c4bf6412e7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 8d6dff6b8b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 5bb2785cdd 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new db9ce9fac7 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new e5a897a0e3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 8b02383e8b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 39656a5eb4 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new dbea7713ad 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 0b54db629b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new f469bf2fa7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 9a8e82ac75 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 874646175d 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 85579b6d98 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 7b209f6ef0 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0d8a8dd038 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 64ffaf4331 124: onsuccess: #2159: 1: Success after linux: 23 commits new 4990eca4c7 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 8967f46214 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 93883717a1 127: onsuccess: #2162: 1: Success after gcc: 9 commits new dc6e260328 128: onsuccess: #2163: 1: Success after linux: 23 commits new 9d1e986f3f 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new f906d2a6d0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new ca56548d27 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 62a33d02a1 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 1a404845bf 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 9c200b6df8 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 60db054673 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 094eefa034 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 89663073eb 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d1829fcfc2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 9dffde6211 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 70ff120b3d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 454c317925 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 09c558d64d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new c032eb24a7 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 143378cd8e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 3b7c16890a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 1e425354e5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 2535232b84 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new a2b5be8550 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 344dc2f1ba 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 2e2fac2d3f 150: onsuccess: #2185: 1: Success after gcc: 3 commits new a200b51305 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 19b0772c0e 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 0321d1f524 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 60af5076d1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 3763506211 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 13fbe50d93 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 6fa36010b1 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 0b7b6173e9 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 6bb117065b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 58080615ee 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 48affeb78e 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new b64ca4a460 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new b2d581b648 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 0d5deabaf6 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 62c1c20679 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 2aecdab5d0 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 071f9fe81c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...]
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 (0cbef42b73) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1712 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31104 -> 30540 bytes 04-build_abe-stage1/console.log.xz | Bin 73140 -> 72488 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9220 -> 9536 bytes 07-build_abe-glibc/console.log.xz | Bin 239960 -> 239692 bytes 08-build_abe-stage2/console.log.xz | Bin 205060 -> 204848 bytes 09-build_abe-gdb/console.log.xz | Bin 37748 -> 37660 bytes 10-build_abe-qemu/console.log.xz | Bin 32188 -> 31428 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2944 -> 2544 bytes 13-check_regression/console.log.xz | Bin 6704 -> 7628 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 17 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 45 +- 13-check_regression/results.compare2 | 310 +- 13-check_regression/results.regressions | 51 - 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 51 - sumfiles/g++.log.xz | Bin 3438928 -> 3417424 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 3002280 -> 3023120 bytes sumfiles/gcc.sum | 5172 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1030516 -> 1028440 bytes sumfiles/gfortran.sum | 61 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202248 -> 202268 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427484 -> 422452 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 3135 insertions(+), 2965 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions