Hi all, Currently we run all unit and answer tests on every push. Running answer testing, particularly with FLASH data, takes a long time. (Sidenote: FLASH in 2.x is particularly bad for large data objects, which answer testing does.) This will get worse once Orion and Chombo have been added. I think we're looking at up to 15 minutes per run. This has two effects: 1) Changes which break unit tests take longer to get reported. 2) We'll go through our ShiningPanda monthly allocation quite quickly. There are two solutions that I see: 1) Buy more time on ShiningPanda 2) Only run answer testing at most once a day, but still run unit tests on every push. My proposal is to go with #2 with the backup of #1 as needed. Can I get [+-]1 on this? -Matt
+1 on (2) On Thu, Feb 14, 2013 at 10:00 AM, Matthew Turk <matthewturk@gmail.com>wrote:
Hi all,
Currently we run all unit and answer tests on every push. Running answer testing, particularly with FLASH data, takes a long time. (Sidenote: FLASH in 2.x is particularly bad for large data objects, which answer testing does.) This will get worse once Orion and Chombo have been added. I think we're looking at up to 15 minutes per run. This has two effects:
1) Changes which break unit tests take longer to get reported. 2) We'll go through our ShiningPanda monthly allocation quite quickly.
There are two solutions that I see:
1) Buy more time on ShiningPanda 2) Only run answer testing at most once a day, but still run unit tests on every push.
My proposal is to go with #2 with the backup of #1 as needed. Can I get [+-]1 on this?
-Matt _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+1 on 2. On Feb 14, 2013 12:08 PM, "Sam Skillman" <samskillman@gmail.com> wrote:
+1 on (2)
On Thu, Feb 14, 2013 at 10:00 AM, Matthew Turk <matthewturk@gmail.com>wrote:
Hi all,
Currently we run all unit and answer tests on every push. Running answer testing, particularly with FLASH data, takes a long time. (Sidenote: FLASH in 2.x is particularly bad for large data objects, which answer testing does.) This will get worse once Orion and Chombo have been added. I think we're looking at up to 15 minutes per run. This has two effects:
1) Changes which break unit tests take longer to get reported. 2) We'll go through our ShiningPanda monthly allocation quite quickly.
There are two solutions that I see:
1) Buy more time on ShiningPanda 2) Only run answer testing at most once a day, but still run unit tests on every push.
My proposal is to go with #2 with the backup of #1 as needed. Can I get [+-]1 on this?
-Matt _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+1 on 2. On Thu, Feb 14, 2013 at 10:10 AM, Britton Smith <brittonsmith@gmail.com> wrote:
+1 on 2.
On Feb 14, 2013 12:08 PM, "Sam Skillman" <samskillman@gmail.com> wrote:
+1 on (2)
On Thu, Feb 14, 2013 at 10:00 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi all,
Currently we run all unit and answer tests on every push. Running answer testing, particularly with FLASH data, takes a long time. (Sidenote: FLASH in 2.x is particularly bad for large data objects, which answer testing does.) This will get worse once Orion and Chombo have been added. I think we're looking at up to 15 minutes per run. This has two effects:
1) Changes which break unit tests take longer to get reported. 2) We'll go through our ShiningPanda monthly allocation quite quickly.
There are two solutions that I see:
1) Buy more time on ShiningPanda 2) Only run answer testing at most once a day, but still run unit tests on every push.
My proposal is to go with #2 with the backup of #1 as needed. Can I get [+-]1 on this?
-Matt _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Stephen Skory s@skory.us http://stephenskory.com/ 510.621.3687 (google voice)
Hi all, Okay, Kacper has volunteered to run answer testing for us. With the FLASH tests, it takes 1:14 on the ShiningPanda instance, which is way too long even to do daily. So the new idea is epsilon different -- ShiningPanda will do a variety of builds, including 2.x, 3.0, etc -- but only unit tests, and still on every push. Kacper will handle answer testing, with whatever frequency he is comfortable. Thank you, Kacper! -Matt On Thu, Feb 14, 2013 at 12:32 PM, Stephen Skory <s@skory.us> wrote:
+1 on 2.
On Thu, Feb 14, 2013 at 10:10 AM, Britton Smith <brittonsmith@gmail.com> wrote:
+1 on 2.
On Feb 14, 2013 12:08 PM, "Sam Skillman" <samskillman@gmail.com> wrote:
+1 on (2)
On Thu, Feb 14, 2013 at 10:00 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi all,
Currently we run all unit and answer tests on every push. Running answer testing, particularly with FLASH data, takes a long time. (Sidenote: FLASH in 2.x is particularly bad for large data objects, which answer testing does.) This will get worse once Orion and Chombo have been added. I think we're looking at up to 15 minutes per run. This has two effects:
1) Changes which break unit tests take longer to get reported. 2) We'll go through our ShiningPanda monthly allocation quite quickly.
There are two solutions that I see:
1) Buy more time on ShiningPanda 2) Only run answer testing at most once a day, but still run unit tests on every push.
My proposal is to go with #2 with the backup of #1 as needed. Can I get [+-]1 on this?
-Matt _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Stephen Skory s@skory.us http://stephenskory.com/ 510.621.3687 (google voice) _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (4)
-
Britton Smith -
Matthew Turk -
Sam Skillman -
Stephen Skory