Ticket #7164 (closed: fixed)
An issue with LoadEventNexus
Reported by: | Roman Tolchenov | Owned by: | Federico M Pouzols |
---|---|---|---|
Priority: | major | Milestone: | Release 3.4 |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Dan Nixon |
Description (last modified by Federico M Pouzols) (diff)
From Pascal:
I am looking at file 62430 which is an event file. When I time-slice it, I get the same results (same stats and the file is of the same size). I have just tried on a WISH file and I get the same issue.
It is just that you have to have the LoadLogs box (in LoadEventNexus alg) ticked otherwise it doesn;t slice but it doesn;t warn you of anything.
Change History
comment:1 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
- Owner set to Anyone
- Priority changed from minor to major
comment:4 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to backlog at the code freeze for R2.6
comment:5 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step
comment:6 Changed 6 years ago by Federico M Pouzols
- Description modified (diff)
I was looking at this but couldn't exactly reproduce the problem. Could you provide more details on how to reproduce the issue? For example, what's that 62430 file?
It seems that TimeSclice is quite uninformative about errors in general. For example, there's no error or warning message for missing or broken files.
comment:8 Changed 6 years ago by Federico M Pouzols
- Owner changed from Anyone to Federico M Pouzols
- Status changed from assigned to verify
- Resolution set to invalid
Great, closing it as 'invalid' / 'not anymore'
comment:9 Changed 6 years ago by Dan Nixon
- Status changed from verify to verifying
- Tester set to Dan Nixon
comment:11 Changed 6 years ago by Nick Draper
- Milestone changed from Backlog to Release 3.4
moved to r 3.4 as tickets are closed
comment:12 Changed 5 years ago by Nick Draper
- Resolution changed from invalid to fixed
Somehow these slipped through without a resolution. Set to Fixed.
comment:13 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 8010