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

Pilots only have the final state #30

Open
iparask opened this issue Feb 10, 2017 · 6 comments
Open

Pilots only have the final state #30

iparask opened this issue Feb 10, 2017 · 6 comments
Labels

Comments

@iparask
Copy link

iparask commented Feb 10, 2017

Hello,

I am running some examples with Analytics and it does not seem to be able to get the pilot states. The example was run with the Devel branch of RP.

The stack used to run analytics is (based on @vivek-bala 's instruction):

(RadicalAnalytics)iparask@js-172-81:~/Repositories/RadicalPilotDevel/examples/work$ radical-stack
python            : 2.7.6
virtualenv        : /home/iparask/Virtualenv/RadicalAnalytics
radical.utils     : v0.44.RC1-11-ge108e90@experiment-aimes
saga-python       : 0.44
radical.pilot     : v0.40.1-244-gece2ed8@fix-legacy_profile_sync
radical.analytics : v0.1-186-g89bfbc0@experiment-aimes

When I try to run example 4 and reach the line I get this:

In [17]: pilots = session.filter(etype='pilot', inplace=False)

In [18]: pprint.pprint(pilots.get()[0])
ra.Entity [pilot]: pilot.0000
    states: ['FAILED']
    events: ['event']

How should I proceed?

@mturilli
Copy link
Contributor

Hi there :)

Just to confirm: did you download and made available also the json file of the session?

@iparask
Copy link
Author

iparask commented Feb 10, 2017 via email

@iparask
Copy link
Author

iparask commented Feb 10, 2017

This is how the folder tree looks like

└── rp.session.js-172-81.jetstream-cloud.org.iparask.017206.0001
    ├── pilot.0000
    │   ├── agent_0.AgentExecutingComponent.0.child.prof
    │   ├── agent_0.AgentExecutingComponent.0.prof
    │   ├── agent_0.AgentSchedulingComponent.0.child.prof
    │   ├── agent_0.AgentSchedulingComponent.0.prof
    │   ├── agent_0.AgentStagingInputComponent.0.child.prof
    │   ├── agent_0.AgentStagingInputComponent.0.prof
    │   ├── agent_0.AgentStagingOutputComponent.0.child.prof
    │   ├── agent_0.AgentStagingOutputComponent.0.prof
    │   ├── agent_0.AgentUpdateWorker.0.child.prof
    │   ├── agent_0.AgentUpdateWorker.0.prof
    │   ├── agent_0.AgentWorker.0.child.prof
    │   ├── agent_0.AgentWorker.0.prof
    │   ├── agent_0.bootstrap_3.prof
    │   ├── agent_0.Heartbeat.0.child.prof
    │   ├── agent_0.Heartbeat.0.prof
    │   ├── bootstrap_1.prof
    │   └── pilot.0000.prof.tgz
    ├── rp.session.js-172-81.jetstream-cloud.org.iparask.017206.0001.json
    └── rp.session.js-172-81.jetstream-cloud.org.iparask.017206.0001.prof

@andre-merzky
Copy link
Member

That structure looks good. Can you make the files available, please?

@iparask
Copy link
Author

iparask commented Feb 10, 2017

analytics_test.tar.gz

@ibethune ibethune added this to the 0.46 milestone Mar 2, 2017
@andre-merzky andre-merzky modified the milestones: v0.47, 0.46 Aug 24, 2017
@andre-merzky
Copy link
Member

This should be fixed by now (in RP), but needs confirmation in RA.

@andre-merzky andre-merzky self-assigned this Aug 24, 2017
@andre-merzky andre-merzky removed their assignment Apr 3, 2019
@mturilli mturilli removed the bug label Jun 5, 2019
@mturilli mturilli removed this from the v0.47 milestone Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants