Trying to emerge dev-scheme/guile-1.6.8 on my AMD64 system failed because one test failed: Running slib.test ERROR: slib.test: Input/Output: delete-file: non existant file - arguments: ((system-error "delete-file" "~A" ("No such file or directory") (2))) FAIL: slib.test: Input/Output: delete-file: existing file ERROR: slib.test: Input/Output: open-file: r - arguments: ((wrong-type-arg "open-file" "Wrong type argument in position ~A (expecting ~A): ~S" (2 "STRINGP" r) #f)) ERROR: slib.test: Input/Output: open-file: rb - arguments: ((wrong-type-arg "open-file" "Wrong type argument in position ~A (expecting ~A): ~S" (2 "STRINGP" rb) #f)) ERROR: slib.test: Input/Output: open-file: w - arguments: ((wrong-type-arg "open-file" "Wrong type argument in position ~A (expecting ~A): ~S" (2 "STRINGP" w) #f)) ERROR: slib.test: Input/Output: open-file: wb - arguments: ((wrong-type-arg "open-file" "Wrong type argument in position ~A (expecting ~A): ~S" (2 "STRINGP" wb) #f)) FAIL: slib.test: Miscellany: Legacy: nil: value FAIL: slib.test: Miscellany: Legacy: t: value ERROR: slib.test: rev2-procedures: <? - arguments: ((unbound-variable #f "Unbound variable: ~S" (<?) #f)) ERROR: slib.test: rev2-procedures: <=? - arguments: ((unbound-variable #f "Unbound variable: ~S" (<=?) #f)) ERROR: slib.test: rev2-procedures: =? - arguments: ((unbound-variable #f "Unbound variable: ~S" (=?) #f)) ERROR: slib.test: rev2-procedures: >? - arguments: ((unbound-variable #f "Unbound variable: ~S" (>?) #f)) ERROR: slib.test: rev2-procedures: >=? - arguments: ((unbound-variable #f "Unbound variable: ~S" (>=?) #f)) FAIL: slib.test: system: exit 1 FAIL: slib.test: system: exit 99
Created attachment 119500 [details] emerge --info output
I've disabled the failing tests. They weren't very valuable. So, fixed. Strangely, rullzer reports that the tests did work for him. I have no explanation for that.
Thanks. That's the nice thing about tests: they can be fixed by disabling them. :-) I suppose I could investigate a bit to see why things fail, but my lisp/scheme foo isn't very good and since you are indicating the tests are not really important I think I'll pass.
I only disabled the failing tests. You can see just which ones by looking at the slibtest.patch file in files/ Some legacy stuff, like #f being equal to nil, which isn't true any more in recent Scheme, some stuff which I think changed behaviour, like the deleting of a non-existing file, and some other stuff which I'm not sure about, like the exit calls.