Dave,
I suggest opening a bug on (1). I think (2) is fixed in HEAD.
Greg On May 5, 2011, at 8:04 PM, Dave Wootton wrote: I ran a test of the PE and LoadLeveler
proxies. I was able to start the proxies, run PE applications and submit
LoadLeveler jobs. I did run into three problems
1) I intermittently get a popup when
I try to start a PE app telling me that the abstract resource manager could
not parse a message (I don't have the exact message since it occurred only
once and I didn't write it down) This is a problem I've seen before with
the PTP 5.0 code and suspect a problem with either the binary message protocol
or Huffman compression code. I asked my development team to look at this
a week or so ago when I saw it the first time.
2) I can create a resource manager and
specify a connection, etc for a brand new resource manager and have it
start correctly. If I edit a resource manager configuration, it's not saved.
I think this is the same problem I've seen discussion about on the mailing
list.
3) I found a problem where if I edit
a resource manager and try to change the path to the proxy executable,
the file selector dialog alternates between two behaviors. If I start with
a resource manager configuration that has a valid proxy path, after I hit
the browse button next to proxy path, I get a file selector dialog where
I see only the selected proxy filename even though there are three files
in the directory. If I select that file and click ok, then I get a red
X in the resource manager configuration dialog and an error message indicating
the path is invalid. If I hit browse again, the file selector dialog opens
in my home directory. If I navigate to the proxy executable and select
it, the resource configuration dialog has no red X and I can click finish/ok.
I made a change to the resource manager configuration dialog a week or
so ago to eliminate the 'Invalid path' message when the dialog was opened
for a new resource manager. I'm not sure I broke anything in that process.
Dave
From:
Beth Tibbitts/Watson/IBM@IBMUS
To:
ptp-dev@xxxxxxxxxxx
Date:
05/05/2011 02:05 PM
Subject:
[ptp-dev] Indigo
M7 EPP parallel package available for testing
Sent by:
ptp-dev-bounces@xxxxxxxxxxx
Please try the epp-parallel package.
See http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110505-1244/
and scroll down to find eclpse-parallel for your platform.
Local projects,pldt basics,build,run,debug work ok on brief smoke test.
About to test (old) remote projects.
Can somebody please test rsync projects and assure it works at least as
well as the non-packaged version of PTP?
Esp. if the jGit and jaxb parts are there.
I need to vote +1 on it being built ok then take off for the afternoon.
Thanks
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
----- Forwarded by Beth Tibbitts/Watson/IBM on 05/05/2011 02:01 PM -----
Well, there was something else important today... it is time to test and
to vote for the Indigo M7 build:
http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110505-1244/
Unfortunately we lost some packages in Indigo, but on the other hand there
are 3 new packages
- the Parallel Application Developers package (Bug 331589,
since some milestones)
- a Scout Developers package (Bug 340698)
and
- a Testing Package (Bug 344369)
Please
test the above build and send your +1/-1 vote to this mailing list by tomorrow
/ Friday.
Thanks,
Markus
(At the time of this writing, the Reporting, Scout, and Testing packages
are still building. They should be available soon.)_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-dev
|