Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

docs CI tests failing

See original GitHub issue

Description of problem:

tox -edocs fails with errors. This is causing GitHub tests to fail.

See: https://github.com/log2timeline/plaso/runs/5977142890?check_suite_focus=true

/plaso/plaso/engine/engine.py:docstring of plaso.engine.engine.BaseEngine.GetSourceFileSystem:15: ERROR: Unexpected indentation.
/plaso/plaso/formatters/yaml_formatters_file.py:docstring of plaso.formatters.yaml_formatters_file.YAMLFormattersFile:15: ERROR: Unexpected indentation.
/plaso/plaso/lib/dtfabric_helper.py:docstring of plaso.lib.dtfabric_helper.DtFabricHelper:32: ERROR: Unexpected indentation.
/plaso/plaso/parsers/docker.py:docstring of plaso.parsers.docker.DockerJSONParser:5: ERROR: Unexpected indentation.
/plaso/plaso/parsers/dpkg.py:docstring of plaso.parsers.dpkg:13: ERROR: Unexpected indentation.
/plaso/plaso/parsers/dpkg.py:docstring of plaso.parsers.dpkg:20: ERROR: Unexpected indentation.
/plaso/plaso/parsers/presets.py:docstring of plaso.parsers.presets.ParserPresetsManager.GetPresetsInformation:9: ERROR: Unexpected indentation.
/plaso/plaso/parsers/sqlite_plugins/ls_quarantine.py:docstring of plaso.parsers.sqlite_plugins.ls_quarantine.LsQuarantinePlugin:5: ERROR: Unexpected indentation.
/plaso/plaso/parsers/sqlite_plugins/mac_notificationcenter.py:docstring of plaso.parsers.sqlite_plugins.mac_notificationcenter.MacNotificationCenterPlugin:8: ERROR: Unexpected indentation.
/plaso/plaso/parsers/sqlite_plugins/windows_timeline.py:docstring of plaso.parsers.sqlite_plugins.windows_timeline.WindowsTimelinePlugin.ParseGenericRow:5: ERROR: Unexpected indentation.
/plaso/plaso/parsers/winreg_plugins/ccleaner.py:docstring of plaso.parsers.winreg_plugins.ccleaner.CCleanerPlugin:16: ERROR: Unexpected indentation.
build finished with problems, 87 warnings.

Command line and arguments:

tox -edocs

Plaso version:

latest main branch

Full output See https://github.com/log2timeline/plaso/runs/5977142890?check_suite_focus=true

Issue Analytics

State:
Created a year ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

joachimmetzcommented, Apr 12, 2022

From now on, debugging related to testing issues will be left in the thread of the issue without requesting an assignment.

Don’t hesitate to add debug findings to an issue thread. We can always assign it later. I’m wary of issues that need attention and that are waiting on expectation to be resolved by assignee. For feature requests I’m happy to assign you, indicates that you’re working on it.

Or should I work on the issue first and then connect the PR?

Yeah feel free to propose a PR. Though I would recommend getting to the core of the issue first and discuss possible solution.

To ask you an additional question, is there any criteria for Assign for Issue?

No this is not a formal process at this time.

0reactions

joachimmetzcommented, Apr 12, 2022

GitHub docs pages also appear flaky with local browser, adding an URL check ignore for now https://github.com/log2timeline/plaso/pull/4072

Top Results From Across the Web

CICD - How To Resolve Failing Tests - Undo.io

Achieving this requires having a zero-tolerance of failing tests. Tests must pass reliably and when they don't, to avoid delivery delays, failing test...

Debugging Failing Tests and Test Pipelines - GitLab

These guidelines are intended to help you to investigate end-to-end test pipeline failures so that they can be properly addressed. This will involve...

How to Reduce Test Failures in CI/CD Pipelines? - Foresight

In this blog, we discuss how to fix tests on CI servers, when to take failing tests seriously, and how to simplify the...

How to Fix Flaky Tests - Semaphore CI

Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....

Why are my tests failing in CI and not locally? #597 - GitHub

This exists here https://docs.cypress.io/faq/questions/using-cypress-faq.html#Why-do-my-Cypress-tests-pass-locally-but-not-in-CI.