lessless
Hello,
I’m trying to test that worker terminates via {:stop, reason, state} after a certain number of retries. My first attempt was to use Process.flag(:trap_exit, true)
test "worker termination after all retries failed", ctx do
error = ~s<{"just": "because"}>
{:ok, wrk} = GenServer.start(Elastic.Worker, nil)
Process.flag(:trap_exit, true)
Application.put_env(:tirexs, :uri, endpoint_url(ctx.bypass.port))
Bypass.expect(ctx.bypass, &Plug.Conn.send_resp(&1, 500, error))
Elastic.Worker.insert(wrk, ctx.doc, Property)
assert_receive {:EXIT, ^wrk, ^error}, 1000
end
it failed due to reason described here Trapping GenServer exits in ExUnit tests · Issue #3507 · elixir-lang/elixir · GitHub and then I tried to wrap operation in try/catch/rescue block
{:ok, wrk} = GenServer.start(Elastic.Worker, nil)
Elastic.Worker.insert(wrk, ctx.doc, Property)
:timer.sleep(1000)
rescue
msg -> IO.inspect "rescued #{msg}"
catch
msg -> IO.inspect "catched #{msg}"
end
No luck as well as with catch_exit and assert_raise:
assert catch_exit((fn ->
{:ok, wrk} = GenServer.start(Elastic.Worker, nil)
Elastic.Worker.insert(wrk, ctx.doc, Property)
:timer.sleep(1000)
end).()) == 1
Error mesasge (and the reason) looks like that:
.12:10:03.513 [error] GenServer #PID<0.530.0> terminating
** (stop) {:error, 500, %{just: "because"}}
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
If you are trapping exits, you need to make sure the GenServer is linked by starting it with GenServer.start_link.
lessless
The test process mailbox now has it
but, probably, due to
raisethat occurs in the GenServer there is as an error message in the console and test is considered as skipped.josevalim
If a test is skipped, it didn’t even start running. So it cannot be due to a GenServer raise inside the test. How are you running your tests?
lessless
Dang, sorry for misleading: I chose to run only second test by myself via
mix test test/lib/elastic/worker_test.exs:39, so it was the other test which was skippedWhen I run full file both scenarios are executed, but failure is still there
josevalim
I see no failure, only a logger report because your GenServer is still failing. If you want to avoid the report from being logged, add
@tag :capture_logbefore your test.lessless
thank you!