Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 177
    • Issues 177
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Issues
  • #408

Closed
Open
Opened Sep 27, 2024 by Alfredo Di Napoli@AlfredoDiNapoli
  • Report abuse
  • New issue
Report abuse New issue

Various test failures

Currently dev doesn't pass all the tests cleanly on CI. At least two things which stood out from past runs:

  • marking stuff behaves as expected fails:
      marking stuff behaves as expected:                              FAIL (1.45s)
        uncaught exception: PatternMatchFail
        test/Test/Utils/Jobs.hs:409:7-49: Non-exhaustive patterns in [jl0,
                                          jl1,
                                          jl2,
                                          jl3,
                                          jl4,
                                          jl5,
                                          jl6]
  • Some async notifications contains (uncaught) errors

At least in one place I could see:

[DEBUG] [central_exchange] sending: {"js":{"id":"4-1727373085.986721983000-0b343a288f27f48dc020255d002f8720655fe2c263393b755362d634ce86f332","log":[{"events":[{"level":"ERROR","message":"Error in $: parsing Gargantext.Core.Text.Corpus.Parsers.JSON.JSONStruct(JSONStruct) failed, key \"garg_version\" not found"}],"failed":3,"remaining":0,"succeeded":0}],"status":"IsRunning"},"type":"update_job_progress"}

But this is not reflected in any failure (to my knowledge).

@anoe Broken tests are not nice, so if you are OK with it, I will do a quick detour on Monday and work on fixing those, if the fix is cheap enough.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
Bug
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#408