test_pull_path_non_ascii_or_trailing_whitespace fails with XPASS(strict)

Open Beginner friendly
#2,953 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Start with test/property/test_pebble_multipart.py and inspect test_pull_path_non_ascii_or_trailing_whitespace and its strict xfail marks. Run the reported cases to confirm why they now pass unexpectedly, then check the email parser behavior those tests cover. Done when the outdated expected failures are handled and the property test job passes.

Written by the indexing model from the issue text.

Description

tests

Summary

test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace failed in the test job, with three failures marked [XPASS(strict)]. The failures suggest the email parser mangles filenames that contain non-ASCII or trailing whitespace.

Failures

  • test: test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace[/srv/caf\xe9] failed with [XPASS(strict)] the email parser mangles the filename
  • test: test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace[/srv/file ] failed with [XPASS(strict)] the email parser mangles the filename
  • test: test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace[/srv/file\t] failed with [XPASS(strict)] the email parser mangles the filename

Workflow: ops Property Tests (nightly)
Run: https://github.com/canonical/operator/actions/runs/44762491044

Dominant language
Python
Stars
267
Forks
156
Avg merge
5d 3h
Merged PRs (30d)
43

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from canonical/operator

All issues in canonical/operator

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.