Occasional wrong values for some branches in snapshot'd file

Hi,

I’ve encountered that occasionally wrong values are stored for some branches for all the events in a file after taking a snapshot. It is reproducible in two different machines I’ve tried with different gcc versions. Making plot directly after Filter gives the correct answer, while making the plot byreading back from the snapshot’d filtered events gives wrong values. It doesn’t occur for all files. But when it does occur, all the events in a certain branch seems to get corrupted.

I’ve put a good ROOT file and a bad one with a simple script to illustrate the problem.
https://cernbox.cern.ch/index.php/s/O3Hi5DGmk9y1ltf

Regards,
Suyong


_ROOT Version: 6.15.01
_Platform: Linux
_Compiler: 6.4.1 or 4.8.5


Hi,
We fixed several issues in RDF in the last weeks, could you please try to reproduce the problem with the current master branch? (Either by recompiling or taking it from CVMFS).

Cheers,
Enrico

Hi Enrico,

The problem is still there in the latest master branch.
You can reproduce the problem using the files in https://cernbox.cern.ch/index.php/s/O3Hi5DGmk9y1ltf

Regards,
Suyong

Hi Suyong,
thank you very much, we will get back to you as soon as possible.

Cheers,
Enrico

Hi @Suyong_Choi,
I see the problem too, it’s most probably a bug on our side.

This is now bug report ROOT-9860, you can follow the progress towards resolution there. As you see it’s marked with very high priority, so it should be resolved soon.

Thank you very much for the report and the simple reproducer!

Cheers,
Enrico

Hi @Suyong_Choi, thanks to @Danilo the bug should now be fixed both on the current master branch and in the v6.16 branch (from which we will release v6.16 very soon).

It would be great if you could confirm that things work fine on your side now.

Cheers,
Enrico

Hi Enrico,

I checked out the master branch and am testing. I don’t see the problem any more for the problematic files. so far.

Regards,
Suyong

2 Likes

Thank you for the quick reply!
I will mark this as resolved, but do not hesitate to contact us should you encounter any further issue – or for any kind of feedback really.

Cheers,
Enrico

Thanks again Suyong for the detailed report and the responsiveness when it was time to test the fix, really appreciated!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.