From f12871451f2c60bc35da053198ccc48d1b1db687 Mon Sep 17 00:00:00 2001
From: Fred Hebert <mononcqc@ferd.ca>
Date: Wed, 6 Dec 2017 08:53:12 -0500
Subject: Safer purge switch

Rather than the caller having to think of what to purge or not, use
erlang:check_process_code/2 to detect if the caller (rebar3) may die
because of the operation.

If so, do a soft purge with a conditional delete instead of a hard purge
with a mandatory delete.
---
 systest/all_SUITE.erl | 1 +
 1 file changed, 1 insertion(+)

(limited to 'systest')

diff --git a/systest/all_SUITE.erl b/systest/all_SUITE.erl
index ba06a9c..6d2f14f 100644
--- a/systest/all_SUITE.erl
+++ b/systest/all_SUITE.erl
@@ -66,6 +66,7 @@ alias_clash(Config) ->
     ?assertNotEqual(nomatch,
         re:run(Output, "Not adding provider default test from module rebar_prv_alias_test "
                        "because it already exists from module rebar_prv_alias_test")),
+    ok.
 
 grisp_explode() ->
     [{doc, "Don't force purge a plugin that runs the compile job itself"}].
-- 
cgit v1.1