Probo tasks not appearing in the order they execute

[Auspicus]

The build steps that we have above execute in the order:

• install node
• npm install
• es lint
• sass lint
• install test suite
• run tests

However, when looking on probo.ci the install node task is showing up after sass lint.

[thom8]

I've also been able to replicate this issue

[AlexU-A]

@tortillaj - any ideas as to why this might be happening in the app.probo.ci interface?

[sk33lz]

@EdiSch and @thom8 can you please contact us on Zendesk with your build id or link for a build this is occurring on? That will help us debug this issue. Thanks!

[ElusiveMind]

This is an active issue still and is being investigated. It is important to note that all build steps DO happen in the order inside the .probo.yml file, but are not reflected that way on the interface.