[CI] disable tests/operators/test_token_penalty.py in unit_test

[EmmonsCurse]

Motivation

[CI] disable tests/operators/test_token_penalty.py in unit_test

Root cause summary

Layer	Description
Paddle change(PaddlePaddle/Paddle#79130)	uniform_real_transform adds a post-cast boundary check: if result == max, it is clamped to min (i.e., 1.0 → 0.0)
Impact on tests	With a fixed seed, the distribution of paddle.rand in float16 changes; positions that previously never produced 0.0 may now produce 0.0
Assertion incompatibility	The test does not handle the boundary case where orig == 0.0, so expressions like 0.0 / 1.2 == 0.0 may violate assertLess expectations

Modifications

[CI] disable tests/operators/test_token_penalty.py in unit_test

Usage or Command

N/A

Accuracy Tests

N/A

Checklist

• Add at least a tag in the PR title.
  • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
  • You can add new tags based on the PR content, but the semantics must be clear.
• Format your code, run pre-commit before commit.
• Add unit tests. Please write the reason in this PR if no unit tests.
• Provide accuracy results.
• If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

[paddle-bot]

Thanks for your contribution!