Page MenuHomeSoftware Heritage

Software Heritage Python tests

Build Steps

    • Build a working copy in Drydock.
    Output Artifacts
    Working Copytest-artifact
    • Run command curmodule=$(basename $(pwd)); cd ../swh-environment; mr -t -j5 up; for file in * .mrconfig; do if [ $file != $curmodule ]; then rm -rf ../$file; cp -r $file ../; fi; done on test-artifact.
    Depends On
    Build StepClone on Software Heritage Worker
    Input Artifacts
    Drydock Leasetest-artifact
  • Step 3.1 Python tests
    • Run command env PYTHONPATH=$(cd ..; bash ./pythonpath.sh --print) python3 -m nose -sva !db $(find . -name tests -type d) on test-artifact.
    Depends On
    Build StepUpdate environment from working copy
    Build StepClone on Software Heritage Worker
    Input Artifacts
    Drydock Leasetest-artifact
  • Step 3.2 Lint
    • Run command make check on test-artifact.
    Depends On
    Build StepUpdate environment from working copy
    Build StepClone on Software Heritage Worker
    Input Artifacts
    Drydock Leasetest-artifact

Plan Behaviors

NameBehaviorDetails
Hold DraftsAlwaysRevisions are not sent for review until the build completes, and are returned to the author for updates if the build fails.
Edit
Warn When LandingAlways"arc land" warns if the build is still running or has failed.
Edit
Affects BuildableAlwaysThe buildable waits for the build, and fails if the build fails.
Edit
RestartableAlwaysThe build may be restarted.
Edit
RunnableIf EditableOnly users who can edit the plan can run it manually.
Edit

Run By Herald Rules

  • No active Herald rules trigger this build.

Recent Builds

Event Timeline

olasd renamed this build plan from "Run tests" to "Software Heritage Python tests".Mar 8 2016, 3:40 PM
olasd changed the visibility from "All Users" to "Public (No Login Required)".Aug 1 2016, 11:29 AM