yuanbiao
/
emqx
1
0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: test issue (probably) caused by application start order 

After adding `emqx_rule_engine` to the `app.src` file for
`emqx_ee_schema_registry` the test suites in `emqx_ee_schema_registry`
started to fail when they where run together with
`make "lib-ee/emqx_ee_schema_registry-ct"`. However, they still worked
when executed one by one with
`SUITE=lib-ee/emqx_ee_schema_registry/test/emqx_ee_schema_registry_http_api_SUITE.erl make ct-suite`.
The failure probably happened as this changed the application start
order. As `emqx_ee_schema_registry` only requires `emqx_rule_engine` to be
loaded, `emqx_rule_engine` can be put in the included_applications list in
the emqx_ee_schema_registry.app.src file instead (this solved the issue).
This commit is contained in:
Kjell Winblad 2023-07-03 18:07:40 +02:00
parent 6c2185bed7
commit 86a38b98b2
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
lib-ee/emqx_ee_schema_registry/src/emqx_ee_schema_registry.app.src
View File

@ -3,12 +3,14 @@
{vsn, "0.1.5"}, {vsn, "0.1.5"},
{registered, [emqx_ee_schema_registry_sup]}, {registered, [emqx_ee_schema_registry_sup]},
{mod, {emqx_ee_schema_registry_app, []}}, {mod, {emqx_ee_schema_registry_app, []}},
{included_applications, [
emqx_rule_engine
]},
{applications, [ {applications, [
kernel, kernel,
stdlib, stdlib,
erlavro, erlavro,
gpb, gpb
emqx_rule_engine
]}, ]},
{env, []}, {env, []},
{modules, []}, {modules, []},

2
lib-ee/emqx_ee_schema_registry/test/emqx_ee_schema_registry_SUITE.erl
View File

@ -814,7 +814,7 @@ t_sparkplug_decode(_Config) ->
?assertMatch(#{data := ExpectedRuleOutput}, Res), ?assertMatch(#{data := ExpectedRuleOutput}, Res),
ok. ok.
t_sparkplug_encode(Config) -> t_sparkplug_encode(_Config) ->
%% Default message name field is 'Payload' %% Default message name field is 'Payload'
SQL = SQL =
<< <<