Opened 14 years ago

Last modified 7 years ago

#22645 assigned defect

taskjuggler @2.4.3_3 build failure: Task 'project1.task1' needs a start specification to be scheduled in ASAP mode in the 'plan' scenario.

Reported by: borschel@… Owned by:
Priority: Normal Milestone:
Component: ports Version: 1.8.1
Keywords: Cc: mikesanders5@…
Port: taskjuggler

Description (last modified by mf2k (Frank Schima))

I don't know why it fails. My MacPorts is up to date at version 1.8.1 and I also did an upgrade outdated. I then completely removed all kde related stuff so that it would be re-installed from fetch. But that didn't help either.

Apparently all build and test stages are fine, but at the end it doesn't get installed because of

make: *** [all] Error 2
while executing
"command_exec build"
    (procedure "portbuild::build_main" line 9)
    invoked from within
"$procedure $targetname"

I attached the full debug output.

Attachments (1)

TaskJuggler-debug.txt (2.9 KB) - added by borschel@… 14 years ago.

Download all attachments as: .zip

Change History (9)

Changed 14 years ago by borschel@…

Attachment: TaskJuggler-debug.txt added

comment:1 Changed 14 years ago by mf2k (Frank Schima)

Description: modified (diff)
Owner: changed from macports-tickets@… to rene@…
Port: taskjuggler added

comment:2 Changed 14 years ago by france.baril@…

I too, have the same error with Leopard Snow and MacPort 1.8.1… but I seem to have extra details as to why it failed:

--

--->  Building taskjuggler
DEBUG: Executing org.macports.build (taskjuggler)
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.6' MAKEFLAGS='-j2'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3" && /usr/bin/make -j2 all DYLD_LIBRARY_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/taskjuggler/.libs'
/usr/bin/make  all-recursive
Making all in taskjuggler
make[2]: Nothing to be done for `all'.
Making all in Contrib
Making all in kate
make[3]: Nothing to be done for `all'.
make[3]: Nothing to be done for `all-am'.
Making all in Examples
Making all in FirstProject
make[3]: Nothing to be done for `all'.
Making all in BigProject
Making all in Common
make[4]: Nothing to be done for `all'.
Making all in Project1
make[4]: Nothing to be done for `all'.
Making all in Project2
../../../taskjuggler/taskjuggler --debug 1 Project2.tjp
TaskJuggler v2.4.3 - A Project Management Software
Processing file '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/Examples/BigProject/Project2/Project2.tjp'
Processing file '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/Examples/BigProject/Common/Resources.tji'
Processing file '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/Examples/BigProject/Project1/Project1-Interface.tji'
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/Examples/BigProject/Project1/Project1-Interface.tji:12: Date 2002-01-15-23:00:00--0500 is outside of project time frame (2002-01-16-00:00:00--0500 - 2002-06-29-23:59:59--0500)
    plan:start 2002-01-16-00:00:00--0500
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/Examples/BigProject/Project1/Project1-Interface.tji:11: Task 'project1.task1' needs a start specification to be scheduled in ASAP mode in the 'plan' scenario.
make[4]: *** [Project2.html] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3" && /usr/bin/make -j2 all DYLD_LIBRARY_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/taskjuggler/.libs " returned error 2
DEBUG: Backtrace: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3" && /usr/bin/make -j2 all DYLD_LIBRARY_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/taskjuggler-2.4.3/taskjuggler/.libs " returned error 2
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 9)
    invoked from within
"$procedure $targetname"
Warning: the following items did not execute (for taskjuggler): org.macports.activate org.macports.build org.macports.destroot org.macports.install
Error: Status 1 encountered during processing.

--

I also noticed in the bug list a note about -j2 not being supported, but it was striked, so I have a feeling it should have been resolved.

Thanks!

comment:3 in reply to:  2 Changed 14 years ago by rene@…

Status: newassigned

It looks like the test is failing for some reason. TaskJuggler schedules its examples during the test phase and the error you got is simply an error from the taskjuggler scheduler:

Examples/BigProject/Project1/Project1-Interface.tji:12: Date 2002-01-15-23:00:00--0500 is outside of project time frame

I am not sure why this is happening and I cannot reproduce it here. Does the problem still exist?

comment:4 Changed 13 years ago by jmroot (Joshua Root)

Resolution: worksforme
Status: assignedclosed

No response; closing as per comment:3.

comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: mikesanders5@… added
Resolution: worksforme
Status: closedreopened
Summary: port install taskjuggler failstaskjuggler: Task 'project1.task1' needs a start specification to be scheduled in ASAP mode in the 'plan' scenario.

Re-opening per duplicate #29272.

comment:6 in reply to:  5 Changed 13 years ago by mikesanders5@…

Replying to ryandesign@…:

Re-opening per duplicate #29272.

I got this to install by tweaking the Project1-Interface.tji file. Basically, I had to remove task dependencies and the supplemental shift assignments. This doesn't make for a great example for beginners of this software, however it will build. The examples end up going into a very obscure location anyway, /opt/local/var/macports/software/taskjuggler/2.4.3_3/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_office_taskjuggler/work/destroot/share/doc

Here is the resulting Project1-Interface.tji file that I used.

/*
 * This file has been generated by TaskJuggler 2.4.3
 * at 2011-04-25 21:48:56 CDT.
 */
/*
 * For details about TaskJuggler see http://www.taskjuggler.org
 */
projectids project1
task project1 "First Project" {
  scheduling asap 
  projectid project1
  task task1 "Task 1" {
    plan:start 2002-01-17
    plan:end 2002-02-12-18:00:00--0500
    plan:scheduled
  }
  task task2 "Task 2" {
    plan:start 2002-02-13-09:00:00--0500
    plan:end 2002-03-05-18:00:00--0500
    plan:scheduled
  }
  task task3 "Task 3" {
    plan:start 2002-03-06-09:00:00--0500
    plan:end 2002-03-26-18:00:00--0500
    plan:scheduled
  }
}
flags interface
supplement task project1 {
  supplement task task1 {
  }
  supplement task task2 {
    purge flags
    flags interface
  }
  supplement task task3 {
  }
}

comment:7 Changed 9 years ago by jmroot (Joshua Root)

Summary: taskjuggler: Task 'project1.task1' needs a start specification to be scheduled in ASAP mode in the 'plan' scenario.taskjuggler @2.4.3_3 build failure: Task 'project1.task1' needs a start specification to be scheduled in ASAP mode in the 'plan' scenario.

Still a problem with version 3.5.0?

comment:8 Changed 7 years ago by kurthindenburg (Kurt Hindenburg)

Owner: rene@… deleted
Status: reopenedassigned
Note: See TracTickets for help on using tickets.