Skip to content

sb-cli false negatives for tests that are skipped for one-core machines #29

Description

@klieret

Note

This should only affect evaluation with sb-cli

Affected Instance

pylint-dev__pylint-6528

Description

The sb-cli evaluation marks pylint-dev__pylint-6528 as resolved: false even though all 4 FAIL_TO_PASS tests pass. The failure is caused by 4 PASS_TO_PASS tests being SKIPPED (not failed) in the Docker environment, which the evaluation framework then counts as regressions.

Root Cause

The Docker container used by sb-cli has only 1 CPU core. Four tests in the PASS_TO_PASS list have a skip condition requiring 2+ cores:

SKIPPED [1] tests/lint/unittest_lint.py:774: Need 2 or more cores for test to be meaningful
SKIPPED [2] tests/lint/unittest_lint.py:803: Need 2 or more cores for test to be meaningful
SKIPPED [1] tests/test_self.py:1050: Need 2 or more cores for test to be meaningful

The gold patch also changes _discover_files from @staticmethod to instance method (same as the submitted patch), so these tests would be skipped for the gold patch as well in the same environment. This means the instance is unsolvable in a single-core environment — the gold patch itself would also be marked resolved: false.

Additional Notes

  • The overall pytest result line confirms: 2 failed, 171 passed, 4 skipped, 1 xfailed
  • The 2 actual failures (test_generate_toml_config, test_generate_toml_config_disable_symbolic_names) are caused by a pre-existing tomlkit version incompatibility in the Docker image and are not in the PASS_TO_PASS list.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions