Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.web
beat.web
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.webbeat.web
  • Issues
  • #51

Closed
Open
Opened Oct 17, 2014 by André Anjos@andre.anjos💬
  • Report abuse
  • New issue
Report abuse New issue

Reset statistics if Experiment results are cached, but Experiment is reset from the admin interface

In the case the Experiment is reset from the admin interface, its cache files are not erased (they cannot since we don't know if they would be shared by other experiments). If the experiment is re-scheduled, the scheduler will not run a single block since all files are cached. When replying to the webserver, the scheduler will indicate successful completion, but no statistics, stdout or stderr will be present.

At this point, the web believes these are empty. Instead, it would be more correct if the backend would try to re-connect old statistics to the experiment instead.

Assignee
Assign to
Tutorial for the FG2015 Conference
Milestone
Tutorial for the FG2015 Conference
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: beat/beat.web#51