Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export issues from cyclus/core to cyclus/modules repositories #9

Closed
katyhuff opened this issue Jul 11, 2012 · 2 comments
Closed

Export issues from cyclus/core to cyclus/modules repositories #9

katyhuff opened this issue Jul 11, 2012 · 2 comments

Comments

@katyhuff
Copy link
Member

This issue is a subpart of issue #37.

Make sure github issues are moved to any new repositories with which they are associated. (https://github.com/mkorenkov/tools/blob/master/gh-issues-import/gh-issues-import.py).

This issue is blocked by issue https://github.com/cyclus/core/issues/191 in which modules are moved into their own repositories.

Next Action : Decide whether it's okay to use the script to grab 27/37 issues (without comments) and port the rest over manually. If so, do that. Else, figure something else out.

@ghost ghost assigned katyhuff Jul 11, 2012
@katyhuff
Copy link
Member Author

This issue came from https://github.com/cyclus/core/issues/192 . Go there for previous comments.

It was originally opened by @katyhuff .

@katyhuff
Copy link
Member Author

Having moved all of the module related issues into this cycamore repository, that fixes #9 .

@gidden gidden mentioned this issue Dec 14, 2013
9 tasks
gidden pushed a commit to gidden/cycamore that referenced this issue Mar 17, 2014
…syntax.

Also, changes situations where comp().comp() occured to iso_vector_.comp(). The 
former (comp().comp()) threw errors in Material::clone() function testing
(added here). The latter does not throw such errors.  

For reference, a backtrace of the sort of errors the former 
threw follows (the 'identifier' in question is always different, btw):


[----------] 2 tests from MaterialTest
[ RUN      ] MaterialTest.Constructors
[       OK ] MaterialTest.Constructors (0 ms)
[ RUN      ] MaterialTest.Clone
terminate called after throwing an instance of 'CycRangeException'
  what():  cyclus exception: Isotope identifier '574365655' is not valid.

Program received signal SIGABRT, Aborted.
0x00007fff85dbc0b6 in __kill ()
(gdb) bt
#0  0x00007fff85dbc0b6 in __kill ()
#1  0x00007fff85e5c9f6 in abort ()
#2  0x00007fff87d7e5d2 in __gnu_cxx::__verbose_terminate_handler ()
#3  0x00007fff87d7cae1 in __cxxabiv1::__terminate ()
#4  0x00007fff87d7cb16 in std::terminate ()
#5  0x00007fff87d7cbfc in __cxa_throw ()
#6  0x0000000100084be1 in IsoVector::validateIsotopeNumber ()
#7  0x0000000100084d2d in IsoVector::atomCount ()
#8  0x000000010008949b in Material::checkQuality ()
cyclus#9  0x00000001000e6616 in MaterialTest_Clone_Test::TestBody ()
cyclus#10 0x000000010159b7dd in testing::Test::Run ()
cyclus#11 0x00000001015a246e in testing::internal::TestInfoImpl::Run ()
cyclus#12 0x00000001015a25a4 in testing::TestCase::Run ()
cyclus#13 0x00000001015a2872 in testing::internal::UnitTestImpl::RunAllTests ()
cyclus#14 0x00000001015a29e9 in testing::UnitTest::Run ()
cyclus#15 0x0000000100020130 in main ()
(gdb)
FlanFlanagan pushed a commit that referenced this issue Feb 28, 2019
Revert "Recordtimeseries storage with reactor "
gonuke pushed a commit that referenced this issue Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant