Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-editing-services
gst-editing-services
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 77
    • Issues 77
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GStreamer
  • gst-editing-servicesgst-editing-services
  • Issues
  • #4

Closed
Open
Opened Nov 16, 2011 by Bugzilla Migration User@bugzilla-migration

Tests for huge timelines in the integration test suite

Submitted by Jeff Fortin Tam @nekohayo

Link to original bug (#664222)

Description

The huge amount of rendering bugs in pitivi prompts for some more solid automated torture testing. Hopefully, the simpler use cases might be solved by the port to GES, but there remains a need for testing "serious business" projects. While rare, it is not unusual to hear reports of users trying to deal with hundreds of clips or very long timelines, and running into kernel limitations, hangs/crashes or memory problems.

For GES to be considered ready for serious production needs, we would need some test suite (using "insanity" to complement the existing "nekohayo"?) to run at least the following scenarios:

  • a timeline with 2000 different clips
  • a timeline with a couple of multi-gigabyte files
  • feature-length projects (timelines that are 1-3 hours long)

Tests should ensure that those timelines render flawlessly, and could also profile loading times, seeking times, memory usage, etc.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gst-editing-services#4