What happened: Virtual jobs continue deployment even if there are jobs in blockedBy section that are running.

What you expected to happen: Virtual jobs should not run until all jobs in the blockedBy section have completed.

How to reproduce it: Create a virtual job (job A) with job B in the blockedBy section. Run the pipeline and while job B is executing try running job A in another pipeline. It will succeed when the expected behavior is for it to be blocked until job B completes.