Skip to content
This repository has been archived by the owner on Oct 22, 2023. It is now read-only.

Weird dependency execution order #53

Closed
ineffyble opened this issue Jan 16, 2019 · 6 comments
Closed

Weird dependency execution order #53

ineffyble opened this issue Jan 16, 2019 · 6 comments
Labels

Comments

@ineffyble
Copy link
Contributor

ineffyble commented Jan 16, 2019

I've run into a situation where tasks are executing in an unexpected fashion. I've replicated this situation with the batect.yml below.

Expected behaviour: makeTheSandwich runs before takeABiteOfTheSandwich

Is there something I'm missing in my dependency tree that's causing it to run in this order?

batect.yml.txt

@charleskorn
Copy link
Collaborator

Thanks for the feedback @ineffyble. Just to be clear, which task are you running? (ie. ./batect <some-task-name-here>)

@ineffyble
Copy link
Contributor Author

Oops, sorry. ./batect sandwichHasBeenEaten

@charleskorn
Copy link
Collaborator

Right, so if I understand correctly, the order in prerequisites is not respected?

I would expect the execution order to be:

  • getSandwichContents
  • putContentsInBread
  • prepareTheTable
  • makeTheSandwich
  • takeABiteOfTheSandwich
  • eatTheSandwich
  • sandwichHasBeenEaten

If that's not what's happening then this sounds like a bug, not something you're missing in your configuration.

@ineffyble
Copy link
Contributor Author

That's right - they're running in the wrong order.

Good to know it is a bug and just not me goofing up.

@charleskorn
Copy link
Collaborator

Alright, I'll take a look into it. Thanks for the detailed report and reproduction!

@charleskorn
Copy link
Collaborator

I've just pushed a fix for this, and will publish a release shortly.

Thanks again for taking the time to report the issue and for providing a reproduction @ineffyble!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

2 participants