Re: [MTT users] Database submit error
Short Version: -- I just finished the fix, and the submit script is back up and running. This was a bug that arose in testing, but somehow did not get propagated to the production database. Long Version: - The new databases uses partition tables to archive test results. As part of this there are some complex rules to mask the partition table complexity from the users of the db. There was a bug in the insert rule in which the 'id' of the submitted result (mpi_install, test_build, and test_run) was a different value than expected since the 'id' was not translated properly to the partition table setup. The fix was to drop all rules and replace them with the correct versions. The submit errors you saw below were caused by integrity checks in the submit script that keep data from being submitted that do not have a proper lineage (e.g., you cannot submit a test_run without having submitted a test_build and an mpi_install result). The bug caused the client and the server to become confused on what the proper 'id' should be and when the submit script attempted to 'guess' the correct run it was unsuccessful and errored out. So sorry this bug lived this long, but it should be fixed now. -- Josh On Aug 28, 2007, at 10:16 AM, Jeff Squyres wrote: Josh found the problem and is in the process of fixing it. DB submits are currently disabled while Josh is working on the fix. More specific details coming soon. Unfortunately, it looks like all data from last night will be junk. :-( You might as well kill any MTT scripts that are still running from last night. On Aug 28, 2007, at 9:14 AM, Jeff Squyres wrote: Josh and I are investigating -- the total runs in the db in the summary report from this morning is far too low. :-( On Aug 28, 2007, at 9:13 AM, Tim Prins wrote: It installed and the tests built and made it into the database: http://www.open-mpi.org/mtt/reporter.php?do_redir=293 Tim Jeff Squyres wrote: Did you get a correct MPI install section for mpich2? On Aug 28, 2007, at 9:05 AM, Tim Prins wrote: Hi all, I am working with the jms branch, and when trying to use mpich2, I get the following submit error: *** WARNING: MTTDatabase server notice: mpi_install_section_name is not in mtt database. MTTDatabase server notice: number_of_results is not in mtt database. MTTDatabase server notice: phase is not in mtt database. MTTDatabase server notice: test_type is not in mtt database. MTTDatabase server notice: test_build_section_name is not in mtt database. MTTDatabase server notice: variant is not in mtt database. MTTDatabase server notice: command is not in mtt database. MTTDatabase server notice: fields is not in mtt database. MTTDatabase server notice: resource_manager is not in mtt database. MTT submission for test run MTTDatabase server notice: Invalid test_build_id (47368) given. Guessing that it should be -1 MTTDatabase server error: ERROR: Unable to find a test_build to associate with this test_run. MTTDatabase abort: (Tried to send HTTP error) 400 MTTDatabase abort: No test_build associated with this test_run *** WARNING: MTTDatabase did not get a serial; phases will be isolated from each other in the reports Reported to MTTDatabase: 1 successful submit, 0 failed submits (total of 12 results) This happens for each test run section. Thanks, Tim ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users -- Jeff Squyres Cisco Systems ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users -- Jeff Squyres Cisco Systems ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
Re: [MTT users] Please, forward this question to open-mpi developers
On Aug 28, 2007, at 4:15 AM, Shai Venter wrote: Hi guys, Ive found that when entering "./ompi_info --param oob tcp" for help on the oob, I see this: MCA oob: parameter "oob_tcp_include" (current value: ) MCA oob: parameter "oob_tcp_exclude" (current value: ) Should'nt it be oob_tcp_if_include , oob_tcp_if_exclude ? This question is better suited for the OMPI user's list (http:// www.open-mpi.org/mailman/listinfo.cgi/users). See http://www.open-mpi.org/faq/?category=tcp#tcp-selection -- we know they're named inconsistently and have fixed them in the both the trunk (what will eventually become v1.3) and the v1.2 branch such that oob_tcp_include and oob_tcp_if_include are synonyms (similar for exclude). I don't remember exactly when the fix went in to the v1.2 branch, whether it is starting with what will become 1.2.4 or before that. -- Jeff Squyres Cisco Systems
Re: [MTT users] Database submit error
Josh found the problem and is in the process of fixing it. DB submits are currently disabled while Josh is working on the fix. More specific details coming soon. Unfortunately, it looks like all data from last night will be junk. :-( You might as well kill any MTT scripts that are still running from last night. On Aug 28, 2007, at 9:14 AM, Jeff Squyres wrote: Josh and I are investigating -- the total runs in the db in the summary report from this morning is far too low. :-( On Aug 28, 2007, at 9:13 AM, Tim Prins wrote: It installed and the tests built and made it into the database: http://www.open-mpi.org/mtt/reporter.php?do_redir=293 Tim Jeff Squyres wrote: Did you get a correct MPI install section for mpich2? On Aug 28, 2007, at 9:05 AM, Tim Prins wrote: Hi all, I am working with the jms branch, and when trying to use mpich2, I get the following submit error: *** WARNING: MTTDatabase server notice: mpi_install_section_name is not in mtt database. MTTDatabase server notice: number_of_results is not in mtt database. MTTDatabase server notice: phase is not in mtt database. MTTDatabase server notice: test_type is not in mtt database. MTTDatabase server notice: test_build_section_name is not in mtt database. MTTDatabase server notice: variant is not in mtt database. MTTDatabase server notice: command is not in mtt database. MTTDatabase server notice: fields is not in mtt database. MTTDatabase server notice: resource_manager is not in mtt database. MTT submission for test run MTTDatabase server notice: Invalid test_build_id (47368) given. Guessing that it should be -1 MTTDatabase server error: ERROR: Unable to find a test_build to associate with this test_run. MTTDatabase abort: (Tried to send HTTP error) 400 MTTDatabase abort: No test_build associated with this test_run *** WARNING: MTTDatabase did not get a serial; phases will be isolated from each other in the reports Reported to MTTDatabase: 1 successful submit, 0 failed submits (total of 12 results) This happens for each test run section. Thanks, Tim ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users -- Jeff Squyres Cisco Systems ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users -- Jeff Squyres Cisco Systems
Re: [MTT users] Database submit error
Josh and I are investigating -- the total runs in the db in the summary report from this morning is far too low. :-( On Aug 28, 2007, at 9:13 AM, Tim Prins wrote: It installed and the tests built and made it into the database: http://www.open-mpi.org/mtt/reporter.php?do_redir=293 Tim Jeff Squyres wrote: Did you get a correct MPI install section for mpich2? On Aug 28, 2007, at 9:05 AM, Tim Prins wrote: Hi all, I am working with the jms branch, and when trying to use mpich2, I get the following submit error: *** WARNING: MTTDatabase server notice: mpi_install_section_name is not in mtt database. MTTDatabase server notice: number_of_results is not in mtt database. MTTDatabase server notice: phase is not in mtt database. MTTDatabase server notice: test_type is not in mtt database. MTTDatabase server notice: test_build_section_name is not in mtt database. MTTDatabase server notice: variant is not in mtt database. MTTDatabase server notice: command is not in mtt database. MTTDatabase server notice: fields is not in mtt database. MTTDatabase server notice: resource_manager is not in mtt database. MTT submission for test run MTTDatabase server notice: Invalid test_build_id (47368) given. Guessing that it should be -1 MTTDatabase server error: ERROR: Unable to find a test_build to associate with this test_run. MTTDatabase abort: (Tried to send HTTP error) 400 MTTDatabase abort: No test_build associated with this test_run *** WARNING: MTTDatabase did not get a serial; phases will be isolated from each other in the reports Reported to MTTDatabase: 1 successful submit, 0 failed submits (total of 12 results) This happens for each test run section. Thanks, Tim ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users -- Jeff Squyres Cisco Systems
Re: [MTT users] Database submit error
It installed and the tests built and made it into the database: http://www.open-mpi.org/mtt/reporter.php?do_redir=293 Tim Jeff Squyres wrote: Did you get a correct MPI install section for mpich2? On Aug 28, 2007, at 9:05 AM, Tim Prins wrote: Hi all, I am working with the jms branch, and when trying to use mpich2, I get the following submit error: *** WARNING: MTTDatabase server notice: mpi_install_section_name is not in mtt database. MTTDatabase server notice: number_of_results is not in mtt database. MTTDatabase server notice: phase is not in mtt database. MTTDatabase server notice: test_type is not in mtt database. MTTDatabase server notice: test_build_section_name is not in mtt database. MTTDatabase server notice: variant is not in mtt database. MTTDatabase server notice: command is not in mtt database. MTTDatabase server notice: fields is not in mtt database. MTTDatabase server notice: resource_manager is not in mtt database. MTT submission for test run MTTDatabase server notice: Invalid test_build_id (47368) given. Guessing that it should be -1 MTTDatabase server error: ERROR: Unable to find a test_build to associate with this test_run. MTTDatabase abort: (Tried to send HTTP error) 400 MTTDatabase abort: No test_build associated with this test_run *** WARNING: MTTDatabase did not get a serial; phases will be isolated from each other in the reports Reported to MTTDatabase: 1 successful submit, 0 failed submits (total of 12 results) This happens for each test run section. Thanks, Tim ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
Re: [MTT users] Database submit error
Did you get a correct MPI install section for mpich2? On Aug 28, 2007, at 9:05 AM, Tim Prins wrote: Hi all, I am working with the jms branch, and when trying to use mpich2, I get the following submit error: *** WARNING: MTTDatabase server notice: mpi_install_section_name is not in mtt database. MTTDatabase server notice: number_of_results is not in mtt database. MTTDatabase server notice: phase is not in mtt database. MTTDatabase server notice: test_type is not in mtt database. MTTDatabase server notice: test_build_section_name is not in mtt database. MTTDatabase server notice: variant is not in mtt database. MTTDatabase server notice: command is not in mtt database. MTTDatabase server notice: fields is not in mtt database. MTTDatabase server notice: resource_manager is not in mtt database. MTT submission for test run MTTDatabase server notice: Invalid test_build_id (47368) given. Guessing that it should be -1 MTTDatabase server error: ERROR: Unable to find a test_build to associate with this test_run. MTTDatabase abort: (Tried to send HTTP error) 400 MTTDatabase abort: No test_build associated with this test_run *** WARNING: MTTDatabase did not get a serial; phases will be isolated from each other in the reports Reported to MTTDatabase: 1 successful submit, 0 failed submits (total of 12 results) This happens for each test run section. Thanks, Tim ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users -- Jeff Squyres Cisco Systems
[MTT users] Database submit error
Hi all, I am working with the jms branch, and when trying to use mpich2, I get the following submit error: *** WARNING: MTTDatabase server notice: mpi_install_section_name is not in mtt database. MTTDatabase server notice: number_of_results is not in mtt database. MTTDatabase server notice: phase is not in mtt database. MTTDatabase server notice: test_type is not in mtt database. MTTDatabase server notice: test_build_section_name is not in mtt database. MTTDatabase server notice: variant is not in mtt database. MTTDatabase server notice: command is not in mtt database. MTTDatabase server notice: fields is not in mtt database. MTTDatabase server notice: resource_manager is not in mtt database. MTT submission for test run MTTDatabase server notice: Invalid test_build_id (47368) given. Guessing that it should be -1 MTTDatabase server error: ERROR: Unable to find a test_build to associate with this test_run. MTTDatabase abort: (Tried to send HTTP error) 400 MTTDatabase abort: No test_build associated with this test_run *** WARNING: MTTDatabase did not get a serial; phases will be isolated from each other in the reports >> Reported to MTTDatabase: 1 successful submit, 0 failed submits (total of 12 results) This happens for each test run section. Thanks, Tim
[MTT users] Please, forward this question to open-mpi developers
Hi guys, Ive found that when entering "./ompi_info --param oob tcp" for help on the oob, I see this: MCA oob: parameter "oob_tcp_include" (current value: ) MCA oob: parameter "oob_tcp_exclude" (current value: ) Should'nt it be oob_tcp_if_include , oob_tcp_if_exclude ? Regards, Shai Venter. -Original Message- From: mtt-users-boun...@open-mpi.org [mailto:mtt-users-boun...@open-mpi.org] On Behalf Of mtt-users-requ...@open-mpi.org Sent: Saturday, August 25, 2007 7:00 PM To: mtt-us...@open-mpi.org Subject: mtt-users Digest, Vol 18, Issue 3 Send mtt-users mailing list submissions to mtt-us...@open-mpi.org To subscribe or unsubscribe via the World Wide Web, visit http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users or, via email, send a message with subject or body 'help' to mtt-users-requ...@open-mpi.org You can reach the person managing the list at mtt-users-ow...@open-mpi.org When replying, please edit your Subject line so it is more specific than "Re: Contents of mtt-users digest..." Today's Topics: 1. MTT Database and Reporter Upgrade **Action Required** (Josh Hursey) -- Message: 1 List-Post: mtt-users@lists.open-mpi.org Date: Fri, 24 Aug 2007 13:37:18 -0400 From: Josh Hursey Subject: [MTT users] MTT Database and Reporter Upgrade **Action Required** To: General user list for the MPI Testing Tool Message-ID: <58b351f2-6879-42b9-b44b-079a1badf...@open-mpi.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Short Version: -- The MTT development group is rolling out newly optimized web frontend and backend database. As a result we will be taking down the MTT site at IU Monday, August 27 from 8 am to Noon US eastern time. During this time you will not be able to submit data to the MTT database. Therefore you need to disable any runs that will report during this time or your client will fail with unable to connect to server messages. This change does not affect the client configurations, so MTT users do *not* need to update their clients at this time. Longer Version: --- The MTT development team has been working diligently on server side optimizations over the past few months. This work involved major changes to the database schema, web reporter, and web submit components of the server. We want to roll out the new server side optimizations on Monday, Aug. 27. Given the extensive nature of the improvements the MTT server will need to be taken down for a few hours for this upgrade to take place. We are planning on taking down the MTT server at 8 am and we hope to have it back by Noon US Eastern time. MTT users that would normally submit results during this time range will need to disable their runs, or they will see server error messages during this outage. This upgrade does not require any client changes, so outside of the down time contributors need not change or upgrade their MTT installations. Below are a few rough performance numbers illustrating the difference between the old and new server versions as seen by the reporter. Summary report: 24 hours, all orgs 87 sec - old version 6 sec - new version Summary report: 24 hours, org = 'iu' 37 sec - old 4 sec - new Summary report: Past 3 days, all orgs 138 sec - old 9 sec - new Summary report: Past 3 days, org = 'iu' 49 sec - old 11 sec - new Summary report: Past 2 weeks, all orgs 863 sec - old 34 sec - new Summary report: Past 2 weeks, org = 'iu' 878 sec - old 12 sec - new Summary report: Past 1 month, all org 1395 sec - old 158 sec - new Summary report: Past 1 month, org = 'iu' 1069 sec - old 39 sec - new Summary report: (2007-06-18 - 2007-06-19), all org 484 sec - old 5 sec - new Summary report: (2007-06-18 - 2007-06-19), org = 'iu' 479 sec - old 2 sec - new -- ___ mtt-users mailing list mtt-us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users End of mtt-users Digest, Vol 18, Issue 3
