Discrepancy between the number of built and executed objects in `dbt build` with unit tests

### Is this a new bug in dbt-core?

- [X] I believe this is a new bug in dbt-core
- [X] I have searched the existing issues, and I could not find an existing issue for this bug

### Current Behavior

While executing the DBT build command, I can see contradictory outputs.
e.g., I can see this.
"188 of 208 OK created sql view model my_dataset.fct_missed_sales_score_daily_v"

However, the execution stops after the 188th object as reported above.
And DBT reports the following afterwards.

"Done. PASS=188 WARN=0 ERROR=0 SKIP=0 TOTAL=188"

Just wondering: why the execution stops after the 188th object? What are the rest of the objects?
Any help would be highly appreciated!

Thanks!

### Expected Behavior

I believe the the number of objects should be the same in both cases.

I'd like to see all the 208 objects executed and reported while running the dbt build command.

### Steps To Reproduce

In our DBT project, we have models, tests, unit tests, seeds and snapshots. And the command looks like this.

"dbt build --target my_core --select tag:daily tag:intra-day"

### Relevant log output

_No response_

### Environment

```markdown
- OS: Unix
- Python: 3.10
- dbt: Running with dbt=1.8.5, Registered adapter: bigquery=1.9.0
```

### Which database adapter are you using with dbt?

bigquery

### Additional Context

_No response_