Skip to content

haskell-gargantext
haskell-gargantext

Improve startup error from runDbCheck 

Previously we would fail with a generic message suggesting to run
`gargantext-init`, but that wouldn't always be the case; sometimes
there might be problems connecting to the database, and we want to
show the raw exception. This code should help diagnosing what's wrong.

It also changes the error hint to report the correct executable, as
these days we use `gargantext-cli init` instead.
4 jobs for adinapoli/improve-error-at-startup in 63 minutes and 11 seconds (queued for 4 seconds)
latest
4c97676e 4c97676eaef20e270cdffacc9b2839b7eda35887
Status Job ID Name Coverage
  Cabal
passed #15073
cabal

00:27:52

 
  Stack
passed #15074
stack

00:05:10

 
  Bench
manual #15075
allowed to fail manual
bench
 
  Test
failed #15076
test

00:30:07

 
Name Stage Failure
failed
test Test 
calling stop notifications - done
Test suite garg-test-hspec: PASS
Test suite logged to:
/builds/gargantext/haskell-gargantext/dist-newstyle/build/x86_64-linux/ghc-9.4.8/gargantext-0.0.7.3/t/garg-test-hspec/opt/test/gargantext-0.0.7.3-garg-test-hspec.log
1 of 1 test suites (1 of 1 test cases) passed.
Error: cabal: Tests failed for test:garg-test-tasty from gargantext-0.0.7.3.

Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1