Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected errors collecting all the tests of the repository #3969

Closed
Rebits opened this issue Feb 17, 2023 · 6 comments
Closed

Unexpected errors collecting all the tests of the repository #3969

Rebits opened this issue Feb 17, 2023 · 6 comments
Assignees
Labels

Comments

@Rebits
Copy link
Member

Rebits commented Feb 17, 2023

Description

Currently, repository test collection fails

../../../../.local/lib/python3.10/site-packages/_pytest/config/__init__.py:1488: in getoption
    val = getattr(self.option, name)
E   AttributeError: 'Namespace' object has no attribute 'fim_database_memory'

The above exception was the direct cause of the following exception:
../../../../.local/lib/python3.10/site-packages/pluggy/manager.py:127: in register
    hook._maybe_apply_history(hookimpl)
../../../../.local/lib/python3.10/site-packages/pluggy/hooks.py:333: in _maybe_apply_history
    res = self._hookexec(self, [method], kwargs)
../../../../.local/lib/python3.10/site-packages/pluggy/manager.py:93: in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
../../../../.local/lib/python3.10/site-packages/pluggy/manager.py:84: in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
integration/conftest.py:325: in pytest_configure
    fim_database_memory = config.getoption("--fim-database-memory")
../../../../.local/lib/python3.10/site-packages/_pytest/config/__init__.py:1499: in getoption
    raise ValueError(f"no option named {name!r}") from e
E   ValueError: no option named 'fim_database_memory'

@Rebits
Copy link
Member Author

Rebits commented Feb 20, 2023

Update 20/02/2023

Rebits added a commit that referenced this issue Feb 21, 2023
Rebits added a commit that referenced this issue Feb 21, 2023
Rebits added a commit that referenced this issue Feb 21, 2023
Rebits added a commit that referenced this issue Feb 21, 2023
@Rebits Rebits linked a pull request May 19, 2023 that will close this issue
8 tasks
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
Rebits added a commit that referenced this issue May 22, 2023
@Rebits Rebits assigned juliamagan and unassigned juliamagan Jun 28, 2023
@Rebits
Copy link
Member Author

Rebits commented Jul 28, 2023

  • Apply requested changes. I need more feedback from @mauromalara in order to continue with the suggestions

@mauromalara
Copy link
Contributor

Review comment No. 1

  • Checked changes, all OK.
  • Asked for last 2 changes to be applied

juliamagan added a commit that referenced this issue Sep 7, 2023
juliamagan pushed a commit that referenced this issue Sep 7, 2023
juliamagan pushed a commit that referenced this issue Sep 7, 2023
juliamagan pushed a commit that referenced this issue Sep 7, 2023
@wazuhci wazuhci moved this to On hold in Release 4.5.3 Sep 7, 2023
@wazuhci wazuhci removed this from Release 4.5.3 Sep 13, 2023
@wazuhci wazuhci moved this to On hold in Release 4.5.3 Sep 13, 2023
@verdx verdx removed this from Release 4.5.3 Sep 15, 2023
@wazuhci wazuhci moved this to On hold in Release 4.8.0 Sep 15, 2023
@wazuhci wazuhci moved this to On hold in Release 4.9.0 Nov 6, 2023
@wazuhci wazuhci removed this from Release 4.8.0 Nov 6, 2023
@Rebits Rebits moved this from On hold to In progress in Release 4.9.0 Jan 3, 2024
@Rebits Rebits moved this from In progress to On hold in Release 4.9.0 Jan 3, 2024
@wazuhci wazuhci moved this from On hold to Blocked in Release 4.9.0 Mar 8, 2024
@havidarou havidarou closed this as not planned Won't fix, can't repro, duplicate, stale Apr 8, 2024
@wazuhci wazuhci moved this from Blocked to Done in Release 4.9.0 Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

6 participants