Add failing test demonstrating #422

[koral--]

PR only for bug #422 reproduction purposes. Not for direct merging.

[MiSikora]

It fails for me locally, but I'm confused. Shouldn't this test fail the CI?

[koral--]

I expect it to fail on CI. I guess that something is misconfigured on GitHub Actions 🤔
test task is invoked but I'm not sure if unit tests are actually performed. https://github.com/ChuckerTeam/chucker/pull/423/checks?check_run_id=980944852

[MiSikora]

Tests seem to run correctly here https://github.com/ChuckerTeam/chucker/pull/424/checks?check_run_id=981509232#step:4:246. Not sure what is going on. Do you test locally on Linux or macOS?

[koral--]

On macOS only.

[vbuberen]

Just 2 weeks ago I had sort of similar strange issue with Github Actions on another project. Actions just tried to build project without latest commit and I had to do some additional commit to trigger freshly updated build. Happed on a few branches.

[vbuberen]

/rebase

[vbuberen]

Trying to make Actions show logs to see info about added test.

UPD: Yeah, missed the fact that this test isn't in Chucker repo, so rebase action has no permission to do automatic rebase.

[cortinico]

I've cherry-picked your commit on a separate branch on top of develop here: https://github.com/ChuckerTeam/chucker/compare/nc/test-run-for-433

The CI actually fails: https://github.com/ChuckerTeam/chucker/runs/1016449784?check_suite_focus=true
So the issue seems to be related to #435.

Please rebase and the status should be red 👍

[koral--]

Indeed now it fails.
This Issue is addressed in #427 so it seems that this PR can be closed.