• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

processone / ejabberd / 844
34%

Build:
DEFAULT BRANCH: master
Ran 22 Nov 2024 06:50PM UTC
Jobs 1
Files 292
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

22 Nov 2024 06:25PM UTC coverage: 32.912% (+0.001%) from 32.911%
844

push

github

badlop
Fix problem starting ejabberd when first host uses SQL, other one mnesia

The problem appeared when there are several vhosts,
the first vhost uses SQL for persistent data (and RAM for volatile),
and another vhost wants to use Mnesia

Example config to trigger the problem:

  hosts:
    - mysql.localhost
    - localhost
  host_config:
    mysql.localhost:
      default_db: sql

In that case, ejabberd crashed at start with an error like:
[critical] Internal error of module mod_muc has occurred during start:
...
** exception exit: {aborted,
                     {no_exists,
                         [muc_room,
                          [{{muc_room,{'_',<<"conference.localhost">>},'_'},
                            [],
                            ['$_']}]]}}

1 of 1 new or added line in 1 file covered. (100.0%)

1 existing line in 1 file now uncovered.

14587 of 44321 relevant lines covered (32.91%)

619.67 hits per line

Uncovered Existing Lines

Lines Coverage ∆ File
1
52.53
-0.33% src/mod_muc_mnesia.erl
Jobs
ID Job ID Ran Files Coverage
1 844.1 22 Nov 2024 06:50PM UTC 292
32.91
GitHub Action Run
Source Files on build 844
  • Tree
  • List 292
  • Changed 36
  • Source Changed 1
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • c291c20a on github
  • Prev Build on master (#840)
  • Next Build on master (#848)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc