--fail-fast dont work on multhread execution

[T00595]

Hello everything is fine? I have a very specific problem with the gem, here in our project we run the automation in parallel on a farm of devices, we try to apply the fail fast command but when we run it like this, the command does not generate the cucumber report since it just kills the threads but does not generate the final report, why do we want that? We have the smoke tests and we need it to stop running when it finds the first failure to save time for the next run.

here the command used:
execute_command logger "bundle exec parallel_cucumber #{load_features_path_from_file(args)} -n #{number_of_devices(args)} --group-by scenarios --first-is-1 --fail-fast "

here it interrupts the threads but does not generate the cucumber report:

[grosser]

that might be fixable by making the other processes finalize the report on_exit / when Interrupt-ed
PR welcome, maybe start by making a failing test case

[T00595]

But we assemble the report in at_exit, but what happens is that when the threads are interrupted the json files not exist fro him to assemble the final report, he simply stops the execution

[T00595]

at_exit do finish_labmobile_execution if SESSION_TYPE.eql?('continuous') && TEST_LOCATION.eql?('labmobile') if ENV.fetch('TEST_ENV_NUMBER', nil) && ParallelTests.first_process? ParallelTests.wait_for_other_processes_to_finish options = { report_path: File.join('reports', "features_report_#{PLATFORM}") } ReportBuilder.build_report ReportBuilder.options.merge(options) end end

[grosser]

each worker also has to dump their report at_exit to make this work ?

[T00595]

each worker also has to dump their report at_exit to make this work ?

in this case yes, because they are independent executions and at the end it groups all the reports

[T00595]

any news?

[grosser]

idk this is complicated 😞
... can you make a simple example repo that shows the problem ?
would help verifying any fix that we come up with and allow me to play with the setup you are running

[T00595]

idk this is complicated 😞 ... can you make a simple example repo that shows the problem ? would help verifying any fix that we come up with and allow me to play with the setup you are running

ok, let's try to reproduce our project without exposing our data, as soon as we have it we will attach it here

[grosser]

Ideally just as simple a pic as possible 😀

…

On Thu, Mar 30, 2023, 1:08 PM T00595 ***@***.***> wrote: idk this is complicated 😞 ... can you make a simple example repo that shows the problem ? would help verifying any fix that we come up with and allow me to play with the setup you are running ok, let's try to reproduce our project without exposing our data, as soon as we have it we will attach it here — Reply to this email directly, view it on GitHub <#895 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAACYZYLMDHDABH2L6YSEYLW6XR3PANCNFSM6AAAAAAVWVGZEM> . You are receiving this because you commented.Message ID: ***@***.***>

[ramosjuliano]

@grosser As per the above conversation, here is a structure similar to ours. It has a basic test, but it shows the same error as ours.

https://github.com/ramosjuliano/automation-app

[grosser]

Error Message:
  Oracle instant client is not found.
  You need to install Oracle instant client.

and when I remove ruby-oci8 I get

NO VIRTUAL DEVICES FOUND, MAKE SURE YOU HAVE SOME VIRTUAL DEVICE CREATED!

when I meant was an example that has 2-4 tests that all sleep for example and then 1 of them fails
no gems except parallel_tests + cucumber and especially no databases :)

[T00595]

Error Message:
  Oracle instant client is not found.
  You need to install Oracle instant client.

and when I remove ruby-oci8 I get

NO VIRTUAL DEVICES FOUND, MAKE SURE YOU HAVE SOME VIRTUAL DEVICE CREATED!

when I meant was an example that has 2-4 tests that all sleep for example and then 1 of them fails no gems except parallel_tests + cucumber and especially no databases :)

about the devices, you need to have android studio installed on your machine together with the appium, create a device in the android studio nexus 5x, after that start the appium and run the automation code so you won't have this error.