Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • emulab-devel emulab-devel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 160
    • Issues 160
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emulab
  • emulab-develemulab-devel
  • Repository
Switch branch/tag
  • emulab-devel
  • apt
  • create_instance.in
Find file BlameHistoryPermalink
  • Leigh B Stoller's avatar
    Add a little more parsing of stitcher error output so that we can classify · f9759233
    Leigh B Stoller authored Mar 14, 2016
    errors properly (not enough nodes, not enough bandwidth, etc) rather then
    everything just getting "stitcher error". This will make the numbers on the
    dashboard page look much better!
    f9759233