ChanServ changed the topic of #crystal-lang to: The Crystal programming language | | Fund Crystal's development: | GH: | Docs: | Gitter:
ur5us has quit [Ping timeout: 260 seconds]
brw has quit [*.net *.split]
kevinsjoberg has quit [*.net *.split]
hexology has quit [*.net *.split]
kevinsjoberg has joined #crystal-lang
brw has joined #crystal-lang
hexology has joined #crystal-lang
jhass[m] has quit [*.net *.split]
SamantazFox has quit [*.net *.split]
SamantazFox has joined #crystal-lang
jhass[m] has joined #crystal-lang
ur5us has joined #crystal-lang
hightower2 has joined #crystal-lang
ur5us has quit [Ping timeout: 260 seconds]
hightower2 has quit [Ping timeout: 268 seconds]
hightower3 has joined #crystal-lang
hightower3 has quit [Ping timeout: 268 seconds]
Guest8553 has joined #crystal-lang
hightower3 has joined #crystal-lang
guniberas has joined #crystal-lang
greenbigfrog has quit [Ping timeout: 264 seconds]
greenbigfrog has joined #crystal-lang
<FromGitter> <deiv> anyone has a clue about:
<FromGitter> <deiv> Failures: ⏎ ⏎ 1) Crystal::Command::FormatCommand formats stdin (bug + show-backtrace) ⏎ ⏎ ```code paste, see link``` []
<FromGitter> <deiv> ?
<FromGitter> <Blacksmoke16> what did you run/do to cause this?
<FromGitter> <Blacksmoke16> looks like from a spec?
<FromGitter> <deiv> compiling last version of crystal
<FromGitter> <deiv> compiler spec
<FromGitter> <deiv> is strange, because only happens in certains machines
<FromGitter> <Blacksmoke16> only on certain architecture/os?
<FromGitter> <Blacksmoke16> maybe is
<FromGitter> <deiv> uhm, same architecture and OS
<FromGitter> <Blacksmoke16> hm
<FromGitter> <deiv> diffrente enviroments, I think
<FromGitter> <deiv> in my machine runs perfect the test suite
<FromGitter> <deiv> maybe is as you say, gcc10 vs gcc11
<FromGitter> <Blacksmoke16> possibly? maybe try reproducing locally with it?
<FromGitter> <deiv> I has done locally, with chroot (gcc11) and it fails
<FromGitter> <Blacksmoke16> oh nice! so it more so seem to be gcc11 issue and not related to tumbleweed?
<FromGitter> <deiv> but maybe related with the formatting (show_backtrace) instead of the test itself
<FromGitter> <Blacksmoke16> related to that issue there deff seems to be an issue with printing backtraces
<FromGitter> <deiv> is the first diffrence I spotted beetween build enviroments
<FromGitter> <Blacksmoke16> might be worth commenting on it saying you reproduced on a diff arch, so doesnt seem to be specific to that one anymore
<FromGitter> <deiv> added !
<FromGitter> <Blacksmoke16> ❤️
<FromGitter> <deiv> I will comment it, to get crystal into Debian testing finally xD
maxpowa has joined #crystal-lang
guniberas has quit [Ping timeout: 268 seconds]
ur5us has joined #crystal-lang
avane has joined #crystal-lang
avane has quit [Changing host]
ur5us has quit [Quit: Leaving]
ur5us has joined #crystal-lang
<FromGitter> <> How do you get the current cpu arch in crystal?
<FromGitter> <> jwaldrip (
<FromGitter> <> thank you