Skip to content
Haskell CI

Reduce allocations #70

Sign in to view logs

Reduce allocations

Reduce allocations #70

Triggered via pull request September 20, 2024 12:08
@dcouttsdcoutts
synchronize #22
dcoutts/allocations-reduction
Status Failure
Total duration 3m 13s
Artifacts –

haskell.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 10 warnings
build (9.10.1, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’
build (9.10.1, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.10.1, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.10.1, 3.10.3.0, ubuntu-latest, liburing-2.6)
Process completed with exit code 1.
build (9.8.2, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’ with ‘GHC.ST.ST s’
build (9.8.2, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.8.2, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.8.2, 3.10.3.0, ubuntu-latest, liburing-2.6)
Process completed with exit code 1.
build (8.10.7, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L143
• Couldn't match type ‘s’ with ‘VM.PrimState m0’
build (8.10.7, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (8.10.7, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (8.10.7, 3.10.3.0, ubuntu-latest, liburing-2.6)
Process completed with exit code 1.
build (9.6.5, 3.10.3.0, ubuntu-22.04, system): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’ with ‘GHC.ST.ST s’
build (9.6.5, 3.10.3.0, ubuntu-22.04, system): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.6.5, 3.10.3.0, ubuntu-22.04, system): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.6.5, 3.10.3.0, ubuntu-22.04, system)
Process completed with exit code 1.
build (9.4.8, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’ with ‘GHC.ST.ST s’
build (9.4.8, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.4.8, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.4.8, 3.10.3.0, ubuntu-latest, liburing-2.6)
Process completed with exit code 1.
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.1): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’ with ‘GHC.ST.ST s’
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.1): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.1): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.1)
Process completed with exit code 1.
build (9.6.5, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’ with ‘GHC.ST.ST s’
build (9.6.5, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.6.5, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.6.5, 3.10.3.0, ubuntu-latest, liburing-2.6)
Process completed with exit code 1.
build (9.2.8, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L143
• Couldn't match type ‘s’ with ‘VM.PrimState m0’
build (9.2.8, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.2.8, 3.10.3.0, ubuntu-latest, liburing-2.6): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.2.8, 3.10.3.0, ubuntu-latest, liburing-2.6)
Process completed with exit code 1.
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.6): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’ with ‘GHC.ST.ST s’
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.6): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.6): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.6)
Process completed with exit code 1.
build (9.6.5, 3.10.3.0, ubuntu-22.04, liburing-2.1): benchmark/Bench.hs#L143
• Couldn't match type ‘m0’ with ‘GHC.ST.ST s’
build (9.6.5, 3.10.3.0, ubuntu-22.04, liburing-2.1): benchmark/Bench.hs#L146
• Ambiguous type variable ‘m0’ arising from a use of ‘return’
build (9.6.5, 3.10.3.0, ubuntu-22.04, liburing-2.1): benchmark/Bench.hs#L151
• Ambiguous type variable ‘m0’ arising from a use of ‘VM.unsafeWrite’
build (9.6.5, 3.10.3.0, ubuntu-22.04, liburing-2.1)
Process completed with exit code 1.
build (9.10.1, 3.10.3.0, ubuntu-latest, liburing-2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.8.2, 3.10.3.0, ubuntu-latest, liburing-2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (8.10.7, 3.10.3.0, ubuntu-latest, liburing-2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.6.5, 3.10.3.0, ubuntu-22.04, system)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.4.8, 3.10.3.0, ubuntu-latest, liburing-2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.6.5, 3.10.3.0, ubuntu-latest, liburing-2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.2.8, 3.10.3.0, ubuntu-latest, liburing-2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.6.5, 3.10.3.0, ubuntu-20.04, liburing-2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (9.6.5, 3.10.3.0, ubuntu-22.04, liburing-2.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/