Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L lisa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Tooling
  • lisa
  • Issues
  • #543
Closed
Open
Created Jan 18, 2018 by Darryl Green@Darryl.GreenOwner

Wltest setup bugs

Created by: qperret

When setting up wltest for the first time we noticed that the following problems are not caught:

  • it is possible to run lisa-wltest-series without having the virtualenv binary installed which leads to all sorts of errors. The presence of virtualenv should be checked in lisa-wltest-init
  • when there are permissions issues with fastboot (udev rules not set correctly, sudo rights needed, ...) the user will face the "timeout to reboot in bootloader" error. This should be caught with a better error message at least.
Assignee
Assign to
Time tracking