Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 14 16:25
    Snaipe commented #301
  • Sep 13 19:26
    Snaipe commented #302
  • Sep 13 19:21
    Snaipe commented #302
  • Sep 13 17:36
    MrAnno commented #301
  • Sep 13 17:35
    MrAnno commented #301
  • Sep 13 15:28
    kugel- commented #302
  • Sep 13 15:26
    kugel- commented #302
  • Sep 13 15:14
    Snaipe labeled #302
  • Sep 13 15:14
    Snaipe labeled #302
  • Sep 13 15:14
    Snaipe labeled #302
  • Sep 13 15:14
    Snaipe assigned #302
  • Sep 13 15:14
    Snaipe opened #302
  • Sep 13 14:55

    Snaipe on actions

    ci: setup basic actions yaml (compare)

  • Sep 11 08:33
    MrAnno opened #301
  • Sep 03 18:13
    Fumesover closed #300
  • Sep 03 18:13
    Fumesover commented #300
  • Sep 03 18:02
    Fumesover edited #300
  • Sep 03 18:02
    Fumesover edited #300
  • Sep 03 17:32
    Fumesover opened #300
  • Aug 26 18:59
    4lph4-Ph4un closed #298
Dominik
@kaidowei
which (in almost all cases) makes no sense :(
Franklin Mathieu
@Snaipe
yeah, it's a shame
I think the idea was to have more detail in the "timestamp" field
but currently "timestamp" is not an information that is gathered in the stats
actually nevermind, there's no "timestamp_end", so "timestamp" in itself is useless to calculate the time spent
and in any case a timestamp is in seconds
so yeah, it's too bad.
Dominik
@kaidowei
meaning 0.001 is 1ms
Franklin Mathieu
@Snaipe
Oh, then that's perfect
I don't know why I remember it being an integer
I must have mixed it up with something else
so then round up to the millisecond
in any case it's the only sane measurement accross platforms, as some does not give precision up to nanoseconds
Dominik
@kaidowei
elapsed_time is already in ms?
Franklin Mathieu
@Snaipe
seconds
Dominik
@kaidowei
ah so, I don't have to do anything, cool
Franklin Mathieu
@Snaipe
yep
Dominik
@kaidowei
what does it contain, if the test crashed?
Franklin Mathieu
@Snaipe
0
because nothing gets reported after the crash
I ought to fix this someday
Dominik
@kaidowei
the time for a suite... do I have to calc that or is there already a function somewhere?
Franklin Mathieu
@Snaipe
no, you have to sum all the elapsed_times
Dominik
@kaidowei
best place for that?
Franklin Mathieu
@Snaipe
Dominik
@kaidowei
yeah... are there unittests for the xml io?
Franklin Mathieu
@Snaipe
there are no unit tests, but a bunch of system tests to validate the output in test/cram
if you want to regenerate the new tests outputs, simply call make cram_tests CRAM=-i
Dominik
@kaidowei
pullrequest to master or bleeding?
Franklin Mathieu
@Snaipe
bleeding
I'll roll this out for 2.3.0
Dominik
@kaidowei
are you currently on bleeding?
can you check for me, if the time is accounted correctly?
I have a sleep in my test and the time is still 0.00
with 2.2.1 it works
Franklin Mathieu
@Snaipe
mmh, right. Times aren't reported on bleeding for some reason
let me investigate
oh, right, I remember why
that's because the protocol started working with timestamps rather than elapsed times
and currently timestamps aren't implemented
I ought to make an issue so I don't forget
Dominik
@kaidowei
can you elaborate on the cram tests? can't get them to run
Franklin Mathieu
@Snaipe
they run alongside everything else when running ctest
if ctest does nothing, then you probably have to run cmake -DCTESTS=ON -DDEV_BUILD=ON .. from your build directory
Dominik
@kaidowei
ah, I don't know cmake, so I didn't know about ctest
they're running now
where can I see the results of the cram test?
it just says, it failed
Franklin Mathieu
@Snaipe
oh, right, I'm assuming you don't have cram installed on your system