Re: [asdf-devel] Please test before releasing ASDF 3.0.0 - Also, resigning again

2013-04-30 Thread Stas Boukarev
Faré fah...@gmail.com writes:

 Dear Lisp hackers,

 I'd like to release ASDF 3.0 next week (maybe even later this week).
 Can you test ASDF before I do?
I get asdf-pathname-test.script failure on SBCL:

These two expressions yield paths that are not pathname-equal
the first expression (RESOLVE-LOCATION '(/foo bar baz)) yields this:
  #P/bar/baz
  (:HOST #SB-IMPL::UNIX-HOST {100023F223} :DEVICE NIL :DIRECTORY
   (:ABSOLUTE bar) :NAME baz :TYPE :UNSPECIFIC :VERSION NIL)

the other expression #P/foo/bar/baz yields that:
  #P/foo/bar/baz
  (:HOST #SB-IMPL::UNIX-HOST {100023F223} :DEVICE NIL :DIRECTORY
   (:ABSOLUTE foo bar) :NAME baz :TYPE NIL :VERSION :NEWEST)

-- 
With best regards, Stas.



Re: [asdf-devel] Please test before releasing ASDF 3.0.0 - Also, resigning again

2013-04-30 Thread Stas Boukarev
Faré fah...@gmail.com writes:

 Works for me. Weird. Which version of SBCL are you using?
1.1.6.14-76e4485

-- 
With best regards, Stas.



Re: [asdf-devel] Please test before releasing ASDF 3.0.0 - Also, resigning again

2013-04-30 Thread Stas Boukarev
Faré fah...@gmail.com writes:

 Works for me. Weird. Which version of SBCL are you using?
I also have a file /foo, if that matters.

-- 
With best regards, Stas.



Re: [asdf-devel] Please test before releasing ASDF 3.0.0 - Also, resigning again

2013-04-30 Thread Faré
On Tue, Apr 30, 2013 at 10:30 AM, Stas Boukarev stass...@gmail.com wrote:

 I also have a file /foo, if that m

Yes, that probably matters. I don't remember exactly how things go,
but I believe that what's going on is that ASDF by default gets
truenames at every step, which causes this behaviour. I suppose it
should rather error out, expecting a directory pathname, than give
this answer.

Also, this particular test should probably disable the truename resolution.

—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
Fascists divide in two categories: the fascists and the anti-fascists
— Ennio Flaiano



Re: [asdf-devel] Please test before releasing ASDF 3.0.0 - Also, resigning again

2013-04-30 Thread Faré
This is bug worthy. Dunno that I have the courage to fix it before
3.0.0. Maybe a good target for procrastination, though.

—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
You can tell whether a man is clever by his answers.
You can tell whether a man is wise by his questions. — Naguib Mahfouz


On Tue, Apr 30, 2013 at 10:40 AM, Stas Boukarev stass...@gmail.com wrote:
 Faré fah...@gmail.com writes:

 On Tue, Apr 30, 2013 at 10:30 AM, Stas Boukarev stass...@gmail.com wrote:

 I also have a file /foo, if that m

 Yes, that probably matters. I don't remember exactly how things go,
 but I believe that what's going on is that ASDF by default gets
 truenames at every step, which causes this behaviour. I suppose it
 should rather error out, expecting a directory pathname, than give
 this answer.

 Also, this particular test should probably disable the truename resolution.
 Removing that file results in successful execution of tests.

 --
 With best regards, Stas.



Re: [asdf-devel] Please test before releasing ASDF 3.0.0 - Also, resigning again

2013-04-30 Thread Juan Jose Garcia-Ripoll
Faré, your code is not valid in ECL because ECL does not support to use
run-program with output to text strings. This is not a bug but something
that would involve some major redesign of the function we have.


On Tue, Apr 30, 2013 at 2:52 AM, Faré fah...@gmail.com wrote:

 I believe this is a bug in ECL.

 Its can be reproduced this way:

 (in-package :asdf)
 (let ((ok1 (format nil ; $ echo ok 1~%ok 1~%)))
   (assert-equal
(with-output-to-string (s)
  (let ((*verbose-out* t)
(*standard-output* s))
(run-shell-command echo ok ~D 1)))
ok1))

 Or more simply this way:
 (with-output-to-string (*standard-output*) (uiop:RUN-PROGRAM echo ok
 1 :FORCE-SHELL T :IGNORE-ERROR-STATUS T :OUTPUT T))

 I've commented out this test for ECL.

 Thanks for the bug report!

 —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics•
 http://fare.tunes.org
 In a five year period we can get one superb programming language.
 Only we can't control when the five year period will begin. — Alan Perlis


 On Mon, Apr 29, 2013 at 6:43 PM, Robert Goldman rpgold...@sift.info
 wrote:
  On ECL 12.12.1 on Mac OSX, test-run-program.script failed for me:
 
  ;;; Loading /Users/rpg/lisp/asdf/test/script-support.lisp
  ;;; Loading /Users/rpg/lisp/asdf/build/fasls/ecl/asdf.fas
  Configuring ASDF
  Enabling debugging
  Being a bit verbose
  Comparing directories
  ASDF-TEST:*TEST-DIRECTORY* and ASDF-TEST::X both evaluate to same path:
#P/Users/rpg/lisp/asdf/test/
  Frob packages
 
  Internal or unrecoverable error in:
  illegal stream mode
[2: No such file or directory]
 
  ;;; ECL C Backtrace
  ;;; 0   libecl.12.12.dylib  0x00010e3b68e4
  si_dump_c_backtrace + 52
  ;;; 1   libecl.12.12.dylib  0x00010e3a7721
  ecl_internal_error + 113
  ;;; 2   libecl.12.12.dylib  0x00010e39abb4
  ecl_stream_to_handle + 148
  ;;; 3   libecl.12.12.dylib  0x00010e3dbc50
  si_run_program + 1168
  ;;; 4   libecl.12.12.dylib  0x00010e3641b3 si_system
  + 179
  ;;; 5   asdf.fas0x000111514e98
  LC359system + 440
  ;;; 6   asdf.fas0x0001115150db
  LC360call_system + 523
  ;;; 7   asdf.fas0x00011151552f
  LC361uiop_stream__think + 1023
  ;;; 8   asdf.fas0x00011153bdae
  L288call_with_temporary_file + 3182
  ;;; 9   asdf.fas0x000111515d96
  L363run_program + 1334
  ;;; 10  asdf.fas0x0001114e6356
  L849run_shell_command + 758
  ;;; 11  libecl.12.12.dylib  0x00010e373c25 APPLY +
 101
  ;;; 12  libecl.12.12.dylib  0x00010e38382c
  ecl_interpret + 9932
  ;;; 13  libecl.12.12.dylib  0x00010e38b21e eval_form
  + 350
  ;;; 14  libecl.12.12.dylib  0x00010e38b761
  si_eval_with_env + 1281
  ;;; 15  libecl.12.12.dylib  0x00010e3d89e9
  si_load_source + 409
  ;;; 16  libecl.12.12.dylib  0x00010e3d91f1 cl_load +
  1825
  ;;; 17  libecl.12.12.dylib  0x00010e373c10 APPLY + 80
  ;;; 18  libecl.12.12.dylib  0x00010e38382c
  ecl_interpret + 9932
  ;;; 19  libecl.12.12.dylib  0x00010e383c5e
  _ecl_bytecodes_dispatch_vararg + 350
  ;;; 20  asdf.fas0x00011153e767
  L472call_with_asdf_cache + 695
  ;;; 21  libecl.12.12.dylib  0x00010e373c10 APPLY + 80
  ;;; 22  libecl.12.12.dylib  0x00010e38382c
  ecl_interpret + 9932
  ;;; 23  libecl.12.12.dylib  0x00010e38385a
  ecl_interpret + 9978
  ;;; 24  libecl.12.12.dylib  0x00010e38b21e eval_form
  + 350
  ;;; 25  libecl.12.12.dylib  0x00010e386292
  compile_toplevel_body + 130
  ;;; 26  libecl.12.12.dylib  0x00010e389f18
  compile_form + 600
  ;;; 27  libecl.12.12.dylib  0x00010e38ae15
  compile_with_load_time_forms + 53
  ;;; 28  libecl.12.12.dylib  0x00010e38b1b9 eval_form
  + 249
  ;;; 29  libecl.12.12.dylib  0x00010e38b761
  si_eval_with_env + 1281
  ;;; 30  libecl.12.12.dylib  0x00010e380683 cl_eval +
 19
  ;;; 31  libecl.12.12.dylib  0x00010e3ab487 dispatch1
  + 39
  ./run-tests.sh: line 78: 85028 Abort trap: 6   $@
  + echo 'Using ecl, test-run-program.script failed'
  Using ecl, test-run-program.script failed
 




-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com