test: add create and drop sink test for nexmark

[lmatz]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Previously the drop sink can be stuck (not sure if it is stuck forever or comes back to normal after a long period of time)
After #8672, the drop sink is super fast.
We add drop sink into e2e tests to avoid similar problems from happening again in the future

Checklist For Contributors

• [ ] I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• [ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• [ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
• All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

• I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

• My PR DOES NOT contain user-facing changes.

Click here for Documentation

Types of user-facing changes

Please keep the types that apply to your changes, and remove the others.

• Installation and deployment
• Connector (sources & sinks)
• SQL commands, functions, and operators
• RisingWave cluster configuration changes
• Other (please specify in the release note below)

Release note

[BugenZhao]

There seem too many logs. Can we disable these?

2023-03-21T09:19:25.490674Z  INFO risingwave_frontend::scheduler::hummock_snapshot_manager: Unpin epoch 4073400070111232 with RPC

2023-03-21T09:14:24.546932Z  INFO risingwave_meta::hummock::manager: report_scale_compactor_info ScaleCompactorInfo { running_cores: 1, total_cores: 16, waiting_compaction_bytes: 0 } suggest_scale_out_core 0

[lmatz]

timeout?

[BugenZhao]

[codecov]

Codecov Report

Merging #8686 (95b6316) into main (e294250) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #8686      +/-   ##
==========================================
- Coverage   70.88%   70.87%   -0.01%     
==========================================
  Files        1197     1197              
  Lines      199012   199012              
==========================================
- Hits       141069   141059      -10     
- Misses      57943    57953      +10     

Flag	Coverage Δ
rust	70.87% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 6 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[BugenZhao]

The e2e-source lasts too long and becomes the bottleneck of the workflow. 🥵 Is it possible to split it into another step?

[xxchan]

Is the speed expected?

The e2e-source lasts too long and becomes the bottleneck of the workflow.

Can we move to e2e-sink?

[tabVersion]

+1

[lmatz]

this is weird, I tested locally on my Mac, and it finishes very fast besides the 20-second sleep on purpose...
🤔
After Bugen's two PR that makes drop sink completely async, drop sink is expected to be very fast.

This PR intends to detect this type of anomaly though.

[xxchan]

Wait, can we run the tests in parallel?! 🥵

[tabVersion]

basically LGTM
lets keep watching the CI

[tabVersion]

+1

[tabVersion]

Wait, can we run the tests in parallel?! 🥵

Yes, any step behind build can run in parallel

[xxchan]

Wait, can we run the tests in parallel?! 🥵

Yes, any step behind build can run in parallel

I mean sqllogictest -j

[lmatz]

Succeed once after moving to the e2e sink test:
https://buildkite.com/risingwavelabs/pull-request/builds/21269#01876fa5-474c-41a5-8a35-ebcaa51afaa8

Good to merge?