Building an easystack.yml with --job results in redundant/conflicting build jobs for common dependencies

[stderr-enst]

If an easystack.yml contains two packages with the same dependent package (e.g. "GCCcore"), building the easystack file with -r and --job results in multiple submitted build jobs for that package.

Of course the first job wins and builds happily, but subsequent attempts fail with different failure modes.

@ocaisa suggested in a slack discussion:

For your use case, you'd have to retain some knowledge of what has been submitted. It just needs some design, a dict perhaps that gets updated with submitted jobs, if you get a hit you link the job id, if not you submit a job and add to the dict

[ocaisa]

I looked into it a bit, one way to do it is

• add an optional argument (full_ordered_ecs) to https://github.com/easybuilders/easybuild-framework/blob/develop/easybuild/main.py#L295 which holds the complete ordered list of easyconfigs,
• use that to filter ordered_ecs at https://github.com/easybuilders/easybuild-framework/blob/develop/easybuild/main.py#L556

  if full_ordered_ecs:
  ordered_ecs = [ec for ec in ordered_ecs if ec not in full_ordered_ecs]
  full_ordered_ecs = full_ordered_ecs + ordered_ecs

• return an updated value for full_ordered_ecs at https://github.com/easybuilders/easybuild-framework/blob/develop/easybuild/main.py#L597

  return overall_success, full_ordered_ecs

• Tweak https://github.com/easybuilders/easybuild-framework/blob/develop/easybuild/main.py#L226 to use full_ordered_ecs