Skip to content

Skipped Task unexpectedly evaluate both output.as and export.as #481

@cdavernas

Description

@cdavernas

I tried this:

Run a task that defines an unmatched if clause

This happened:

Both output.as and export.as in the task were evaluated. Moreover, export.as ended up applying to the entire context instead of the task's output, causing the context to become invalid.

I expected this:

output.as and export.as to be ignored for a skipped task

Is there a workaround?

No response

Anything else?

No response

Platform(s)

No response

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞

Metadata

Metadata

Assignees

Labels

app: runnerConcerns the Runnerpriority: highIndicates a high priority issuetype: bugSomething isn't workingweight: 2An issue with a low development impact

Type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions